CN113498025B

CN113498025B - Bearer change method, network equipment and terminal equipment

Info

Publication number: CN113498025B
Application number: CN202010260671.7A
Authority: CN
Inventors: 吴昱民
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2020-04-03
Filing date: 2020-04-03
Publication date: 2023-03-24
Anticipated expiration: 2040-04-03
Also published as: CN113498025A; WO2021197468A1

Abstract

The invention discloses a bearer change method, network equipment and terminal equipment. The bearer change method is applied to terminal equipment, and comprises the following steps: aiming at one service, establishing a plurality of bearers according to the network side indication; receiving data of the service through a source bearer, wherein the source bearer is one of the plurality of bearers; receiving the bearer change indication information, where the bearer change indication information is used to indicate that data transmission of the service is changed from the source bearer to a target bearer, and the target bearer is one of the multiple bearers; and receiving the data of the service from the target bearer.

Description

Bearer change method, network equipment and terminal equipment

Technical Field

The present invention relates to the field of communications, and in particular, to a bearer change method, a network device, and a terminal device.

Background

In the related art, in order to effectively utilize resources of a mobile network, realize resource sharing of a network (including a core network and an access network), realize services to as many users as possible having the same requirement with as few resources as possible, and adopt a one-to-many transmission mode. For example, multimedia Broadcast Multicast Service (MBMS) or Broadcast Multicast Service (MBS)

In the LTE system, the MBMS service may be transmitted in the following two ways:

MBMS/MBS transmission mode 1: the MBMS transmission is transmitted through a Physical Multicast Channel (PMCH) in an MBMS Single Frequency Network (MBSFN) subframe. The Control information is transmitted through system information (e.g., SIB 13) and a broadcast Control Channel (MCCH), and the data is transmitted through a broadcast Traffic Channel (MTCH).

MBMS/MBS transmission mode 2: and a Physical Downlink Shared Channel (PDSCH) scheduled by a Physical Downlink Control Channel (PDCCH). The Control information is transmitted through system information (e.g., SIB 20) and a Single Cell Multicast Control Channel (SC-MCCH), and the data is transmitted through a Single Cell Multicast Traffic Channel (SC-MTCH). The SC-MCCH is transmitted through a PDSCH scheduled by a Single Cell Radio Network Temporary Identity (RNTI) (Single Cell RNTI, SC-RNTI) PDCCH, and the SC-MTCH is transmitted through a PDSCH scheduled by G-RNTI PDCCH.

The MBS service is transmitted through a specific MBMS Radio Bearer (MRB). MBS services can be marked by the following identities:

(1) Temporary Mobile Group Identity (TMGI)

(2) QoS flow identification (flow ID).

And unicast reception of the UE is received through a specific unicast Data Radio Bearer (DRB). At 5G, the protocol stack for unicast reception (or transmission) sequentially includes, from top to bottom: a Service Data Attachment Protocol (SDAP) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Media Access Control (MAC) layer.

For a specific service, if the base station wants to switch the transmission mode of the specific service between a unicast bearer and a multicast bearer, it needs to release the unicast (or multicast) bearer and then establish the multicast (or unicast) bearer for the UE, thereby possibly causing a relatively large data transmission delay.

Disclosure of Invention

The embodiment of the invention aims to provide a bearer change method, network equipment and terminal equipment so as to avoid data transmission delay caused by bearer change.

In a first aspect, a bearer change method is provided, which is applied to a terminal device, and includes: aiming at one service, establishing a plurality of bearers according to the network side indication; receiving data of the service through a source bearer, wherein the source bearer is one of the plurality of bearers; receiving the bearer change indication information, where the bearer change indication information is used to indicate that data transmission of the service is changed from the source bearer to a target bearer, and the target bearer is one of the multiple bearers; and receiving the data of the service from the target bearer.

In a second aspect, a bearer change method is provided, which is applied to a network device, and the method includes: establishing a plurality of bearers for one service; sending data of the service through a source bearer, wherein the source bearer is one of the plurality of bearers; sending bearer change indication information, wherein the bearer change indication information is used for indicating that the data transmission of the service is changed from the source bearer to a target bearer, and the target bearer is one of the bearers; and sending the data of the service from the target bearer.

In a third aspect, a terminal device is provided, which includes: a first establishing module, configured to establish multiple bearers according to a network side indication for a service; a first receiving module, configured to receive data of the service through a source bearer, where the source bearer is one of the multiple bearers; a second receiving module, configured to receive the bearer change indication information, where the bearer change indication information is used to indicate that data transmission of the service is changed from the source bearer to a target bearer, where the target bearer is one of the multiple bearers; and a third receiving module, configured to receive the data of the service from the target bearer.

In a fifth aspect, a network device is provided, which includes: a second establishing module, configured to establish a plurality of bearers for a service; a first sending module, configured to send data of the service through a source bearer, where the source bearer is one of the multiple bearers; a second sending module, configured to send bearer change indication information, where the bearer change indication information is used to indicate that data transmission of the service is changed from the source bearer to a target bearer, where the bearer is one of the bearers; and the third sending module is used for sending the data of the service from the target bearer.

In a sixth aspect, a terminal device is provided, which includes: a memory, a processor and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing the steps of the method according to the first aspect.

In a seventh aspect, a network device is provided, including: memory, a processor and a computer program stored on the memory and executable on the processor, the computer program realizing the steps of the method according to the second aspect when executed by the processor.

In an eighth aspect, a computer-readable storage medium is provided, having stored thereon a computer program which, when executed by a processor, implements the steps of the method of the first or second aspect.

In the embodiment of the invention, aiming at one service, a base station and terminal equipment establish a plurality of bearers, when the bearer needs to be changed, the base station sends the bearer change instruction and sends the service data on the target bearer, so that the service data transmission can be directly changed to the target bearer without releasing the source bearer and establishing the target bearer, thereby avoiding the sending delay of the service data caused by the bearer change.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the invention and not to limit the invention. In the drawings:

