CN114070482A

CN114070482A - Service transmission processing method and device, network side equipment and terminal

Info

Publication number: CN114070482A
Application number: CN202010762077.8A
Authority: CN
Inventors: 周叶
Original assignee: Datang Mobile Communications Equipment Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2020-07-31
Filing date: 2020-07-31
Publication date: 2022-02-18
Anticipated expiration: 2040-07-31
Also published as: CN114070482B

Abstract

The embodiment of the invention provides a method and a device for processing service transmission, network side equipment and a terminal, wherein the method comprises the following steps: sending a first message to a first terminal device, the first message comprising: first configuration information of a first downlink logical channel and a second downlink logical channel, where the first downlink logical channel is a single-pair single channel configured by a network side device for a first multicast radio bearer of the first terminal device, and the second downlink logical channel is a single-pair multi-channel configured by the network side device for the first multicast radio bearer of the first terminal device; wherein the first downlink logical channel and the second downlink logical channel share the same radio link control, RLC, state variable; the embodiment of the invention can lead the network to flexibly realize single multicast conversion aiming at each terminal device, and can also reuse the automatic retransmission mechanism of the RLC to the multicast service.

Description

Service transmission processing method and device, network side equipment and terminal

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for processing service transmission, a network side device, and a terminal.

Background

A scenario exists in a wireless communication system in which a plurality of User Equipments (UEs) request the same downlink service data. In order to reduce the operation cost, a "multicast" function is proposed in the industry, which allows the network side of one radio cell to transmit a single downlink data using a specific radio resource, and a plurality of ues respectively receive and decode the downlink data at the same time, so as to achieve the purpose that the network transmits the downlink data to the plurality of ues using one radio communication resource. This mode is called multicast mode, also known as Point to Multipoint (PtM). In contrast, the network sends a single downlink data through a specific radio resource, and the transmission mode in which only one ue receives and decodes the downlink data is called unicast mode, also called Point to Point (PtP).

In the prior art, for each piece of downlink RLC (Radio Link Control) bearer adopting an Acknowledged Mode (AM), according to configuration of an RRC signaling, an RLC layer of a receiving side may send an RLC Protocol Data Unit (PDU) to an RLC layer of a sending side at a certain time, where the PDU is in a state PDU format, and is used to inform the RLC layer of the sending side of which Sequence Number (SN) RLC Service Data units (Service Data units, SDUs) have been completely received, and which RLC of SN has not been completely received. Further, the status PDU may also include RLC SDUs that have not been completely received, specifically which segments (segments) have not been successfully received. The RLC layer of the transmitting side may accordingly retransmit RLC SDUs or segments thereof that are not completely received to the RLC layer of the receiving side. This process is called an ARQ (Automatic Repeat Request) process, and this mechanism is called an Automatic retransmission mechanism.

According to the prior art, a network cannot flexibly realize single multicast conversion for each terminal device, and if the existing automatic retransmission mechanism of the RLC is directly reused on the multicast service, obvious air interface resource waste is caused.

Disclosure of Invention

Embodiments of the present invention provide a method and an apparatus for processing service transmission, a network side device, and a terminal, so as to solve a problem in the prior art that a single-multicast conversion cannot be flexibly implemented for each terminal device.

In order to solve the above problem, an embodiment of the present invention provides a method for processing service transmission, which is applied to a network device, and includes:

sending a first message to a first terminal device, the first message comprising: first configuration information of a first downlink logical channel and a second downlink logical channel, where the first downlink logical channel is a single-pair single channel configured by a network side device for a first multicast radio bearer of the first terminal device, and the second downlink logical channel is a single-pair multi-channel configured by the network side device for the first multicast radio bearer of the first terminal device;

wherein the first downlink logical channel and the second downlink logical channel share the same radio link control, RLC, state variable.

Wherein the first message further comprises:

first indication information, where the first indication information is used to indicate the first terminal device to activate or deactivate the second downlink logical channel.

Wherein the method further comprises:

and sending a second message to the first terminal device, where the second message carries second indication information for indicating the first terminal device to activate or deactivate the second downlink logical channel.

Wherein the second message is: RLC protocol data unit PDU.

Wherein the first message further comprises:

and second configuration information of a first uplink logical channel, where the first uplink logical channel is a single-to-single channel configured by the first multicast radio bearer of the first terminal device of the network side device.

Wherein the method further comprises:

receiving an RLC status report sent by the first terminal equipment through the first uplink logical channel; the RLC status report is generated by the first terminal device according to the data of the first multicast radio bearer received by the first terminal device through the second downlink logical channel;

determining data of a first multicast radio bearer which is not received by the first terminal equipment according to the RLC status report;

transmitting the determined data of the first multicast radio bearer not received by the first terminal device to the first terminal device through the first downlink logical channel.

Before receiving the RLC status report sent by the first terminal device through the first uplink logical channel, the method further includes:

and sending RLC protocol data units to the first terminal equipment through the second downlink logical channel, wherein at least one RLC protocol data unit comprises third indication information, and the third indication information is used for indicating the first terminal equipment to feed back the RLC status report.

Wherein, before sending the first message to the first terminal device, the method further comprises:

mapping the first multicast radio bearer to a first RLC channel;

mapping the first RLC channel to the first downlink logical channel and the second downlink logical channel;

establishing a first RLC entity for processing the first RLC channel, a first sending port of the first downlink logical channel on the first RLC entity, and a second sending port of the second downlink logical channel on the first RLC entity; wherein the first RLC entity maintains an RLC state variable shared by the first downlink logical channel and the second downlink logical channel.

mapping the first multicast radio bearer to a second RLC channel and a third RLC channel;

mapping the second RLC channel to the first downlink logical channel, and mapping the third RLC channel to the second downlink logical channel;

establishing a second RLC entity for processing the second RLC channel and a third sending port of the first downlink logical channel on the second RLC entity;

establishing a third RLC entity for processing the third RLC channel and a fourth sending port of the second downlink logical channel on the third RLC entity;

wherein the second RLC entity maintains an RLC state variable shared by the first downlink logical channel and the second downlink logical channel; or, the second RLC entity and the third RLC entity respectively maintain the RLC state variables shared by the first downlink logical channel and the second downlink logical channel;

and the sending conditions of the first downlink logical channel and the second downlink logical channel can be interacted between the second RLC entity and the third RLC entity.

The embodiment of the invention also provides a method for processing service transmission, which is applied to the first terminal device and comprises the following steps:

receiving a first message sent by a network side device, wherein the first message comprises: first configuration information of a first downlink logical channel and a second downlink logical channel, where the first downlink logical channel is a single-pair single channel configured by a network side device for a first multicast radio bearer of the first terminal device, and the second downlink logical channel is a single-pair multi-channel configured by the network side device for the first multicast radio bearer of the first terminal device;

Wherein the first message further comprises:

Wherein the method further comprises:

and receiving a second message sent by the network side device, where the second message carries second indication information used for indicating the first terminal device to activate or deactivate the second downlink logical channel.

Wherein the second message is: RLC protocol data unit PDU.

Wherein the method comprises the following steps:

and receiving the data of the first multicast radio bearer sent by the network side equipment through the second downlink logical channel according to the bottom layer configuration information associated with the second downlink logical channel under the condition of activating the second downlink logical channel.

Wherein the first message further comprises:

Wherein the method further comprises:

generating an RLC status report according to the data of the first multicast radio bearer received by the first terminal equipment through the second downlink logical channel;

and sending the RLC status report through the first uplink logical channel, wherein the RLC status report at least indicates data of a first multicast radio bearer which is not received by the first terminal equipment.

Wherein, before the RLC status report is sent through the first uplink logical channel, the method further includes:

and receiving RLC protocol data units sent by the network side equipment through the second downlink logical channel, wherein at least one RLC protocol data unit contains third indication information, and the third indication information is used for indicating the first terminal equipment to feed back the RLC status report.

After receiving the first message sent by the network side device, the method further includes:

establishing a fourth RLC entity for processing a first RLC channel according to the first message; wherein, the first RLC channel is a channel mapped by the first multicast radio bearer;

establishing a first receiving port of the first downlink logical channel on a fourth RLC entity and a second receiving port of the second downlink logical channel on the fourth RLC entity;

wherein the fourth RLC entity maintains an RLC state variable shared by the first downlink logical channel and the second downlink logical channel.

according to the first message, establishing a fifth RLC entity for processing a second RLC channel and a sixth RLC entity for processing a third RLC channel; the second RLC channel and the third RLC channel are channels mapped by the first multicast radio bearer respectively;

establishing a fifth RLC entity for processing the second RLC channel and a third receiving port of the first downlink logical channel on the fifth RLC entity;

establishing a sixth RLC entity for processing the third RLC channel and a fourth receiving port of the second downlink logical channel on the sixth RLC entity;

wherein the fifth RLC entity maintains an RLC state variable shared by the first downlink logical channel and the second downlink logical channel; or, the fifth RLC entity and the sixth RLC entity respectively maintain the RLC state variables shared by the first downlink logical channel and the second downlink logical channel;

and the sending conditions of the first downlink logical channel and the second downlink logical channel can be interacted between the fifth RLC entity and the sixth RLC entity.

The embodiment of the invention also provides network side equipment, which comprises a memory, a transceiver and a processor; a memory for storing a computer program; a transceiver for transceiving data under control of the processor; a processor for reading the computer program in the memory and performing the following operations:

Wherein the first message further comprises:

Wherein the processor is further configured to read the computer program in the memory and perform the following operations:

Wherein the second message is: RLC protocol data unit PDU.

Wherein the first message further comprises:

mapping the first multicast radio bearer to a first RLC channel;

The embodiment of the present invention further provides a processing apparatus for service transmission, which is applied to a network side device, and includes:

a first sending unit, configured to send a first message to a first terminal device, where the first message includes: first configuration information of a first downlink logical channel and a second downlink logical channel, where the first downlink logical channel is a single-pair single channel configured by a network side device for a first multicast radio bearer of the first terminal device, and the second downlink logical channel is a single-pair multi-channel configured by the network side device for the first multicast radio bearer of the first terminal device;

The embodiment of the invention also provides a terminal device, wherein the terminal device is a first terminal device and comprises a memory, a transceiver and a processor; a memory for storing a computer program; a transceiver for transceiving data under control of the processor; a processor for reading the computer program in the memory and performing the following operations:

Wherein the first message further comprises:

Wherein the second message is: RLC protocol data unit PDU.

Wherein the first message further comprises:

An embodiment of the present invention further provides a device for processing service transmission, which is applied to a first terminal device, and is characterized in that the device includes:

a first receiving unit, configured to receive a first message sent by a network side device, where the first message includes: first configuration information of a first downlink logical channel and a second downlink logical channel, where the first downlink logical channel is a single-pair single channel configured by a network side device for a first multicast radio bearer of the first terminal device, and the second downlink logical channel is a single-pair multi-channel configured by the network side device for the first multicast radio bearer of the first terminal device;

An embodiment of the present invention further provides a processor-readable storage medium, where the processor-readable storage medium stores a computer program, and the computer program is configured to cause the processor to execute the method described above.

The technical scheme of the invention at least has the following beneficial effects:

in the service transmission processing method, device, network side equipment and terminal of the embodiment of the invention, a single-to-single logical channel and a single-to-multiple logical channel are established for the multicast service of one terminal equipment, and the single-to-single logical channel and the single-to-multiple logical channel share the same radio link control RLC state variable, so that the network can flexibly realize single-multicast conversion for each terminal equipment and can reuse the automatic retransmission mechanism of the RLC for the multicast service.

Drawings

Fig. 1 illustrates a block diagram of a wireless communication system in which embodiments of the present invention are applicable;

fig. 2 is a flowchart illustrating a method for processing service transmission according to an embodiment of the present invention;

fig. 3 is a second schematic flow chart of a method for processing service transmission according to an embodiment of the present invention;

FIG. 4 is a schematic diagram of an example of a first embodiment of the present invention;

FIG. 5 is a schematic diagram of a second example provided by an embodiment of the invention;

FIG. 6 is a schematic diagram of an example III provided by an embodiment of the present invention;

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

fig. 8 is a schematic structural diagram of a processing apparatus for service transmission according to an embodiment of the present invention;

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

fig. 10 is a second schematic structural diagram of a processing apparatus for service transmission according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. 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 application.

The technical scheme provided by the embodiment of the application can be suitable for various systems, particularly 5G systems. For example, the applicable system may be a global system for mobile communication (GSM) system, a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) General Packet Radio Service (GPRS) system, a long term evolution (long term evolution, LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD) system, an LTE-a (long term evolution) system, a universal mobile system (universal mobile telecommunications system, UMTS), a Worldwide Interoperability for Mobile Access (WiMAX) system, a New Radio network (NR 5) system, etc. These various systems each include a terminal device and a network-side device. The System may further include a core network portion, such as an Evolved Packet System (EPS), a 5G System (5GS), and the like.