fig. 1 is a schematic flowchart of a bearer change method according to an embodiment of the present invention;

fig. 2 is another schematic flow chart of a bearer change method according to an embodiment of the present invention;

fig. 3 is a schematic structural diagram of a terminal device according to an embodiment of the present invention;

fig. 4 is a schematic structural diagram of a network device according to an embodiment of the present invention;

fig. 5 is a schematic structural diagram of another terminal device provided in the embodiment of the present invention;

fig. 6 is a schematic structural diagram of another network device according to an embodiment of the present invention.

Detailed Description

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

The technical scheme of the invention can be applied to various communication systems, such as: global System for Mobile communications (GSM), code Division Multiple Access (CDMA), wideband Code Division Multiple Access (WCDMA), general Packet Radio Service (GPRS), long Term Evolution (LTE), long Term Evolution/enhanced Long Term Evolution (LTE-a), and NR (New Radio).

User Equipment (UE), also referred to as Terminal Equipment, mobile Terminal (Mobile Terminal), mobile User Equipment, etc., may communicate with one or more core networks via a Radio Access Network (e.g., RAN), and may be Mobile terminals, such as Mobile phones (or "cellular" phones) and computers with Mobile terminals, such as portable, pocket, hand-held, computer-included, or vehicle-mounted Mobile devices, which exchange languages and/or data with the Radio Access Network.

The Base Station may be a Base Transceiver Station (BTS) in GSM or CDMA, a Base Station (NodeB) in WCDMA, or an evolved Node B (eNB or e-NodeB) and a 5G Base Station (gNB) in LTE.

The technical solutions provided by the embodiments of the present invention are described in detail below with reference to the accompanying drawings.

Fig. 1 is a flowchart of a bearer change indication method provided in an embodiment of the present invention, where the method 100 may be executed by a terminal device. In other words, the method may be performed by software or hardware installed on the terminal device. As shown in fig. 1, the method may include the following steps.

S110, aiming at one service, a plurality of bearers are established according to the network side indication.

In the embodiment of the invention, the network side can send the indication information to the UE according to the requirement to indicate the UE to establish a plurality of bearers for the data reception of the same service. Optionally, the network side sends configuration information for establishing multiple bearers to the UE, for example, the network side provides two sets of configurations for MBS service-1 (e.g., TMGI-1) at the same time, configuration-1 is used for establishing unicast bearer DRB-1, configuration-2 is used for establishing multicast bearer MRB-1, and the UE establishes unicast bearer DRB-1 and multicast bearer MRB-1 according to the configuration of the network side.

In the embodiment of the present invention, any bearer in the multiple established bearers may be any one of the following types: DRB, MRB, data flow, and Protocol Data Unit (PDU) session.

Optionally, in the embodiment of the present invention, types of multiple bearers established for the same service are different from each other.

In the embodiment of the present invention, optionally, the service may be an MBS service, and certainly, the service is not limited to this, and may also be other services as long as the data transmission channel of the service has a requirement for change.

In a specific application, if there are multiple services to be transmitted between the base station and the terminal device, multiple bearers can be established for each service.

S112, receiving the data of the service through a source bearer, where the source bearer is one of the multiple bearers.

In this embodiment of the present invention, the source bearer may be any one of a DRB, an MRB, a Data stream, and a Protocol Data Unit (PDU) session, and specifically may be determined by a network side according to a current transmission requirement of a service, which is not limited in this embodiment of the present invention.

S114, receiving bearer change indication information, where the bearer change indication information is used to indicate that data transmission of the service is changed from the source bearer to a target bearer, where the target bearer is one of the multiple bearers.

In this embodiment of the present invention, the target bearer may be any one of a DRB, an MRB, a Data stream, and a Protocol Data Unit (PDU) session, specifically, the target bearer may be determined by the network side according to the current transmission requirement of the service, and optionally, the type of the target bearer is different from the type of the source bearer.

In a possible implementation manner, the network side may instruct the UE to change the bearer for data transmission of the service by sending a data end indication on the source bearer. Thus, in this possible implementation, the bearer change indication includes: an end of data indication received from the source bearer, where the end of data indication is used to indicate that the data of the service is finished being transmitted in the source bearer, for example, end-marker. The UE may determine to change the bearer for data transmission of the service to the target bearer according to the data end indication. For example, for the same service, two bearers are established, the data sent by the network side is received on the source bearer, and then a data end instruction sent by the network side on the source bearer is received, so that the UE can know that the data for ending the service is received on the source bearer and change the receiving into receiving the data for the service from the target bearer.

Or, in another possible implementation manner, the network side may also instruct the UE to change the bearer for data transmission of the service by sending a data start indication on the target bearer. Thus, in this possible implementation, the bearer change indication includes: a data start indication received from the target bearer, wherein the data start indication is used to indicate that data of the service starts to be transmitted on the target bearer. Such as start-marker. The UE may determine to change the bearer for data transmission of the service to the target bearer according to the data start indication. For example, for the same service, two bearers are established, data sent by the network side is received on the source bearer, and then a data start instruction sent by the network side on the target bearer is received, so that the UE can know that the data reception of the service is changed to the target bearer.

In one possible implementation, the network side may send the bearer change indication through a predetermined protocol layer. Thus, in this possible implementation, step S114 may include: receiving the bearer change indication information sent by a predetermined protocol layer, wherein the predetermined protocol layer includes any one of: SDAP layer, PDCP layer, RLC protocol layer, and MAC protocol layer. With this possible implementation, the bearer change indication may be sent to the UE through a predetermined protocol layer.

In the possible implementation manner, optionally, if the bearer change indication information is sent through an MAC protocol layer, the bearer change indication information further carries the identification information of the service. Through the identification information of the service, the UE can acquire the service corresponding to the bearer change indication information.

Wherein the identification information of the service may include at least one of: a service identification (e.g., TMGI-1), a data flow identification (e.g., qoS flow-1), and a session identification (e.g., PDU session identification).