Fig. 1 shows a block diagram of a wireless communication system to which embodiments of the present invention are applicable. The wireless communication system includes a terminal apparatus 11 and a network-side apparatus 12. The network side device and the terminal device may each use one or more antennas to perform Multiple Input Multiple Output (MIMO) transmission, where the MIMO transmission may be Single User MIMO (SU-MIMO) or Multi-User MIMO (MU-MIMO). The MIMO transmission may be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO, or may be diversity transmission, precoding transmission, beamforming transmission, or the like, depending on the form and number of root antenna combinations.

The terminal device referred to in the embodiments of the present application may refer to a device providing voice and/or data connectivity to a user, a handheld device having a wireless connection function, or another processing device connected to a wireless modem. In different systems, the names of the terminal devices may be different, for example, in a 5G system, the terminal device may be called a User Equipment (UE). A wireless terminal device, which may be a mobile terminal device such as a mobile telephone (or "cellular" telephone) and a computer having a mobile terminal device, for example, a portable, pocket, hand-held, computer-included, or vehicle-mounted mobile device, may communicate with one or more Core Networks (CNs) via a Radio Access Network (RAN). Examples of such devices include Personal Communication Service (PCS) phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). The wireless terminal device may also be referred to as a system, a subscriber unit (subscriber unit), a subscriber station (subscriber station), a mobile station (mobile), a remote station (remote station), an access point (access point), a remote terminal device (remote terminal), an access terminal device (access terminal), a user terminal device (user terminal), a user agent (user agent), and a user device (user device), which are not limited in this embodiment of the present application.

The network side device according to the embodiment of the present application may be a base station, and the base station may include a plurality of cells for providing services for a terminal. A base station may also be referred to as an access point, or a device in an access network that communicates over the air-interface, through one or more sectors, with wireless terminal devices, or by other names, depending on the particular application. The network-side device may be configured to exchange the received air frame with an Internet Protocol (IP) packet as a router between the wireless terminal device and the rest of the access network, where the rest of the access network may include an Internet Protocol (IP) communication network. The network side device may also coordinate attribute management for the air interface. For example, the network side device according to the embodiment of the present application may be a Base Transceiver Station (BTS) in a Global System for Mobile communications (GSM) or a Code Division Multiple Access (CDMA), may also be a network side device (NodeB) in a Wideband Code Division Multiple Access (WCDMA), may also be a evolved Node B (eNB) or an e-NodeB) in a Long Term Evolution (LTE) System, may also be a 5G Base Station (gNB) in a 5G network architecture (next generation System), may also be a Home evolved Node B (Home evolved Node B, HeNB), a relay Node (relay Node), a Home Base Station (pico), and the like, and is not limited in the embodiments of the present application. In some network structures, the network side device may include a Centralized Unit (CU) node and a Distributed Unit (DU) node, and the centralized unit and the distributed unit may be geographically separated.

As shown in fig. 2, a method for processing service transmission is applied to a network device, and includes:

step 21, sending a first message to a first terminal device, where the first message includes: first configuration information of a first downlink logical channel and a second downlink logical channel, where the first downlink logical channel is a single-pair single channel configured by a network side device for a first multicast radio bearer of the first terminal device, and the second downlink logical channel is a single-pair multi-channel configured by the network side device for the first multicast radio bearer of the first terminal device;

Optionally, in the foregoing embodiment of the present invention, the first message may be an air interface RRC message. The first message further comprises:

As an optional embodiment, when the network side device wants to change the multicast service transmission mode corresponding to the first multicast radio bearer from the "multicast mode" to the "unicast mode", or vice versa, from the "unicast mode" to the "multicast mode", with respect to the first terminal device. Because the first downlink logical channel and the second downlink logical channel share the same set of RLC state variables, the RLC layer of the terminal equipment as the receiving party can equally process no matter which downlink logical channel the data packet of the multicast service is transmitted through, thereby ensuring the service continuity during the single multicast mode conversion.

In order to implement the conversion of the single multicast module, the method in the embodiment of the present invention further includes:

and sending a second message to the first terminal device, where the second message carries second indication information for indicating the first terminal device to activate or deactivate the second downlink logical channel. For example, when the current second downlink logical channel is in an activated state, the second indication information may indicate that the second downlink logical channel is deactivated; or, when the current second downlink logical channel is in the deactivated state, the second indication information may indicate that the second downlink logical channel is activated.

Wherein the second message is: RLC protocol data unit PDU.

It should be noted that, although the second message may also be implemented by air interface RRC signaling. However, in many network deployment scenarios, a module capable of generating an air interface RRC signaling, a bottom layer module capable of knowing a radio channel condition, and an RLC entity capable of knowing an RLC state variable are located in different physical entities, and in order to implement a "single multicast switching" function, the bottom layer module or the RLC entity interacts information with the module capable of generating the RRC signaling through a network interface, so that the technology is complex, and flexibility and timeliness are often poor. In the embodiment of the invention, the RLC entity and the bottom layer module for knowing the wireless channel condition are always positioned in the same physical entity, the mode that the RLC PDU carries the second message is adopted, the decision process can be directly solved through internal information interaction, and the flexibility and the timeliness are good.

As an optional embodiment, the first message further comprises:

When the first terminal device fails to successfully receive one or more RLC service data units SDU (which carry data of the first multicast radio bearer) through the second downlink logical channel, the network side device retransmits the one or more RLC SDUs to the first terminal device through the first uplink logical channel. That is, the first uplink logical channel provided in the embodiment of the present invention can implement automatic retransmission of a multicast service in AM (Acknowledged Mode).

Bearing the above example, in the embodiment of the present invention, the method further includes:

Further, in the above embodiment of the present invention, before receiving the RLC status report sent by the first terminal device through the first uplink logical channel, the method further includes:

For example, the terminal device sends an RLC status report through the first uplink logical channel immediately or when the condition is satisfied according to the third indication information. The RLC status report may be carried by an RLC PDU.

As an alternative embodiment, for one multicast service (i.e., the first multicast radio bearer), the network-side device may directly map the first multicast radio bearer to one RLC channel and map one RLC channel to two downlink logical channels (i.e., the first downlink logical channel and the second downlink logical channel), or, for one multicast service (i.e., the first multicast radio bearer), the network-side device maps the first multicast radio bearer to two RLC channels respectively and maps the two RLC channels to two downlink logical channels (i.e., the first downlink logical channel and the second downlink logical channel) respectively.

For one RLC channel, before step 21, the method further comprises:

mapping the first multicast radio bearer to a first RLC channel;

For two RLC channels, before step 21, the method further comprises:

since the first multicast radio bearer is mapped to a second RLC channel and a third RLC channel, in order to ensure that the first downlink logical channel and the second downlink logical channel share the same RLC state variable, the sending conditions of the first downlink logical channel and the second downlink logical channel can be interacted between the second RLC entity and the third RLC entity; that is, the "two downlink logical channels share the RLC state variables" is realized by the interaction between the RLC entities.

The specific details that the sending conditions of the first downlink logical channel and the second downlink logical channel can be interacted between the second RLC entity and the third RLC entity are as follows: and the second RLC entity and the third RLC entity interact the sending condition of the RLC SDU sent by each entity. That is, as for one RLC SDU or RLC SDU fragment, as long as it is transmitted by any one RLC entity, the other RLC entity also considers that the RLC SDU or RLC SDU fragment has been already transmitted to the first terminal device, so that the RLC state variable in the second RLC entity can reflect the transmission condition of the second downlink logical channel.

In summary, in the embodiment of the present invention, a single-to-single logical channel and a single-to-multiple logical channel are established for a multicast service of a terminal device, and the single-to-single logical channel and the single-to-multiple logical channel share the same RLC state variable, so that a network can flexibly implement single-multicast switching for each terminal device, and an automatic retransmission mechanism of the RLC can be reused for the multicast service.

As shown in fig. 3, an embodiment of the present invention further provides a method for processing service transmission, which is applied to a first terminal device, and includes:

step 31, receiving a first message sent by a network side device, where the first message includes: first configuration information of a first downlink logical channel and a second downlink logical channel, where the first downlink logical channel is a single-pair single channel configured by a network side device for a first multicast radio bearer of the first terminal device, and the second downlink logical channel is a single-pair multi-channel configured by the network side device for the first multicast radio bearer of the first terminal device;

And receiving data of the first multicast radio bearer, which is sent by network side equipment through the second downlink logical channel, according to bottom layer configuration information associated with the second downlink logical channel under the condition that the first indication information activates the second downlink logical channel.

and receiving a second message sent by the network side device, where the second message carries second indication information used for indicating the first terminal device to activate or deactivate the second downlink logical channel. For example, when the current second downlink logical channel is in an activated state, the second indication information may indicate that the second downlink logical channel is deactivated; or, when the current second downlink logical channel is in the deactivated state, the second indication information may indicate that the second downlink logical channel is activated.

Wherein, when the second indication information activates the second downlink logical channel, receiving, according to the bottom layer configuration information associated with the second downlink logical channel, data of the first multicast radio bearer sent by the network side device through the second downlink logical channel

Wherein the second message is: RLC protocol data unit PDU.

As an optional embodiment, the first message further comprises:

When the first terminal device fails to successfully receive one or more RLC service data units SDU (the RLC SDU carries data of the first multicast radio bearer) through the second downlink logical channel, the first terminal device informs the first terminal device of the situation through the first uplink logical channel, and then the network device retransmits the one or more RLC SDUs to the first terminal device through the first downlink logical channel. That is, the first uplink logical channel provided in the embodiment of the present invention can implement automatic retransmission of a multicast service in AM (Acknowledged Mode).

Further, in the above embodiment of the present invention, before the sending the RLC status report through the first uplink logical channel, the method further includes:

In this embodiment of the present invention, for a multicast service (i.e. the first multicast radio bearer), a network side device may directly map the first multicast radio bearer to an RLC channel, and map an RLC channel to two downlink logical channels (i.e. a first downlink logical channel and a second downlink logical channel), and accordingly, the first terminal device also needs to establish a corresponding RLC entity to process the RLC channel; or, for one multicast service (i.e. the first multicast radio bearer), the network side device maps the first multicast radio bearer to two RLC channels respectively, and maps the two RLC channels to two downlink logical channels respectively (i.e. a first downlink logical channel and a second downlink logical channel), and correspondingly, the first terminal device also needs to establish two corresponding RLC entities to process the corresponding RLC channels respectively.

For one RLC channel, after step 31, the method further comprises:

For two RLC channels, after step 31, the method further comprises:

since the first multicast radio bearer is mapped to a second RLC channel and a third RLC channel, in order to ensure that the first downlink logical channel and the second downlink logical channel share the same RLC state variable, the fifth RLC entity and the sixth RLC entity can interact with the receiving conditions of the first downlink logical channel and the second downlink logical channel; that is, the "two downlink logical channels share the RLC state variables" is realized by the interaction between the RLC entities.

The specific details that the receiving conditions of the first downlink logical channel and the second downlink logical channel can be interacted between the fifth RLC entity and the sixth RLC entity are as follows: and the fifth RLC entity and the sixth RLC entity interact the receiving condition of the RLC SDU received by each entity. That is, for one RLC SDU or RLC SDU fragment, as long as it is received by any one RLC entity, the other RLC entity also considers that the RLC SDU or RLC SDU fragment has been received as if it had been received, and thus, the RLC state variables of both parties are synchronized.

In order to more clearly describe the service transmission processing method provided by the embodiment of the present invention, the following description is made with reference to several examples.

Example one, single RLC channel implementation

As shown in fig. 4, the "two downlink logical channels share the RLC state variables" is implemented by directly mapping one RLC channel into two downlink logical channels.

Specifically, for each terminal device, the network layer device maps one radio bearer for carrying multicast service data (i.e., the first multicast radio bearer) to one RLC channel, and then further maps to one PtP downlink logical channel (i.e., the first downlink logical channel) and one PtM downlink logical channel (i.e., the second downlink logical channel). The network side device also establishes an RLC entity to process the RLC channel and establishes a sending port of the PtP downlink logical channel. There is a set of RLC state variables in the RLC entity. If the downlink PtM logical channel is not already established, the network side device also establishes a transmission port of the PtM downlink logical channel.

If there are multiple terminal devices that need to receive the multicast service data, the network side device establishes an RLC (network side) channel transmission port for each terminal device, which includes an RLC entity only for the terminal device, a PtP downlink logical channel transmission port only for the terminal device, and a PtM downlink logical channel transmission port shared by all terminals. There is one and only one set of RLC state variables for the terminal device in the RLC entities for the terminal device. The RLC state variables of different terminal devices are not shared but are independent of each other.

And the network side equipment informs the configuration to the terminal equipment through RRC signaling. The terminal device establishes a corresponding RLC entity to process the RLC channel according to the configuration information in the RRC signaling, and establishes receiving ports of the PtP downlink logical channel and the PtM downlink logical channel.

The network side device may notify the terminal device of activating or deactivating the PtM downlink logical channel through any downlink logical channel (see example four for a specific mechanism).

If RLC transmission in AM mode needs to be supported, a PtP uplink logical channel (i.e., a first uplink logical channel) for a single terminal device is also established between the network side device and the terminal device, so as to support the terminal device to feed back the receiving state of RLC SDU to the network side device (see example five for a specific mechanism).

Example two, implementation of two RLC channels, and both RLC channels maintain RLC state variables