In a possible implementation manner, when the network side sends the bearer change instruction information, the bearer change instruction information may be sent through a control packet, or may be indicated through a header of a data packet. Therefore, in this possible implementation manner, the receiving the bearer change indication information sent by the predetermined protocol layer may include: receiving the bearer change indication information transmitted by the control packet of the predetermined protocol layer (e.g., the bearer change indication information indicated by a PDCP or RLC or MAC control packet); alternatively, the bearer change instruction information transmitted through the header of the data packet of the predetermined protocol layer (for example, the bearer change instruction information indicated through the header of the PDCP or RLC data packet or MAC) is received.

And S116, receiving the data of the service from the target bearer.

In a specific application, after receiving a data packet of a service from a protocol layer, a UE needs to send the data packet to a higher layer for parsing. In one possible implementation manner, after receiving the bearer change indication information, the method further includes: and transmitting a first data packet to a high layer, and then transmitting a second data packet to the high layer, wherein the first data packet is a data packet received from the source bearer before the bearer change indication information, and the second data packet is a data packet received from the target bearer.

In a possible implementation, the data packet received from the source bearer before the bearer change indication information may be data received from the source bearer before a receiving time of the bearer change indication information, and therefore, in this possible implementation, the first data packet includes: and receiving the data packet with the receiving time before the receiving time of the bearing change indication information.

For example, the PDCP layer of the source bearing DRB of the UE receives a data packet with the PDCP SN number of 1/2/3, the target bearing MRB of the UE receives the data packet 1/2/3 in sequence, and at the moment, the UE stores the data received by the MRB and temporarily delivers the data not to the higher layer application, but only delivers the data of the source DRB to the higher layer application. After the UE receives the end-marker, the UE delivers the data packet received from the source bearer before the end-marker to the high layer, and then the UE starts to deliver the data received by the MRB to the high layer application.

In another possible implementation manner, the bearer change indication information may include: and the target identification of the last data packet transmitted by the service on the source bearer. For example, the end-marker carries the number information of the last data packet sent on the source bearer, such as PDDCP SN number, or RLC SN number, etc. The data packet received from the source bearer before the bearer change indication information may be a data packet received from the source bearer and having identification information that does not exceed the destination identification indicated by the bearer change indication information. Thus, in this possible implementation, the first packet includes: identifying packets that precede or equal the target identification. For example, the PDCP layer of the source bearer DRB of the UE receives a data packet with a PDCP SN number of 1/2/3, and the UE then receives a PDCP SN number indicated by the end-marker of 4, and then the UE considers that the data packet with the PDCP SN number of 1/2/3 is "a data packet received from the source bearer before the bearer change indication information". For another example, the PDCP layer of the source bearer DRB of the UE receives the data packet with the PDCP SN number of 3, and the UE then receives the PDCP SN number indicated by the end-marker of 3, and since the data packet before the number and including the number is the "data packet received from the source bearer before the bearer change indication information", the UE considers that the data packet with the PDCP SN number of 3 is the "data packet received from the source bearer before the bearer change indication information".

For example, the PDCP layer of the source bearer DRB of the UE receives a data packet with PDCP SN number 1/2/3, the target bearer MRB of the UE receives the data packets 1/2/3 in sequence, and at this time, the UE stores the data received by the MRB and temporarily delivers it not to the upper layer application, but only the data of the source DRB to the upper layer application. When the UE receives the end-marker indicating that the PDCP SN =4, all the data packets before the number 4 have been received (the number is smaller than the number indicated by the end-marker indicating that all the data packets have been received), that is, after the UE has received all the data packets from the source bearer and delivered to the higher layer, the UE starts to deliver the data packets received from the target bearer to the higher layer.

For another example, the PDCP layer of the source bearer DRB of the UE receives a packet with PDCP SN number 1/2/3, the target bearer MRB of the UE receives the packets 1/2/3 in sequence, and at this time, the UE stores the data received by the MRB and temporarily delivers the data to the higher layer application, but only the data of the source DRB is delivered to the higher layer application. When the UE receives the end-marker indicating that the PDCP SN =3, all the data packets before the number 3 have been received (the indication that the number is less than or equal to the end-marker is received), that is, all the data packets received from the source bearer have been received and delivered to the higher layer, the UE starts to deliver the data packets received from the target bearer to the higher layer.

In the possible implementation manner, after receiving the bearer change indication information, the data packet before the target identifier indicated by the bearer change indication information may not be completely received, and the UE may continue to wait for the data packet. Thus, in one possible implementation, transmitting the second data packet to the higher layer after transmitting the first data packet to the higher layer comprises: if a data packet of a first identifier is not currently received from the source bearer, transmitting the first data packet received from the source bearer to a higher layer, and waiting for the data packet of the first identifier until the data packet of the first identifier is received from the source bearer, transmitting the data packet of the first identifier to the higher layer, or until a waiting timer corresponding to the data packet of the first identifier is overtime, wherein the first identifier is located before or equal to the target identifier; and transmitting the second data packet to a higher layer.

For example, the PDCP layer of the source bearer DRB of the UE receives a data packet with PDCP SN number 1/3, the target bearer MRB of the UE receives the data packets 1/2/3 in sequence, and at this time, the UE stores the data received by the MRB and does not deliver the data to the higher layer application, but only delivers the data of the source DRB to the higher layer application. After the UE receives the end-marker indicating that the PDCP SN =4 (or 3), because the data packet with the PDCP SN number of 2 has not been received, the UE continues to wait for the data packet with the PDCP CN number of 2 until the data packet with the PDCP CN number of 2 is received, or until the waiting timer corresponding to the data packet with the PDCP SN number is overtime, that is, the PDCP layer no longer waits for the reception of the data packet with the PDCP CN number of 2, that is, the reception behavior corresponding to the data packet with the PDCP CN number of 2 is completed. The UE then starts delivering the data packets received by the target bearer to the higher layers.