As shown in fig. 5, by mapping the multicast service to two RLC channels, the "two downlink logical channels share the RLC state variables" is realized by the interaction between the RLC entities.

Specifically, for each radio bearer for carrying multicast service data (i.e., the first multicast radio bearer), the network-side device establishes a PtM RLC channel that is common to all terminal devices and is only used for downlink PtM transmission. The network side device establishes a common PtM RLC entity to handle the PtM RLC channel. There is a set of RLC state variables in the PtM RLC entity.

In addition, for each terminal device, the network-side device maps one radio bearer for carrying multicast service data (i.e., the first multicast radio bearer) to one PtP RLC channel and then further maps to one PtP downlink logical channel (i.e., the first downlink logical channel). The network side device also establishes a PtP RLC entity to process the PtP RLC logical channel and establishes the sending port of the PtP downlink logical channel. There is a set of RLC state variables in the PtP RLC entity. The PtP RLC channels of different terminal devices are independent of each other, but the PtP RLC entities interact with the PtM RLC entity in RLC state variables. Specifically, as for one RLC SDU or RLC SDU fragment, as long as it is transmitted by any one RLC entity, the other RLC entity also considers that the RLC SDU or RLC SDU fragment has been considered as having been transmitted to the terminal device, thereby enabling the state variable in the PtP RLC entity to reflect the transmission condition of the PtM downlink logical channel.

And the network side equipment informs the configuration to the terminal equipment through RRC signaling. The terminal device establishes a corresponding PtM RLC entity to process the PtM RLC channel, establishes a corresponding PtP RLC entity to process the PtP RLC channel, and establishes a PtP downlink logical channel and a receiving port of the PtM downlink logical channel according to configuration information in the RRC signaling. The PtP RLC entity inside the terminal device interacts with the PtM RLC entity and synchronizes RLC state variables. Specifically, for one RLC SDU or RLC SDU fragment, as long as it is received by any one RLC entity, the other RLC entity also considers that the RLC SDU or RLC SDU fragment has been received as if it had been received, and thus, the RLC state variables of both parties are synchronized.

Example three, implementation of two RLC channels, but only the PtP RLC channel maintains RLC state variables

As shown in fig. 6, by mapping the multicast service to two RLC channels, the "two downlink logical channels share the RLC state variables" is realized by the PtM RLC entity reporting the transmitted and received RLC SDUs to the PtP entity in one direction.

Specifically, for each radio bearer for carrying multicast service data (i.e., the first multicast radio bearer), the network-side device establishes a PtM RLC channel that is common to all terminal devices and is only used for downlink PtM transmission. The network side device establishes a common PtM RLC entity to handle the PtM RLC channel.

In addition, for each terminal device, the network-side device maps one radio bearer for carrying multicast service data (i.e., the first multicast radio bearer) to one PtP RLC channel and then further maps to one PtP downlink logical channel (i.e., the first downlink logical channel). The network side device also establishes a PtP RLC entity to process the PtP RLC logical channel and establishes the sending port of the PtP downlink logical channel. There is a set of RLC state variables in the PtP RLC entity.

The PtM RLC entity inside the network-side device reports the transmission status of the RLC SDU or RLC SDU fragment it transmits to the PtP RLC entity. Specifically, for one RLC SDU or RLC SDU fragment, the PtP RLC entity also considers that the RLC SDU or RLC SDU fragment has been transmitted as if it had been transmitted as transmitted by the PtM RLC entity.

And the network side equipment informs the configuration to the terminal equipment through RRC signaling. The terminal device establishes a corresponding PtM RLC entity to process the PtM RLC channel, establishes a corresponding PtP RLC entity to process the PtP RLC channel, and establishes a PtP downlink logical channel and a receiving port of the PtM downlink logical channel according to the configuration in the RRC signaling. The PtM RLC entity inside the terminal device reports the reception status of the RLC SDU or RLC SDU fragment it receives to the PtP RLC entity. Specifically, for one RLC SDU or RLC SDU fragment, the PtP RLC entity also considers that the RLC SDU or RLC SDU fragment has been received as if it had been received by the PtM RLC entity.

Example four, activation and deactivation of PtM Downlink logical channels

A terminal device requests a network to receive a multicast service. According to the pre-configuration information of the network side, the multicast service is mapped into a radio bearer.

The network configures two downlink logical channels for the terminal device and for the radio bearer of the multicast service, where one is a downlink PtP logical channel and the other is a downlink PtM logical channel. The two logical channels share the same set of RLC state variables. Optionally, if the network wishes to transmit in RLC acknowledged mode for the multicast radio bearer of the terminal device, the network may also configure an uplink PtP logical channel for the multicast radio bearer for the terminal device to feedback RLC status. The network informs the terminal equipment of the configuration through an air interface RRC message. The air interface RRC message may also carry an indication of activation or deactivation of the downlink PtM logical channel.

If a downstream PtM logical channel is active, the terminal device should receive, through the underlying configuration associated with the downstream PtM logical channel, multicast data sent by the network over the downstream PtM logical channel. Wherein the underlying configuration associated with the downstream PtM logical channel is different than the underlying configuration associated with the downstream PtP logical channel for the terminal device. For example, the MCS (Modulation and Coding Scheme) used by the bottom layer configuration associated with the downlink PtM logical channel is often a static parameter with a low code rate, but the MCS used by the bottom layer configuration associated with the downlink PtP logical channel is often dynamically adjusted according to the air interface channel condition between the base station and the user, and the code rate is usually high. In the embodiment of the present invention, the terminal device may receive most of the multicast service data required by the terminal device through the downlink PtM logical channel. Accordingly, on the network side, the network will not normally transmit data belonging to the multicast radio bearer to the terminal device via the downlink PtP logical channel unless the multicast radio bearer uses RLC acknowledged mode and the terminal device has some packets that cannot be completely received via the downlink PtM logical channel and needs to be retransmitted via the PtP logical channel.

If a downstream PtM logical channel is deactivated, then the terminal device need not receive data sent by the network over the downstream PtM logical channel via the underlying configuration associated with the downstream PtM logical channel. Accordingly, the network must transmit all data belonging to the multicast radio bearer via the above-mentioned downlink PtP logical channel. It should be noted that even if the downlink PtM logical channel is deactivated, the network side may also transmit downlink data through the downlink PtM logical channel at the same time, because one downlink PtM logical channel does not necessarily serve only one terminal device, and even if one terminal device is not suitable for receiving downlink data through the downlink PtM logical channel for some reason, the downlink PtM logical channel can still be used for transmitting multicast service data to other terminal devices.