Or, in the foregoing possible implementation manner, after receiving the bearer change indication information, a data packet before the target identifier indicated by the bearer change indication information may not be completely received, and the UE ignores the data packet. Thus, in one possible implementation, transmitting the second data packet to the higher layer after transmitting the first data packet to the higher layer comprises: and if the data packet of the second identifier is not received from the source bearer currently, transmitting the second data packet to a high layer after all the first data packets which are received currently are transmitted to the high layer, wherein the second identifier is positioned before or equal to the target identifier.

For example, the PDCP layer of the source bearing DRB of the UE receives a data packet with PDCP SN number 1/3, then the UE receives the data packet with PDCP SN number 3 and PDCP SN number 2 indicated by the end-marker, and the data packet has not been received. At this time, the UE ignores the packet waiting for the PDCP SN number 2 and directly delivers the buffered packet number 1/3 to the higher layer.

After all the first data packets that have been received currently are transmitted to a higher layer, the method may further include: and if the data packet of the second identifier is received, discarding the data packet of the second identifier.

For example, in the above-described embodiment, if no data packet with PDCN SN number 2 is received, the packet is waited to be received and a timer (e.g., t-reordering) is started waiting to receive the packet, and if the timer expires, the packet is ignored for reception. Alternatively, reception of the packet is directly ignored. If the packet is received after "ignoring the reception of the packet", the packet is discarded.

In one possible implementation, for the data packet received from the source bearer after the bearer change indication information, the UE may directly discard the data packet. Corresponding to the data packet received from the source bearer before the bearer change instruction information, the data packet received from the source bearer after the bearer change instruction information may include any one of the following:

(1) In the order of reception time, the data packets after the reception time of the bearer change instruction information are all "data packets received from the source bearer after the bearer change instruction information".

(2) In the order of the numbers of the packets indicated by the bearer change instruction information, the packets subsequent to (or equal to) the number of the packet indicated by the bearer change instruction information are all "packets received from the source bearer before the end instruction information". For example, the UE receives the PDCP SN of end-marker 4, and the PDCP layer of the source bearer DRB of the UE receives the data packet of PDCP SN 1/2/3/4/5/6/7, and then the UE considers that the data packet of PDCP SN 5/6/7 is "the data packet received from the source bearer after the bearer change indication information".

It should be noted that, although the end-marker is used as an example to indicate the target identifier in the above description, the present invention is not limited to this, and in practical applications, the network side may also indicate the target identifier by a start-marker sent on a target bearer, and the embodiment of the present invention is not limited in this embodiment.

In one possible implementation, transmitting the first packet to the higher layer may include: and after receiving the bearing change indication information and waiting for a preset time, transmitting the first data packet to a high layer. That is, in this possible implementation manner, after receiving the bearer change instruction information, the UE waits for a period of time and delivers the data packet received from the source bearer to the higher layer application before sending the bearer change instruction information.

Wherein, waiting for the predetermined time may include any one of:

(1) After receiving the bearing change indication information, starting a first timer, and waiting for the first timer to be overtime; that is, the timer started by the UE after receiving the end indication information expires. The value of the timer may be agreed by a protocol or configured by a network.

(2) And a second timer is overtime, wherein the second timer is used for waiting for the data packet which is not received. I.e. the timer used by the UE to wait for a data packet not received has expired. For example, the PDCP layer of the UE starts a Reordering timer (e.g., t-Reordering) when it finds that there is a PDCN SN without a data packet received.

In a possible implementation manner, in order to enable the network side to know feedback of the UE for the bearer change indication information, after receiving the sent bearer change indication information, the method may further include: transmitting one or more feedback information when a trigger condition is met, wherein the trigger condition comprises any one of the following: receiving the bearer change indication information, receiving the bearer change indication information and transmitting the first data packet to a higher layer, receiving the bearer change indication information and starting to transmit the second data packet to the higher layer.

In a possible implementation manner, in order to enable the network side to know the receiving state of the UE before bearer change and avoid missed data reception, after receiving the bearer change indication information, the method may further include: sending reception status information on the source bearer, wherein the reception status information includes at least one of: an identification of a first not received data packet, an identification of a next data packet of the first not received data packet, an identification of a not received data packet. In this possible implementation manner, the UE may report the data receiving status on the source bearer to the network side, so that the network side may know the data receiving condition of the UE on the source bearer, and the network side may conveniently retransmit the data that is not received by the UE on the target bearer according to the data receiving status.

In the possible implementation manner, the UE may report the received data packet and the data packet that is not received to the network side in a bitmap manner. For example, assuming that the maximum number of a data packet of the service currently received by the UE through the source bearer is 8, the UE may send an 8-bit sequence to the network side, where a value of each bit correspondingly indicates whether one data packet is received, where a specific value (e.g., "0") may identify "received" and another specific value (e.g., "1") may identify "not received".

Through the technical scheme provided by the embodiment of the invention, the UE simultaneously establishes a plurality of different types of bearers for receiving the same service, and ensures that the UE can forward the received data when the service data is transmitted in a conversion way among different bearers.

Fig. 2 is another flowchart of a bearer change method according to an embodiment of the present invention, where the method 200 may be executed by a network device, for example, a base station. In other words, the method may be performed by software or hardware installed on the network device. As shown in fig. 2, the method may include the following steps.

S210, establishing a plurality of bearers for a service.

This step corresponds to S110 in the method 100, and for the same service, the network device may configure configuration information of multiple bearers for the UE, and indicate to the terminal device to establish the multiple bearers.

In the embodiment of the present invention, the service may include, but is not limited to, an MBMS service.

In this embodiment of the present invention, the type of any bearer in the multiple established bearers includes any of: DRB, MRB, data flow, and PDU session. Wherein, in the plurality of bearers, the types of the bearers are different.

S212, sending the data of the service through a source bearer, where the source bearer is one of the multiple bearers.

This step corresponds to S112 in the method 100, and for details, reference is made to the description in the method 100, and details are not repeated here.

S214, sending bearer change indication information, where the bearer change indication information is used to indicate that data transmission of the service is changed from the source bearer to a target bearer, where the bearer is one of the multiple bearers.