That is, whether or not a downlink PtM logical channel is active for a terminal device substantially corresponds to whether the terminal device specifically receives multicast service data (excluding automatic retransmission) via the downlink PtM logical channel or multicast service data via the downlink PtP logical channel. In view of this, "downstream PtM logical channel activation" may be referred to as "multicast mode", and "downstream PtM logical channel deactivation" may be referred to as "unicast mode".

Further, when there is a change in the radio channel condition between the network-side device and the terminal device, the network desires to change the transmission mode of the multicast service from the "multicast mode" to the "unicast mode" or from the "unicast mode" to the "multicast mode" for the terminal device. Since the downlink PtM logical channel and the downlink PtP logical channel share the same set of RLC state variables, the RLC layer of the terminal device as the receiving party can process the multicast service packet equally no matter which logical channel the multicast service packet is transmitted through, which ensures service continuity when switching between the single multicast mode and the multicast mode.

To effect this conversion, the network sends an RLC PDU to the terminal device, which contains an indication to instruct the terminal device to activate or deactivate the downlink PtM logical channel.

For example, in the case where the downlink PtM logical channel is activated, the underlying layer reflects that the radio channel condition is significantly deteriorated, the terminal device has been unable to effectively receive the multicast service data through the downlink PtM logical channel, and the packet loss condition may be very common, and then the network expects that the terminal device does not receive the multicast service data through the downlink PtM logical channel any more. In this case, the bottom layer knowing the radio channel condition can report this condition to the decision layer, and then the decision layer instructs the RLC entity or PtP RLC entity on the network side to send an RLC control PDU through the downlink PtP logical channel, which includes an indication to instruct the terminal device to deactivate the downlink PtM logical channel.

For another example, in the case where the downlink PtM logical channel is activated and the transmission employs the AM mode, one RLC SDU or RLC SDU fragment exists among the RLC entities or PtP RLC entities on the network side and is transmitted through the air interface earlier, and has been retransmitted a plurality of times but has not been acknowledged by the terminal device. The network expects the terminal device to no longer receive multicast traffic data via the downstream PtM logical channel. In this case, the RLC entity or the PtP RLC entity on the network side transmits an RLC control PDU including an indication to instruct the terminal device to deactivate the downlink PtM logical channel through the downlink PtP logical channel.

For another example, in the case that the downlink PtM logical channel is not activated, the bottom layer reflects the improvement of the radio channel condition, and the terminal device can already effectively receive the multicast service data through the PtM logical channel, so the network expects the terminal device to receive the multicast service data through the PtM logical channel, and thus the terminal device does not need to additionally send the multicast service data to the terminal device in the "unicast mode", thereby saving air interface resources. In this case, the bottom layer knowing the radio channel condition can report this condition to the decision layer, and then the decision layer instructs the RLC entity or PtP RLC entity on the network side to send an RLC control PDU through the downlink PtP logical channel, which includes an indication to instruct the terminal device to activate the downlink PtM logical channel.

For another example, in the case that the PtM logical channel is activated, the network finds that there are few terminal devices in the cell that need to receive the multicast service data, for example, there is only one terminal device, so that the scheme of "sending the multicast service data through the PtM logical channel with a lower code rate" consumes more air interface resources than the scheme of "directly sending the multicast service data to all the terminal devices that need the PtM logical channel" respectively. In this case, the bottom layer knowing the radio channel condition can report this condition to the decision layer, and then the decision layer instructs the RLC entity or PtM RLC entity on the network side to send an RLC control PDU through the downlink PtM logical channel, which includes an indication to instruct all terminal devices to deactivate the downlink PtM logical channel.

Example five, automatic retransmission in AM mode

The network configures two downlink logical channels and one uplink logical channel for the terminal device and for the multicast radio bearer. One downlink logical channel is a downlink PtP logical channel, the other downlink logical channel is a downlink PtM logical channel, and the uplink logical channel is an uplink PtP logical channel. The two downlink logical channels share the same set of RLC state variables, and an RLC acknowledgement mode is adopted. The network informs the terminal equipment of the configuration through an air interface RRC message.

The terminal device starts receiving multicast service data through the above-described downlink PtM logical channel. The terminal device finds that some SN-numbered RLC SDUs are skipped, which affects the RLC state variables on the terminal device side. For example, the RLC entity or PtM RLC entity of the terminal device does not receive the RLC SDU with SN number 100, but receives RLC SDUs with SN numbers 101 to 150. At this time, the RLC entity or PtP RLC entity of the terminal device sets RX _ Next _ high to 151 and RX _ Next to 100. Since the RLC entity of the terminal device does not receive the RLC SDU with SN number 100 (corresponding to example one), or neither the PtP RLC entity nor PtM RLC entity of the terminal device receives the RLC SDU with SN number 100 (corresponding to examples two and three), the RLC entity or PtM RLC entity of the terminal device starts a timer for the set of RLC state variables since RX _ Next _ Highest is at least 102 and is greater than RX _ Next +1 when receiving the first RLC SDU with SN number greater than 100.

Optionally, the network includes a Polling bit field (Polling bit) in the RLC PDU sent through the downlink PtM logical channel, where the value of the Polling bit field is 1, and the Polling bit field is used to instruct the receiving end to feed back the RLC status report.

The RLC entity or PtP RLC entity of the terminal device transmits an RLC status PDU through the uplink PtP logical channel immediately or when the condition is satisfied according to the investigation bit field. Alternatively, when the timer for the set of RLC status variables expires, the RLC entity or the PtP RLC entity of the terminal equipment considers that the RLC SDU with SN of 100 has failed to receive, and transmits an RLC status PDU through the uplink PtP logical channel. This RLC status PDU includes at least the expression "RLC SDU with SN number 100 is not received".

The RLC entity or PtP RLC entity of the network receives the RLC status PDU, knows that the RLC SDU with SN number 100 is not received by the terminal device, and sets TX _ Next _ Ack for the terminal device to 100. In view of this, the RLC entity or PtP RLC entity on the network side retransmits the RLC SDU with SN number 100 to the terminal device through the above downlink PtP logical channel.

The terminal apparatus has successfully received the RLC SDU with SN number 100 transmitted through the above-described downlink PtP logical channel. Since the RLC SDUs having SN numbers 101 to 150 have been successfully received before, the RLC entity of the terminal device or the PtP RLC entity directly sets RX _ Next to 151.

Under certain conditions, the terminal device may again transmit an RLC status PDU through the uplink PtP logical channel described above, and information in the status PDU may infer that the RLC SDU with SN number 100 has been successfully received. The RLC entity or PtP RLC entity of the network receives the RLC status PDU, knows that the RLC SDU with SN number 100 has been received by the terminal device, and resets the value of TX _ Next _ Ack.

As shown in fig. 7, an embodiment of the present invention further provides a network-side device, which includes a memory 720, a transceiver 710, a processor 700; where in fig. 7, the bus architecture may include any number of interconnected buses and bridges, with various circuits being linked together, particularly one or more processors represented by processor 700 and memory represented by memory 720. 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 710 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 including wireless channels, wired channels, fiber optic cables, and the like. The processor 700 is responsible for managing the bus architecture and general processing, and the memory 720 may store data used by the processor 700 in performing operations.

The processor 700 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or a Complex Programmable Logic Device (CPLD), and may also have a multi-core architecture.

In particular, a memory 720 for storing computer programs; a transceiver 710 for transceiving data under the control of the processor; a processor 700 for reading the computer program in the memory and performing the following operations:

As an optional embodiment, the first message further comprises:

As an alternative embodiment, the processor 700 is further configured to read the computer program in the memory and perform the following operations:

As an alternative embodiment, the second message is: RLC protocol data unit PDU.

As an optional embodiment, the first message further comprises:

mapping the first multicast radio bearer to a first RLC channel;

In the embodiment of the invention, a single-pair single logic channel and a single-pair multi-logic channel are established for the multicast service of one terminal device, and the single-pair single logic channel and the single-pair multi-logic channel share the same radio link control RLC state variable, so that the network can flexibly realize single-multicast conversion for each terminal device and can reuse the automatic retransmission mechanism of the RLC for the multicast service.

The principle of the network side device provided in the embodiment of the present invention for solving the problem is similar to the method in the embodiment of the present invention, so the implementation of the network side device may refer to the implementation of the method, and the repeated points are not described again.

As shown in fig. 8, an embodiment of the present invention further provides a device for processing service transmission, which is applied to a network device, and includes:

a first sending unit 81, configured to send a first message to a first terminal device, where the first message includes: first configuration information of a first downlink logical channel and a second downlink logical channel, where the first downlink logical channel is a single-pair single channel configured by a network side device for a first multicast radio bearer of the first terminal device, and the second downlink logical channel is a single-pair multi-channel configured by the network side device for the first multicast radio bearer of the first terminal device;

As an optional embodiment, the first message further comprises:

As an alternative embodiment, the apparatus further comprises:

a second sending unit, configured to send a second message to the first terminal device, where the second message carries second indication information used to indicate the first terminal device to activate or deactivate the second downlink logical channel.

As an optional embodiment, the first message further comprises:

As an alternative embodiment, the apparatus further comprises:

a status receiving unit, configured to receive an RLC status report sent by the first terminal device through the first uplink logical channel; the RLC status report is generated by the first terminal device according to the data of the first multicast radio bearer received by the first terminal device through the second downlink logical channel;

a determining unit, configured to determine, according to the RLC status report, data of a first multicast radio bearer that is not received by the first terminal device;

a third sending unit, configured to send, to the first terminal device through the first downlink logical channel, the determined data of the first multicast radio bearer that is not received by the first terminal device.

As an alternative embodiment, the apparatus further comprises:

a fourth sending unit, configured to send RLC protocol data units to the first terminal device through the second downlink logical channel, where at least one of the RLC protocol data units includes third indication information, and the third indication information is used to indicate that the first terminal device feeds back the RLC status report.

As an alternative embodiment, the apparatus further comprises:

a first mapping unit, configured to map the first multicast radio bearer to a first RLC channel;

a second mapping unit, configured to map the first RLC channel to the first downlink logical channel and the second downlink logical channel;

a first establishing unit, configured to establish a first RLC entity configured to process the first RLC channel, a first sending port of the first downlink logical channel on the first RLC entity, and a second sending port of the second downlink logical channel on the first RLC entity; wherein the first RLC entity maintains an RLC state variable shared by the first downlink logical channel and the second downlink logical channel.

As an alternative embodiment, the apparatus further comprises:

a third mapping unit, configured to map the first multicast radio bearer to a second RLC channel and a third RLC channel;

a fourth mapping unit, configured to map the second RLC channel to the first downlink logical channel, and map the third RLC channel to the second downlink logical channel;

a second establishing unit, configured to establish a second RLC entity for processing the second RLC channel and a third sending port of the first downlink logical channel on the second RLC entity;

a third establishing unit, configured to establish a third RLC entity for processing the third RLC channel and a fourth sending port of the second downlink logical channel on the third RLC entity;

It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation. In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented as a software functional unit and sold or used as a stand-alone product, may be stored in a processor readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network-side device, etc.) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The principle of the processing device for service transmission provided in the embodiment of the present invention to solve the problem is similar to that of the method in the embodiment of the present invention, so the implementation of the device can refer to the implementation of the method, and repeated parts are not described again.

As shown in fig. 9, an embodiment of the present invention further provides a terminal device, where the terminal device is a first terminal device, and the terminal device includes a memory 920, a transceiver 910, a processor 900, and a user interface 930; in fig. 9, among other things, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by processor 900, and various circuits, represented by memory 920, 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 910 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over transmission media including wireless channels, wired channels, fiber optic cables, and the like. The user interface 930 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 900 is responsible for managing the bus architecture and general processing, and the memory 920 may store data used by the processor 600 in performing operations.