In a specific application, the network device determines to change the bearer for transmitting the data of the service, and then sends bearer change indication information to indicate the UE to change the bearer.

As described in the method 100, in a possible implementation manner, the bearer change indication information may include: and a data end indication sent through the source bearer, where the data end indication is used to indicate that the sending of the data of the service is ended in the source bearer. That is, the network device may send the data end indication at the source bearer, indicating that the data transmission of the service at the source bearer is ended. The UE may determine, through the data end indication, that the data transmission of the service is changed from the source bearer to the target bearer.

Or, in another possible implementation manner, the bearer change indication information may also include: and sending a data start indication through a target bearer, wherein the data start indication is used for indicating that the data of the service starts to be sent in the bearer. That is, the network device may send a data start indication at the target bearer, indicating that the data start of the service ends on the target bearer. The UE may determine, through the data start indication, that the data transmission of the service is changed from the source bearer to the target bearer.

In one possible implementation manner, corresponding to the method 100, in S214, when the bearer change indication information is sent, the bearer change indication information may be sent through a predetermined protocol layer, where the predetermined protocol layer includes any one of the following: SDAP layer, PDCP protocol layer, RLC protocol layer, and MAC protocol layer.

In the possible implementation manner, if the bearer change indication information is sent through an MAC protocol layer, the bearer change indication information also carries the identification information of the service.

Wherein the identification information of the service includes but is not limited to at least one of the following: a service identification, a data stream identification, and a session identification.

In a possible implementation manner, the sending the bearer change indication information through a predetermined protocol layer includes any one of the following:

(1) And sending the bearing change indication information through the control packet of the predetermined protocol layer. I.e. the bearer change indication information is indicated by a control packet of a predetermined protocol layer, e.g. indicated by a PDCP or RLC or MAC control packet.

(2) And sending the bearing change indication information through the packet header of the data packet of the predetermined protocol layer. I.e. by header indication of a data packet of a predetermined protocol layer, e.g. by PDCP or RLC data packet or MAC.

S216, sending the data of the service from the target bearer.

In this embodiment of the present invention, after sending the bearer change indication information, the network device sends the data of the service from the target bearer.

In one possible implementation, after S214, the method may further include: receiving one or more feedback messages of the bearer change indication message. The one or more pieces of feedback information may be sent by the terminal device when the trigger condition is met, which may specifically refer to the related description in the method 100.

In one possible implementation, after S214, the method may further include: receiving status information of the source bearer, wherein the receiving status information includes at least one of: an identifier of a first not received packet, an identifier of a next packet of the first not received packet, an identifier of a received packet, and an identifier of a not received packet. By means of this reception status information, the network device can determine whether certain data packets need to be retransmitted on the target bearer.

In one possible implementation, before S210, the method may further include: and sending configuration indication information to indicate the plurality of bearers to be established. For example, configuration information of multiple bearers is transmitted to the UE.

Through the technical scheme provided by the embodiment of the invention, the network equipment and the terminal equipment can simultaneously establish unicast bearer and multicast bearer for the same service, and when the network equipment changes a specific service data from bearer 1 to bearer 2 for transmission, the network equipment transmits data transmission ending indication information at bearer 1 or transmits data starting indication at bearer 2, so that the UE can know the bearer change of the service and receive the service data on the corresponding bearer.

Fig. 3 is a schematic structural diagram of a terminal device according to an embodiment of the present invention, and as shown in fig. 3, the terminal device 300 includes: a first establishing module 310, configured to establish, for a service, multiple bearers according to a network side indication; a first receiving module 320, configured to receive data of the service through a source bearer, where the source bearer is one of the bearers; a second receiving module 330, configured to receive the bearer change indication information, where the bearer change indication information is used to indicate that data transmission of the service is changed from the source bearer to a target bearer, where the target bearer is one of the multiple bearers; a third receiving module 340, configured to receive data of the service from the target bearer.

In one possible implementation, the type of any bearer in the plurality of bearers includes any one of: DRB, MBMS carry MRB, data flow, and PDU sessions.

In a possible implementation manner, the receiving, by the second receiving module 330, the bearer change indication information includes: receiving the bearer change indication information sent by a predetermined protocol layer, wherein the predetermined protocol layer includes any one of: SDAP layer, PDCP layer, RLC protocol layer, and MAC protocol layer.

In a possible implementation manner, if the bearer change indication information is sent through an MAC protocol layer, the bearer change indication information also carries identification information of the service.

In one possible implementation, the identification information of the service includes at least one of: service identification, data stream identification and session identification.

In a possible implementation manner, the receiving, by the second receiving module 330, the bearer change indication information sent by the predetermined protocol layer includes: receiving the bearing change indication information sent by the control packet of the predetermined protocol layer; or, the bearer change instruction information transmitted through the header of the packet of the predetermined protocol layer is received.

In one possible implementation, the method further includes: a transmission module, configured to transmit a first data packet to a higher layer after receiving the bearer change indication information, and then transmit a second data packet to the higher layer, where the first data packet is a data packet received from the source bearer before the bearer change indication information, and the second data packet is a data packet received from the target bearer.

In one possible implementation, the first data packet includes: and receiving the data packet with the receiving time before the receiving time of the bearing change indication information.

In one possible implementation manner, the bearer change indication information includes: the target identifier of the last data packet transmitted by the service on the source bearer; the first data packet includes: identifying packets that precede or equal the target identification.

In one possible implementation, transmitting the second data packet to the higher layer after transmitting the first data packet to the higher layer includes: if a data packet of a first identifier is not currently received from the source bearer, transmitting the first data packet received from the source bearer to a higher layer, and waiting for the data packet of the first identifier until the data packet of the first identifier is received from the source bearer, transmitting the data packet of the first identifier to the higher layer, or until a waiting timer corresponding to the data packet of the first identifier is overtime, wherein the first identifier is located before or equal to the target identifier; and transmitting the second data packet to a higher layer.

In one possible implementation, transmitting the second data packet to the higher layer after transmitting the first data packet to the higher layer includes: and if the data packet of the second identifier is not received from the source bearer currently, transmitting the second data packet to a high layer after all the first data packets which are received currently are transmitted to the high layer, wherein the second identifier is positioned before or equal to the target identifier.

In a possible implementation manner, the processing module is configured to discard the data packet of the second identifier if the data packet of the second identifier is received after all the first data packets that have been currently received are transmitted to the higher layer.

In one possible implementation, transmitting the first packet to the higher layer includes: and after receiving the bearing change indication information and waiting for a preset time, transmitting the first data packet to a high layer.

In one possible implementation, waiting the predetermined time includes: after receiving the bearing change indication information, starting a first timer, and waiting for the first timer to be overtime; or a second timer expires, wherein the second timer is used for waiting for a data packet which is not received.

In one possible implementation, the method further includes: a first sending module, configured to send one or more pieces of feedback information when a trigger condition is met after receiving the sent bearer change indication information, where the trigger condition includes any one of: receiving the bearer change indication information, receiving the bearer change indication information and transmitting the first data packet to a higher layer, receiving the bearer change indication information and starting to transmit the second data packet to the higher layer.

In one possible implementation, the method further includes: a second sending module, configured to send, after receiving bearer change indication information, reception status information on the source bearer, where the reception status information includes at least one of the following: an identification of a first not received data packet, an identification of a next data packet of the first not received data packet, an identification of a not received data packet.

In a possible implementation manner, the bearer change indication information includes one of: a data end indication received from the source bearer, where the data end indication is used to indicate that the sending of the data of the service is ended in the source bearer; a data start indication received from the target bearer, wherein the data start indication is used to indicate that data of the service starts to be transmitted on the target bearer.

The terminal device provided in the embodiment of the present invention can implement each process implemented by the terminal device in each method embodiment of fig. 1 to fig. 2, and achieve the same effect to avoid repetition, which is not described herein again.

Fig. 4 is a schematic structural diagram of a network device according to an embodiment of the present invention, and as shown in fig. 4, the network device 400 includes: a second establishing module 410, configured to establish a plurality of bearers for one service; a first sending module 420, configured to send data of the service through a source bearer, where the source bearer is one of the multiple bearers; a second sending module 430, configured to send bearer change indication information, where the bearer change indication information is used to indicate that data transmission of the service is changed from the source bearer to a target bearer, where the bearer is one of the multiple bearers; a third sending module 440, configured to send data of the service from the target bearer.

In one possible implementation, the type of any bearer in the plurality of bearers includes any one of: the unicast bearer DRB, the multimedia broadcast multicast service MBMS bearer MRB, the data stream and the protocol data unit PDU session.

In a possible implementation manner, the sending module 430 sends the bearer change indication information, including: sending the bearer change indication information through a predetermined protocol layer, wherein the predetermined protocol layer includes any one of: SDAP layer, PDCP protocol layer, RLC protocol layer, and MAC protocol layer.

In one possible implementation manner, the sending the bearer change indication information through a predetermined protocol layer includes: sending the bearing change indication information through the control packet of the predetermined protocol layer; or, the bearer change instruction information is sent through a header of a packet of the predetermined protocol layer.

In one possible implementation, the method further includes: the first receiving module is configured to receive one or more pieces of feedback information of the bearer change indication information after sending the bearer change indication information.

In one possible implementation, the method further includes: a second receiving module, configured to receive receiving status information of the source bearer after sending bearer change indication information, where the receiving status information includes at least one of the following: an identification of a first not received data packet, an identification of a next data packet of the first not received data packet, an identification of a not received data packet.

In one possible implementation, the method further includes: a third sending module, configured to send configuration indication information to indicate the multiple bearers that need to be established before the multiple bearers are established.

In a possible implementation manner, the bearer change indication information includes one of: a data end indication sent through the source bearer, where the data end indication is used to indicate that the sending of the data of the service is ended in the source bearer; and a data start indication sent by the target bearer, wherein the data start indication is used for indicating that the data of the service starts to be sent in the bearer.

The network device provided in the embodiment of the present invention can implement each process implemented by each network device, base station, or network side in each method embodiment in fig. 1 to fig. 2, and achieve the same effect to avoid repetition, which is not described herein again.

Fig. 5 is a block diagram of a terminal device of another embodiment of the present invention. The terminal device 500 shown in fig. 5 includes: at least one processor 501, memory 502, at least one network interface 504, and a user interface 503. The various components in the terminal device 500 are coupled together by a bus system 505. It is understood that the bus system 505 is used to enable connection communications between these components. The bus system 505 includes a power bus, a control bus, and a status signal bus in addition to a data bus. For clarity of illustration, however, the various buses are labeled as bus system 505 in FIG. 5.

The user interface 503 may include, among other things, a display, a keyboard, or a pointing device (e.g., a mouse, trackball, touch pad, or touch screen, among others.

It is to be understood that the memory 502 in embodiments of the present invention may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of illustration and not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), dynamic Random Access Memory (DRAM), synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), enhanced Synchronous SDRAM (ESDRAM), sync Link DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memory 502 of the subject systems and methods described in connection with the embodiments of the invention is intended to comprise, without being limited to, these and any other suitable types of memory.

In some embodiments, memory 502 stores elements, executable modules or data structures, or a subset thereof, or an expanded set thereof as follows: an operating system 5021 and application programs 5022.

The operating system 5021 includes various system programs, such as a framework layer, a core library layer, a driver layer, and the like, and is used for implementing various basic services and processing hardware-based tasks. The application 5022 includes various applications, such as a Media Player (Media Player), a Browser (Browser), and the like, for implementing various application services. A program for implementing the method according to the embodiment of the present invention may be included in the application program 5022.

In this embodiment of the present invention, the terminal device 500 further includes: a computer program stored on a memory 502 and executable on a processor 501, the computer program when executed by the processor 501 implementing the steps of:

aiming at one service, establishing a plurality of bearers according to the network side indication;

receiving data of the service through a source bearer, wherein the source bearer is one of the plurality of bearers;

receiving bearer change indication information, wherein the bearer change indication information is used for indicating that data transmission of the service is changed from the source bearer to a target bearer, and the target bearer is one of the bearers;

and receiving the data of the service from the target bearer.

The method disclosed by the above-mentioned embodiments of the present invention may be applied to the processor 501, or implemented by the processor 501. The processor 501 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 501. The Processor 501 may be a general-purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components. The various methods, steps and logic blocks disclosed in the embodiments of the present invention may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules may reside in ram, flash memory, rom, prom, or eprom, registers, among other computer-readable storage media known in the art. The computer readable storage medium is located in the memory 502, and the processor 501 reads the information in the memory 502 and performs the steps of the above method in combination with the hardware thereof. In particular, the computer readable storage medium has stored thereon a computer program which, when executed by the processor 501, implements the steps of the method 300 as described above.

It is to be understood that the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or any combination thereof. For a hardware implementation, the Processing units may be implemented within one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), general purpose processors, controllers, micro-controllers, microprocessors, other electronic units designed to perform the functions described herein, or a combination thereof.

For a software implementation, the techniques described in this disclosure may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described in this disclosure. The software codes may be stored in a memory and executed by a processor. The memory may be implemented within the processor or external to the processor.

The terminal device 500 can implement the foregoing processes implemented by the terminal devices in fig. 1 to fig. 2, and details are not repeated here to avoid repetition.

Referring to fig. 6, fig. 6 is a structural diagram of a network device applied in the embodiment of the present invention, which can be used as a base station or a core network to implement various details of the methods 100 to 300, and achieve the same effects. As shown in fig. 6, the network device 600 includes: a processor 601, a transceiver 602, a memory 603, a user interface 604 and a bus interface.

In this embodiment of the present invention, the network device 600 further includes: a computer program stored in the memory 603 and executable on the processor 601, the computer program when executed by the processor 601 performing the steps of: establishing a plurality of bearers for one service; sending data of the service through a source bearer, wherein the source bearer is one of the plurality of bearers; sending bearer change indication information, wherein the bearer change indication information is used for indicating that the data transmission of the service is changed from the source bearer to a target bearer, and the bearer is one of the bearers; and sending the data of the service from the target bearer.

In fig. 6, the bus architecture may include any number of interconnected buses and bridges, with one or more processors represented by processor 601 and various circuits of memory represented by memory 603 being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 602 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium. The user interface 604 may also be an interface capable of interfacing with a desired device for different user devices, including but not limited to a keypad, display, speaker, microphone, joystick, etc.

The processor 601 is responsible for managing the bus architecture and general processing, and the memory 603 may store data used by the processor 601 in performing operations.

The network device 600 can implement the foregoing processes implemented by the base station or the network side in fig. 1 to fig. 2, and achieve the same effect to avoid repetition, which is not described herein again.

An embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the network device or the terminal device in each of the embodiments shown in fig. 1 to 2 may implement each process, and may achieve the same technical effect, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising a … …" does not exclude the presence of another identical element in a process, method, article, or apparatus that comprises the element.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.

While the present invention has been described with reference to the particular illustrative embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, but is intended to cover various modifications, equivalent arrangements, and equivalents thereof, which may be made by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A bearer change method is applied to a terminal device, and comprises the following steps:

receiving bearer change indication information, wherein the bearer change indication information is used for indicating that data transmission of the service is changed from the source bearer to a target bearer, and the target bearer is one of the plurality of bearers; the type of the target bearer is different from the type of the source bearer;

receiving data of the service from the target bearer;

wherein after receiving the bearer change indication information, the method further comprises: and transmitting a first data packet to a high layer, and then transmitting a second data packet to the high layer, wherein the first data packet is a data packet received from the source bearer before the bearer change indication information, and the second data packet is a data packet received from the target bearer.

2. The method of claim 1, wherein the type of any of the plurality of bearers comprises any of: the unicast bearer DRB, the multimedia broadcast multicast service MBMS bearer MRB, the data stream and the protocol data unit PDU session.

3. The method of claim 1, wherein receiving the bearer change indication information comprises:

receiving the bearer change indication information sent by a predetermined protocol layer, wherein the predetermined protocol layer includes any one of: a service data adaptation protocol SDAP layer, a packet data convergence protocol PDCP layer, a radio link control RLC protocol layer, and a medium access control MAC protocol layer.

4. The method of claim 3, wherein if the bearer change indication information is sent through a MAC protocol layer, the bearer change indication information further carries identification information of the service.

5. The method of claim 4, wherein the identification information of the service comprises at least one of: service identification, data stream identification and session identification.

6. The method of claim 3, wherein receiving the bearer change indication information sent by the predetermined protocol layer comprises:

receiving the bearing change indication information sent by the control packet of the predetermined protocol layer; alternatively, the first and second electrodes may be,

and receiving the bearer change indication information sent by the header of the data packet of the predetermined protocol layer.

7. The method of claim 1, wherein the first packet comprises: and receiving the data packet with the receiving time before the receiving time of the bearing change indication information.

8. The method of claim 1,

the bearer change instruction information includes: the target identifier of the last data packet transmitted by the service on the source bearer;

the first packet includes: identifying packets that precede or equal the target identification.

9. The method of claim 8, wherein transmitting the second data packet to the higher layer after transmitting the first data packet to the higher layer comprises:

if a data packet with a first identifier is not received from the source bearer currently, transmitting the first data packet received from the source bearer to a higher layer, and waiting for the data packet with the first identifier until the data packet with the first identifier is received from the source bearer, transmitting the data packet with the first identifier to the higher layer, or until a waiting timer corresponding to the data packet with the first identifier is overtime, wherein the first identifier is positioned before or equal to the target identifier;

and transmitting the second data packet to a higher layer.