Alternatively, the processor 900 may be a CPU (central processing unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a CPLD (Complex Programmable Logic Device), and the processor may also have a multi-core architecture.

The processor is used for executing any one of the methods provided by the embodiment of the application according to the obtained executable instructions by calling the computer program stored in the memory. The processor and memory may also be physically separated.

In particular, a memory 920 for storing computer programs; a transceiver 910 for transceiving data under the control of the processor 900; a processor 900 for reading the computer program in the memory 920 and performing the following operations:

As an optional embodiment, the first message further comprises:

As an alternative embodiment, the processor 900 is further configured to read the computer program in the memory and perform the following operations:

As an optional embodiment, the first message further comprises:

The principle of the problem solving of the terminal device provided by the embodiment of the invention is similar to the method provided by the embodiment of the invention, so the implementation of the terminal can be referred to the implementation of the method, and repeated points are not repeated

As shown in fig. 10, an embodiment of the present invention further provides a processing apparatus for service transmission, which is applied to a first terminal device, and includes:

a first receiving unit 101, configured to receive a first message sent by a network side device, where the first message includes: first configuration information of a first downlink logical channel and a second downlink logical channel, where the first downlink logical channel is a single-pair single channel configured by a network side device for a first multicast radio bearer of the first terminal device, and the second downlink logical channel is a single-pair multi-channel configured by the network side device for the first multicast radio bearer of the first terminal device;

As an optional embodiment, the first message further comprises:

As an alternative embodiment, the apparatus further comprises:

a second receiving unit, configured to receive a second message sent by the network side device, where the second message carries second indication information used to indicate the first terminal device to activate or deactivate the second downlink logical channel.

As an alternative embodiment, the apparatus comprises:

a third receiving unit, configured to receive, according to bottom layer configuration information associated with the second downlink logical channel, data of the first multicast radio bearer sent by a network side device through the second downlink logical channel under a condition that the second downlink logical channel is activated.

As an optional embodiment, the first message further comprises:

As an alternative embodiment, the apparatus further comprises:

a fourth receiving unit, configured to generate an RLC status report according to the data of the first multicast radio bearer received by the first terminal device through the second downlink logical channel;

a status sending unit, configured to send the RLC status report through the first uplink logical channel, where the RLC status report at least indicates data of a first multicast radio bearer that is not received by the first terminal device.

As an alternative embodiment, the apparatus further comprises:

a fifth receiving unit, configured to receive RLC protocol data units sent by a network side device through the second downlink logical channel, where at least one of the RLC protocol data units includes third indication information, and the third indication information is used to indicate the first terminal device to feed back the RLC status report.

As an alternative embodiment, the apparatus further comprises:

a fourth establishing unit, configured to establish a fourth RLC entity for processing the first RLC channel according to the first message; wherein, the first RLC channel is a channel mapped by the first multicast radio bearer;

a fifth establishing unit, configured to establish a first receiving port of the first downlink logical channel on a fourth RLC entity and a second receiving port of the second downlink logical channel on the fourth RLC entity;

As an alternative embodiment, the apparatus further comprises:

a sixth establishing unit, configured to establish, according to the first message, a fifth RLC entity for processing a second RLC channel and a sixth RLC entity for processing a third RLC channel; the second RLC channel and the third RLC channel are channels mapped by the first multicast radio bearer respectively;

a seventh establishing unit, configured to establish a fifth RLC entity for processing the second RLC channel and a third receiving port of the first downlink logical channel on the fifth RLC entity;

an eighth establishing unit, configured to establish a sixth RLC entity configured to process the third RLC channel and a fourth receiving port of the second downlink logical channel on the sixth RLC entity;

The principle of the processing device for service transmission provided in the embodiment of the present invention to solve the problem is similar to the method in the embodiment of the present invention, so the implementation of the device can refer to the implementation of the method, and the repeated points are not repeated

An embodiment of the present invention further provides a processor-readable storage medium, where the processor-readable storage medium stores a computer program, and the computer program is configured to cause the processor to execute the steps in the method embodiment described above. The processor-readable storage medium may be any available medium or data storage device that can be accessed by a processor, including but not limited to magnetic memory (e.g., floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc.), optical memory (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor memory (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND FLASH), Solid State Disks (SSDs)), among others.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These processor-executable instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A processing method for service transmission is applied to network side equipment, and is characterized by comprising the following steps:

2. The method of claim 1, wherein the first message further comprises:

3. The method according to claim 1 or 2, characterized in that the method further comprises:

4. The method of claim 3, wherein the second message is: RLC protocol data unit PDU.

5. The method of claim 1, wherein the first message further comprises:

6. The method of claim 5, further comprising:

7. The method of claim 5, wherein before receiving the RLC status report sent by the first terminal device via the first uplink logical channel, the method further comprises:

8. The method of claim 1, wherein prior to sending the first message to the first terminal device, the method further comprises:

mapping the first multicast radio bearer to a first RLC channel;

9. The method of claim 1, wherein prior to sending the first message to the first terminal device, the method further comprises:

10. A method for processing service transmission is applied to a first terminal device, and is characterized by comprising the following steps:

11. The method of claim 10, wherein the first message further comprises:

12. The method according to claim 10 or 11, characterized in that the method further comprises:

13. The method of claim 12, wherein the second message is: RLC protocol data unit PDU.

14. The method of claim 12, wherein the method comprises:

15. The method of claim 10, wherein the first message further comprises:

16. The method of claim 15, further comprising:

17. The method of claim 16, wherein before the sending the RLC status report over the first uplink logical channel, the method further comprises:

18. The method of claim 10, wherein after receiving the first message sent by the network-side device, the method further comprises:

19. The method of claim 10, wherein after receiving the first message sent by the network-side device, the method further comprises:

20. A network-side device, comprising a memory, a transceiver, a processor; a memory for storing a computer program; a transceiver for transceiving data under control of the processor; a processor for reading the computer program in the memory and performing the following operations:

21. The network-side device of claim 20, wherein the first message further comprises:

22. The network-side device of claim 20 or 21, wherein the processor is further configured to read the computer program in the memory and perform the following operations:

23. The network-side device of claim 22, wherein the second message is: RLC protocol data unit PDU.

24. The network-side device of claim 20, wherein the first message further comprises:

25. The network-side device of claim 20, wherein the processor is further configured to read the computer program in the memory and perform the following operations:

26. The network-side device of claim 24, wherein the processor is further configured to read the computer program in the memory and perform the following operations:

27. The network-side device of claim 20, wherein the processor is further configured to read the computer program in the memory and perform the following operations:

mapping the first multicast radio bearer to a first RLC channel;

28. The network-side device of claim 20, wherein the processor is further configured to read the computer program in the memory and perform the following operations:

29. A processing device for service transmission is applied to a network side device, and is characterized by comprising:

30. A terminal device is a first terminal device and is characterized by comprising a memory, a transceiver and a processor; a memory for storing a computer program; a transceiver for transceiving data under control of the processor; a processor for reading the computer program in the memory and performing the following operations:

31. The terminal device of claim 30, wherein the first message further comprises:

32. A terminal device according to claim 30 or 31, wherein the processor is further configured to read the computer program in the memory and perform the following operations:

33. The terminal device of claim 32, wherein the second message is: RLC protocol data unit PDU.

34. The terminal device of claim 32, wherein the processor is further configured to read the computer program in the memory and perform the following operations:

35. The terminal device of claim 30, wherein the first message further comprises:

36. The terminal device of claim 35, wherein the processor is further configured to read the computer program in the memory and perform the following operations:

37. The terminal device of claim 36, wherein the processor is further configured to read the computer program in the memory and perform the following operations:

38. The terminal device of claim 30, wherein the processor is further configured to read the computer program in the memory and perform the following operations:

39. The terminal device of claim 30, wherein the processor is further configured to read the computer program in the memory and perform the following operations:

40. A processing device for service transmission, applied to a first terminal device, includes:

41. A processor-readable storage medium, wherein the processor-readable storage medium stores a computer program for causing a processor to perform the method of any one of claims 1 to 9; alternatively, the computer program is for causing the processor to perform the method of any of claims 10 to 19.