10. The method of claim 8, wherein transmitting the second data packet to the higher layer after transmitting the first data packet to the higher layer comprises:

and if the data packet of the second identifier is not received from the source bearer currently, transmitting the second data packet to a high layer after all the first data packets which are received currently are transmitted to the high layer, wherein the second identifier is positioned before or equal to the target identifier.

11. The method of claim 10, wherein after transmitting all of the first data packets that have been currently received to a higher layer, the method further comprises:

and if the data packet of the second identifier is received, discarding the data packet of the second identifier.

12. The method of claim 1, wherein transmitting the first packet to the higher layer comprises:

and after receiving the bearing change indication information and waiting for a preset time, transmitting the first data packet to a high layer.

13. The method of claim 12, wherein waiting a predetermined time comprises:

after receiving the bearing change indication information, starting a first timer, and waiting for the first timer to be overtime; or

And a second timer is overtime, wherein the second timer is used for waiting for the data packet which is not received.

14. The method of claim 1, wherein after receiving the transmitted bearer change indication information, the method further comprises:

transmitting one or more feedback information when a trigger condition is met, wherein the trigger condition comprises any one of the following: receiving the bearer change indication information, receiving the bearer change indication information and transmitting the first data packet to a higher layer, receiving the bearer change indication information and starting to transmit the second data packet to the higher layer.

15. The method of claim 1, wherein after receiving bearer change indication information, the method further comprises:

transmitting reception status information on the source bearer, wherein the reception status information comprises at least one of: an identification of a first not received data packet, an identification of a next data packet of the first not received data packet, an identification of a not received data packet.

16. The method according to any of claims 1 to 15, wherein the bearer change indication information comprises one of:

a data end indication received from the source bearer, wherein the data end indication is used for indicating that the transmission of the data of the service is ended in the source bearer;

a data start indication received from the target bearer, wherein the data start indication is used to indicate that data of the service starts to be sent in the target bearer.

17. A method for changing a bearer is applied to a network device, and comprises the following steps:

establishing a plurality of bearers for one service;

sending data of the service through a source bearer, wherein the source bearer is one of the plurality of bearers;

sending bearer change indication information, wherein the bearer change indication information is used for indicating that data transmission of the service is changed from the source bearer to a target bearer, and the target bearer is one of the bearers; the type of the target bearer is different from the type of the source bearer;

sending data of the service from the target bearer;

wherein the bearer change indication information includes one of:

a data end indication sent through the source bearer, where the data end indication is used to indicate that the sending of the data of the service is ended in the source bearer;

and a data start indication sent by the target bearer, wherein the data start indication is used for indicating that the data of the service starts to be sent in the bearer.

18. The method of claim 17, wherein the type of any of the plurality of bearers comprises any of: the unicast bearer DRB, the multimedia broadcast multicast service MBMS bearer MRB, the data stream and the protocol data unit PDU session.

19. The method of claim 17, wherein sending bearer change indication information comprises:

sending the bearer change indication information through a predetermined protocol layer, wherein the predetermined protocol layer includes any one of: SDAP layer, PDCP protocol layer, RLC protocol layer, and MAC protocol layer.

20. The method of claim 19, wherein if the bearer change indication information is sent through a MAC protocol layer, the bearer change indication information further carries identification information of the service.

21. The method of claim 20, wherein the identification information of the service comprises at least one of: service identification, data stream identification and session identification.

22. The method of claim 19, wherein sending the bearer change indication information through a predetermined protocol layer comprises:

sending the bearing change indication information through a control packet of the predetermined protocol layer; alternatively, the first and second electrodes may be,

and sending the bearing change indication information through the packet header of the data packet of the predetermined protocol layer.

23. The method of claim 17, wherein after sending bearer change indication information, the method further comprises:

receiving one or more feedback messages of the bearer change indication message.

24. The method of claim 17, wherein after sending bearer change indication information, the method further comprises:

receiving status information of the source bearer, wherein the receiving status information includes at least one of: an identification of a first not received data packet, an identification of a next data packet of the first not received data packet, an identification of a not received data packet.

25. The method of any of claims 17 to 24, wherein prior to establishing the plurality of bearers, the method further comprises:

and sending configuration indication information to indicate the plurality of bearers to be established.

26. A terminal device, comprising:

the first establishing module is used for establishing a plurality of bearers according to the network side indication aiming at one service;

a first receiving module, configured to receive data of the service through a source bearer, where the source bearer is one of the multiple bearers;

a second receiving module, configured to receive bearer change indication information, where the bearer change indication information is used to indicate that data transmission of the service is changed from the source bearer to a target bearer, where the target bearer is one of the bearers; the type of the target bearer is different from the type of the source bearer;

a third receiving module, configured to receive data of the service from the target bearer;

a transmission module, configured to transmit a first data packet to a higher layer after receiving the bearer change indication information, and then transmit a second data packet to the higher layer, where the first data packet is a data packet received from the source bearer before the bearer change indication information, and the second data packet is a data packet received from the target bearer.

27. A network device, comprising:

a second establishing module, configured to establish a plurality of bearers for a service;

a first sending module, configured to send data of the service through a source bearer, where the source bearer is one of the multiple bearers;

a second sending module, configured to send bearer change indication information, where the bearer change indication information is used to indicate that data transmission of the service is changed from the source bearer to a target bearer, where the bearer is one of the multiple bearers; the type of the target bearer is different from the type of the source bearer;

a third sending module, configured to send data of the service from the target bearer;

wherein the bearer change indication information includes one of:

28. A terminal device, comprising: memory, processor and computer program stored on the memory and executable on the processor, which computer program, when executed by the processor, carries out the steps of the method according to any one of claims 1 to 16.

29. A network device characterized by a memory, a processor and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing the steps of the method according to any one of claims 17 to 25.

30. A computer-readable storage medium, having a computer program stored thereon, which when executed by a processor, implements:

the steps of the method of any one of claims 1 to 16; or

The steps of the method of any one of claims 17 to 25.