CN113556687B

CN113556687B - Method and equipment used for wireless communication

Info

Publication number: CN113556687B
Application number: CN202010325310.6A
Authority: CN
Inventors: 张晓博
Original assignee: Shanghai Langbo Communication Technology Co Ltd
Current assignee: Shanghai Langbo Communication Technology Co Ltd
Priority date: 2020-04-23
Filing date: 2020-04-23
Publication date: 2022-09-27
Anticipated expiration: 2040-04-23
Also published as: CN113556687A

Abstract

A method and apparatus for wireless communication includes receiving a first service over a first radio bearer; receiving a first signaling and sending a first report; receiving the first traffic over at least the latter of both the first radio bearer and the second radio bearer; wherein the first report is transmitted when a first condition is satisfied; the first condition comprises a transition of reception of the first traffic from the first radio bearer to the second radio bearer; the first radio bearer and the second radio bearer are different in bearer type, and the bearer type comprises a non-unicast bearer and a unicast bearer; the first report is used to indicate SDUs related to the first service and received over the first radio bearer, the first report being higher layer control information. By reasonably determining the radio bearer and sending the first report, the packet loss rate is reduced, the interruption is reduced, and the reliability is improved.

Description

Method and equipment used for wireless communication

Technical Field

The present invention relates to a transmission method and apparatus in a wireless communication system, and more particularly, to a transmission method and apparatus for improving system efficiency, optimizing resource utilization, reducing service interruption, improving service continuity, and enhancing reliability in wireless communication.

Background

In the future, the application scenes of the wireless communication system are more and more diversified, and different application scenes put different performance requirements on the system. In order to meet different performance requirements of multiple application scenarios, research on New Radio interface (NR) technology (or Fifth Generation, 5G) is decided on 3GPP (3rd Generation Partner Project) RAN (Radio Access Network) #72 bunions, and Work on NR is started on WI (Work Item) that has passed NR on 3GPP RAN #75 bunions.

In communication, both LTE (Long Term Evolution) and 5G NR relate to accurate reception of reliable information, optimized energy efficiency ratio, determination of information validity, flexible resource allocation, the scalable system structure, high-efficiency non-access stratum information processing, low service interruption and disconnection rate, for low power support, which is for normal communication of base stations and user equipments, for reasonable scheduling of resources, the method has important significance for balancing system load, can be said to be high throughput rate, meets Communication requirements of various services, improves spectrum utilization rate, and improves the quality of service, and is essential for eMBBs (enhanced Mobile BroadBand), URLLC (Ultra Reliable Low Latency Communication) or eMTCs (enhanced Machine Type Communication). Meanwhile, in the Internet of Things in the field of the IIoT (Industrial Internet of Things), in V2X (Vehicular to X), in communication between devices (Device to Device), in communication of unlicensed spectrum, in user communication quality monitoring, in Network planning optimization, in NTN (Non terrestrial Network communication), in TN (terrestrial Network communication), in a Dual connectivity (Dual connectivity) system, in a mixture of the above various communication modes, in radio resource management and codebook selection of multiple antennas, in signaling design, neighborhood management, traffic management, and in beamforming, there is a wide demand for transmission of information, which is divided into broadcast and unicast, and both transmission modes are indispensable for a 5G system, because they help to meet the above demand.

With the continuous increase of the scenes and the complexity of the system, higher requirements are put forward on the reduction of the interruption rate, the reduction of the time delay, the enhancement of the reliability, the enhancement of the stability of the system, the flexibility of the service and the saving of the power, and meanwhile, the compatibility among different versions of different systems needs to be considered when the system is designed.

Disclosure of Invention

In a plurality of communication scenarios, especially in a wireless network supporting broadcast multicast, it relates to configuring a radio bearer for a user for a specific service, where the configured radio bearer may be a unicast bearer and a non-unicast bearer, and may be a non-unicast bearer in one cell, or may be a unicast bearer in another cell, and may be configured as a unicast bearer at a certain time or a non-unicast bearer at another time, so that flexibility of the network and flexibility of resource allocation may be greatly increased, and simultaneously, system resources may be saved, which is an important technical content of 5G broadcast multicast. However, such a configuration may encounter a series of problems, namely how and when to configure what radio bearer, how to perform handover when a user moves between different cells, if the type of radio bearer is different, what auxiliary method is needed to perform appropriate handover and selection to reduce data interruption; similar problems exist when the type of radio bearer changes within a cell. Non-unicast bearers, i.e. broadcast or multicast bearers, may be very different from unicast bearers, i.e. for a cell, a small area, or for a large area, where there are many users in the area, and thus such bearers are difficult to take into account each user, the serving cell does not even know which users are receiving or using non-unicast bearers, and thus does not have context information for these users, and therefore it is difficult to perform optimization and involvement for each specific user like unicast bearers, and mishandling may cause a loss of interruption of data reception, and if the same service is used in one cell and in another non-unicast bearer, transmission in both cells may occur, and even if the same service is used, it may not be synchronized, e.g. one transmission is fast and one transmission is slow, one transmission is many, one transport is less and therefore when switching from one bearer to another different type of bearer, it can cause interruption or even permanent loss of data transmission, resulting in a degradation of user experience and a degradation of network performance.

In view of the above, the present application provides a solution.

It should be noted that, in the case of no conflict, the embodiments and features in the embodiments in any node of the present application may be applied to any other node. The embodiments and features of the embodiments of the present application may be combined with each other arbitrarily without conflict.

The application discloses a method in a first node used for wireless communication, comprising:

receiving a first service through a first radio bearer; receiving a first signaling, wherein the first signaling indicates that a second radio bearer of the first service is established;

sending a first report;

receiving the first traffic over at least the latter of both the first radio bearer and the second radio bearer;

wherein the first report is transmitted when a first condition is satisfied; the first condition comprises a transition of reception of the first traffic from the first radio bearer to the second radio bearer; the first radio bearer and the second radio bearer are different in bearer type, and the bearer type includes a non-unicast bearer and a unicast bearer; the first report is used to indicate SDUs related to the first service and received over the first radio bearer, the first report being higher layer control information.

As an embodiment, the problem to be solved by the present application includes: when a radio bearer for transmitting services such as broadcast multicast is switched between a non-unicast bearer and a unicast bearer, especially from the non-unicast bearer to the unicast bearer, the non-unicast bearer and the unicast bearer are very different from each other, and the configuration mode, the service capability, the resource allocation, the bearer management, the user management, the establishment and the release may be different from each other. The first report is sent and simultaneously skillfully associated with the first radio bearer and the second radio bearer, so that the base station has enough information to correctly send data, and the problems are solved.

As an example, the benefits of the above method include: by receiving the first signaling, the user can establish a second radio bearer by the user and switch the reception of the service to the second radio bearer, and the transmission of the service is also switched to the second radio bearer, and at such time interval, the user informs the serving cell of the situation that the service receives through the first radio bearer by generating a first report, and the situation is taken as the start of the reception of the second radio bearer, so that the service can be seamlessly switched between two completely different bearers, and when the user establishes the second radio bearer and switches the service from the first radio bearer to the second radio bearer, the service can be continuously received as soon as possible, thereby avoiding the interruption of data and being beneficial to reducing time delay. In addition, the method proposed by the present application is advantageous in terms of complexity, unlike other additional steps.

Specifically, according to an aspect of the present invention, the first report is RRC signaling, and the first report includes a first identifier, which is used to determine a PDCP SDU related to the first service and received after a first missing PDCP SDU carried by the first radio bearer.

Specifically, according to an aspect of the present invention, the first report is RRC signaling, and the first report includes a second identifier, which is used to determine a first time window, where the first time window is a time window corresponding to a last SDU received through the first radio bearer and related to the first service.

Specifically, according to an aspect of the present invention, the first report is a PDCP status report, the first state variable group is a subset of a set of all state variables of the PDCP entity associated with the second radio bearer, and the first signaling indicates that a value of a state variable in the first state variable group is determined by a value of a state variable of the PDCP entity associated with the first radio bearer; the first transmitter generates the first report according to the PDCP entity associated with the second radio bearer, and the first transmitter transmits the first report through a radio bearer of which the bearer type is a unicast bearer among the first radio bearer and the second radio bearer.

Specifically, according to an aspect of the present invention, the first report is a PDCP status report, the first transmitter generates the first report according to a PDCP entity associated with the first radio bearer, and the first transmitter transmits the first report through a radio bearer of which the bearer type is a unicast bearer, among the first radio bearer and the second radio bearer.

Specifically, according to one aspect of the present invention, the method comprises:

the first receiver receives a second signaling;

the second signaling indicates that the transmission of the first traffic is switched from the first radio bearer to the second radio bearer.

the first transmitter transmits first information, the first information being used to trigger the first signaling.

the first receiver receives a first set of data over the first and second radio bearers, respectively, the first report being used to determine that the first set of data was sent over the second radio bearer.

As an embodiment, the characteristics of the above method include: RRC is Radio Resource Control (Radio Resource Control).

As an embodiment, the characteristics of the above method include: PDCP is a Packet Data Convergence Protocol (Packet Data Convergence Protocol).

As an embodiment, the characteristics of the above method include: an SDU is a Service Data Unit (Service Data Unit).

Specifically, according to an aspect of the present application, the first node is a user equipment.

Specifically, according to an aspect of the present application, the first node is an internet of things terminal.

Specifically, according to an aspect of the present application, the first node is a relay.

Specifically, according to an aspect of the present application, the first node is a vehicle-mounted terminal.

In particular, according to one aspect of the application, the first node is an aircraft.

The application discloses a method in a second node used for wireless communication, comprising:

sending a first signaling, wherein the first signaling indicates to establish a second radio bearer of a first service; the first service is sent over a first radio bearer;

receiving a first report;

a receiver of the first signaling receives the first traffic over at least the latter of both the first radio bearer and the second radio bearer;

wherein a recipient of the first signaling sends the first report when a first condition is satisfied; the first condition comprises a transition of reception of the first traffic from the first radio bearer to the second radio bearer; the first radio bearer and the second radio bearer are different in bearer type, and the bearer type includes a non-unicast bearer and a unicast bearer; the first report is used to indicate SDUs related to the first service and received over the first radio bearer, the first report being higher layer control information.

Specifically, according to an aspect of the present invention, the first report is a PDCP status report, the first state variable group is a subset of a set of all state variables of the PDCP entity associated with the second radio bearer, and the first signaling indicates that a value of a state variable in the first state variable group is determined by a value of a state variable of the PDCP entity associated with the first radio bearer; a sender of the first report generates the first report according to the PDCP entity associated with the second radio bearer, and the sender of the first report sends the first report through a radio bearer of which the bearer type is a unicast bearer in the first radio bearer and the second radio bearer.

Specifically, according to an aspect of the present invention, the first report is a PDCP status report, the sender of the first report generates the first report according to a PDCP entity associated with the first radio bearer, and the sender of the first report sends the first report through a radio bearer of which the bearer type is a unicast bearer, among the first radio bearer and the second radio bearer.

Specifically, according to one aspect of the present invention, comprises:

the second transmitter is used for transmitting a second signaling;

the second receiver receives first information, which is used to trigger the first signaling.

the second transmitter transmits a first set of data over the first and second radio bearers, respectively, the first report being used to determine that the first set of data is transmitted over the second radio bearer.

Specifically, according to an aspect of the present application, the second node is a base station.

In particular, according to an aspect of the present application, the second node is a relay.

Specifically, according to an aspect of the present application, the second node is a vehicle-mounted terminal.

In particular, according to one aspect of the application, the second node is an aircraft.

In particular, according to an aspect of the present application, the second node is a group header.

In particular, according to an aspect of the present application, the second node is a satellite.

The application discloses a first node to be used for wireless communication, comprising:

a first receiver for receiving a first service through a first radio bearer; receiving a first signaling, wherein the first signaling indicates to establish a second radio bearer of the first service;

a first transmitter to transmit a first report;

the first receiver receiving the first traffic over at least the latter of the first radio bearer and the second radio bearer;

wherein the first transmitter transmits the first report when a first condition is satisfied; the first condition comprises a transition of reception of the first traffic from the first radio bearer to the second radio bearer; the first radio bearer and the second radio bearer are different in bearer type, and the bearer type includes a non-unicast bearer and a unicast bearer; the first report is used to indicate SDUs related to the first service and received over the first radio bearer, the first report being higher layer control information.

The application discloses a second node for wireless communication, comprising:

the second transmitter is used for transmitting a first signaling, and the first signaling indicates to establish a second radio bearer of the first service; the first service is sent over a first radio bearer;

a second receiver to receive the first report;

As an example, compared with the conventional scheme, the method has the following advantages:

when a user goes from a cell transmitting broadcast multicast service through a non-unicast bearer to a cell transmitting broadcast multicast service through a unicast bearer, or when a cell transmitting broadcast multicast service through a non-unicast bearer is converted into a cell transmitting the same service through a unicast bearer, the problem of data loss or even interruption in the conversion process is faced. Since the network may not maintain the user context in a cell using non-unicast bearer, and the non-unicast bearer does not support the feedback of the ue, it is difficult for the serving cell to know the user reception. When the bearer type of the serving cell is changed, the data received by each user may be different, and if a new independent unicast bearer is directly established according to a conventional method, it is difficult to avoid data loss. When the user is handed over, especially when the use condition is switched, the time for switching the user is not determined, because the switching is decided by the user, and therefore, the service cell is more difficult to grasp the acceptance condition of the user. When a user enters a new cell, or when the cell needs to receive data using a unicast bearer, it refers to data that would have been transmitted using a non-unicast bearer before the newly established bearer was enabled to be engaged. The present application solves the above problems by utilizing a first report and associating it with a first radio bearer and a second radio bearer to provide sufficient information for a serving cell, thereby avoiding the problems associated with conventional approaches. In addition, the method provided by the application can provide a solution for configuring completely different conversion from non-unicast to unicast bearing, has wide applicability and flexibility, and is beneficial to improving the utilization rate of resources and improving the service quality.

when a user moves from a cell transmitting broadcast multicast service through unicast bearer to a cell transmitting broadcast multicast service through non-unicast bearer, or when a cell transmitting broadcast multicast service through unicast bearer is converted into non-unicast bearer to transmit the same service, the problem of data loss or even interruption in the conversion process can be faced. When a plurality of unicast users receive the same broadcast multicast service, due to differences in channel characteristics, resource allocation, device capability, priority, etc. of each user, service transmission conditions are different, data of some users is still in the cache of the serving cell, data of some users is already transmitted to the user side, and when the unicast service is uniformly converted into a non-unicast bearer, it is likely that some users, for example, users with slow reception, do not receive enough data, thereby causing a decrease in reception quality. This is an unsolved problem encountered by the conventional method. According to the method and the device, comprehensive judgment is carried out by utilizing the first report generated by each user, enough information is provided for the service cell to set the non-unicast bearer, the configured non-unicast bearer and subsequent data transmission can take account of the data receiving conditions of all the unicast users before, so that the problems are solved, and the problems caused by the traditional method are avoided.

Drawings

Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof with reference to the accompanying drawings in which:

fig. 1 shows a flow chart of receiving first signaling and sending a first report according to an embodiment of the application;

FIG. 2 shows a schematic diagram of a network architecture according to an embodiment of the present application;

figure 3 shows a schematic diagram of an embodiment of a radio protocol architecture for the user plane and the control plane according to an embodiment of the present application;

FIG. 4 shows a schematic diagram of a first node, a second node, according to an embodiment of the present application;

FIG. 5 shows a flow diagram of a transmission according to an embodiment of the present application;

FIG. 6 shows a flow diagram of a transmission according to an embodiment of the present application;

FIG. 7 shows a flow diagram of a transmission according to an embodiment of the present application;

FIG. 8 shows a schematic diagram of a first time window according to an embodiment of the present application;

figure 9 illustrates a schematic diagram of a first report being used to determine that a first set of data is transmitted over a second radio bearer according to an embodiment of the present application;

fig. 10 illustrates a schematic diagram of a first report being used to indicate SDUs related to a first service and received over a first radio bearer according to an embodiment of the present application;

figure 11 illustrates a schematic diagram of a processing apparatus for use in a first node according to one embodiment of the present application;

fig. 12 illustrates a schematic diagram of a processing device for use in a second node according to an embodiment of the application.

Detailed Description

The technical solutions of the present application will be further described in detail with reference to the accompanying drawings, and it should be noted that the embodiments and features of the embodiments in the present application can be arbitrarily combined with each other without conflict.

Example 1

Embodiment 1 illustrates a flow chart of receiving first signaling and sending a first report according to an embodiment of the present application, as shown in fig. 1. In fig. 1, each block represents a step, and it is particularly emphasized that the sequence of the blocks in the figure does not represent a chronological relationship between the represented steps.

In embodiment 1, a first node in the present application receives a first signaling in step 101; sending a first report in step 102;

the first node receives a first service through a first radio bearer; the first signaling instruction establishes a second radio bearer of the first service; the first node receiving the first traffic over at least the latter of both the first radio bearer and the second radio bearer; wherein the first node sends the first report when a first condition is met; the first condition comprises a transition of reception of the first traffic from the first radio bearer to the second radio bearer; the first radio bearer and the second radio bearer are different in bearer type, and the bearer type includes a non-unicast bearer and a unicast bearer; the first report is used to indicate SDUs related to the first service and received over the first radio bearer, the first report being higher layer control information.

As an embodiment, the first node is a UE (User Equipment).

As one embodiment, the first signaling includes control plane control information.

As an embodiment, the first signaling includes user plane control information.

As one embodiment, the first signaling comprises RRC signaling.

As an embodiment, the first signaling includes MAC CE (Medium Access Control Element) signaling.

As an embodiment, the first signaling includes DCI (Downlink Control Information) signaling.

As one embodiment, the first signaling includes PDCP control information.

As an embodiment, the first signaling includes rlc (radio Link control) control information.

As an embodiment, the first signaling comprises a rrcreeconfiguration message.

As an embodiment, the first signaling comprises an RRCConnectionReconfiguration message.

As an embodiment, the first signaling comprises a SCPTMConfiguration message.

As an embodiment, the first signaling includes an SIB (System Information Block).

For one embodiment, the first signaling includes SIB 1.

For one embodiment, the first signaling includes SIB 14.

For one embodiment, the first signaling comprises SIB 15.

For one embodiment, the first signaling includes SIB 16.

For one embodiment, the first signaling includes SIB 17.

For one embodiment, the first signaling includes SIB 18.

For one embodiment, the first signaling includes SIB 19.

For one embodiment, the first signaling includes SIB 20.

As an embodiment, the first signaling is transmitted in a broadcast manner.

As an embodiment, the logical Channel occupied by the first signaling includes a BCCH (Broadcast Control Channel).

As an embodiment, the logical Channel occupied by the first signaling includes an MCCH (Multicast Control Channel).

As an embodiment, the logical Channel occupied by the first signaling includes an SC-MCCH (Single Cell Multicast Control Channel).

As an embodiment, the logical Channel occupied by the first signaling includes a Common Control Channel (CCCH).

As an embodiment, the first signaling is sent in a unicast manner.

As an embodiment, the logical Channel occupied by the first signaling includes a DCCH (Dedicated Control Channel).

As an embodiment, the physical channel occupied by the first signaling includes pdsch (physical Downlink Shared channel).

As an embodiment, the first Radio Bearer is an MRB (Multicast Bearer).

As an embodiment, the first Radio Bearer is a SC-MRB (Single Cell Multicast Radio Bearer).

As an embodiment, the first radio bearer is an SC-PTM MRB (Single Cell Point to Multipoint multicast bearer).

As one embodiment, the first Radio bearer is a drb (data Radio bearer).

As an embodiment, the second Radio Bearer is an MRB (Multicast Bearer).

As an embodiment, the second Radio Bearer is an SC-MRB (Single Cell Multicast Radio Bearer).

As an embodiment, the second radio bearer is a SC-PTM MRB (Single Cell Point to Multipoint multicast bearer).

For one embodiment, the second Radio bearer is a drb (data Radio bearer).

As an embodiment, the non-unicast bearer comprises MRB, SC-PTM MRB, DRB indicated as multicast.

As one embodiment, the unicast bearer includes a DRB that is not indicated as multicast.

As an embodiment, the first node receives the first traffic through the first radio bearer and the second radio bearer.

As an embodiment, the first node receives the first service through the first radio bearer, and then through the first radio bearer and the second radio bearer.

As an embodiment, the first node receives the first service through the first radio bearer first and then through the second radio bearer.

For one embodiment, the first service includes a broadcast service.

In one embodiment, the first service includes a multicast service.

As an embodiment, the first Service includes MBS (Multicast/Broadcast Service) Service.

As an embodiment, the first Service includes an MBMS (Multicast/Broadcast Multimedia Service) Service.

As an embodiment, the first Service includes an eMBMS (enhanced Multicast/Broadcast Multimedia Service) Service.

As an embodiment, the first Service includes a mbms (Multicast Broadcast Multimedia Service, further enhanced Multicast Broadcast Multimedia Service) Service.

As an embodiment, the first Service includes a feffembms (Multicast Broadcast Multimedia Service, further enhanced Multicast Broadcast Multimedia Service) Service.

As an embodiment, the first service includes at least one MBS session (session).

As an embodiment, the first service includes a Broadcast communication service (Broadcast communication service).

As an embodiment, the first service includes a Multicast communication service (Multicast communication service).

As an embodiment, the first service includes at least one MBS flow (MBS flow) transmission.

As an embodiment, the first service includes a PDU session.

As an embodiment, the first service includes MBS PDU session.

As an embodiment, the first service includes an MBMS PDU session.

As an embodiment, MBS Flow (MBS Flow) included in the first service is mapped to the first radio bearer.

As an embodiment, an MBS Flow (MBS Flow) included in the first service is associated with the first radio bearer.

As an embodiment, the first radio bearer is used for transmitting MBS Flow (MBS Flow) included by the first service.

As an embodiment, the first traffic comprises at least one QoS flow (MBS flow) transmission.

As an embodiment, QoS Flow (MBS Flow) included in the first service is mapped onto the first radio bearer.

As an embodiment, a QoS Flow (MBS Flow) included by the first traffic is associated with the first radio bearer.

As an embodiment, the first radio bearer is used for transmitting QoS Flow (MBS Flow) included by the first traffic.

As an embodiment, MBS Flow (MBS Flow) included in the first service is mapped to the second radio bearer.

As an embodiment, MBS Flow (MBS Flow) included in the first service is associated with the second radio bearer.

As an embodiment, the second radio bearer is used for transmitting MBS Flow (MBS Flow) included in the first service.

As an embodiment, QoS Flow (MBS Flow) included in the first service is mapped to the second radio bearer.

As an embodiment, a QoS Flow (MBS Flow) included by the first traffic is associated with the second radio bearer.

As an embodiment, the second radio bearer is used for transmitting QoS Flow (MBS Flow) included by the first traffic.

As an embodiment, the first node receives, through at least the latter one of the first radio bearer and the second radio bearer, an MBS stream corresponding to the first service.

As an embodiment, the first node is connected to a 5G core network (5 GC).

As an embodiment, the first node is connected to an EN-DC core network.

As an embodiment, the first node is served by a first cell and a second cell, when the serving cell of the first node is the first cell, the first node receives the first service through the first radio bearer, and when the serving cell of the first node is the second cell, the first node receives the first service through the second radio bearer.

As a sub-embodiment of this embodiment, the first node is handed over from the first cell to the second cell.

As a sub-embodiment of this embodiment, the first node is conditionally handed over from the first cell to the second cell.

As a sub-embodiment of this embodiment, the first node reselects from the first cell to the second cell.

As a sub-embodiment of this embodiment, the first signaling is used to indicate that the serving cell of the first node is changed from the first cell to the second cell.

As an embodiment, the serving cell of the first node is a third cell, the third cell uses the first radio bearer to transmit the first service in a first time period, and the third cell uses the second radio bearer to transmit the first service in a second time period.

As a sub-embodiment of this embodiment, the first time period and the second time period are orthogonal in the time domain.

In one embodiment, the first radio bearer is a non-unicast bearer and the second radio bearer is a unicast bearer.

In one embodiment, the first radio bearer is a unicast bearer and the second radio bearer is a non-unicast bearer.

As an embodiment, the first report is control information of a control plane.

As an embodiment, the first report is control information of a user plane.

As an embodiment, the first report includes RRC signaling.

As an embodiment, the first report includes MAC CE (Medium Access Control Element) signaling.

As one embodiment, the first report includes PDCP control information.

As an embodiment, the first report includes rlc (radio Link control) control information.

As an embodiment, the first Report includes a PDCP Status Report.

As an embodiment, the first report includes rrcreconconfigurationcomplete.

As an embodiment, the first report includes rrcconnectionreconfiguration complete.

For one embodiment, the first report includes a RRCSetupRequest.

As one embodiment, the first report includes RRCConnectionSetupRequest.

For one embodiment, the first report includes a RRCResumeRequest.

For one embodiment, the first report includes an rrcconnectionresumerrequest.

For one embodiment, the first report includes RRCResumeRequest 1.

For one embodiment, the first report includes rrcconnectionresumerrequest 1.

For one embodiment, the first report includes a RRCReestablishmentRequest.

For one embodiment, the first report includes an rrcconnectionreestablishinrequest.

As one embodiment, the first report includes mbmsinterrestindication.

As an embodiment, the first report includes ueAssistanceInformation.

For one embodiment, the first report includes dedicatedSIBRequest-r 16.

As one embodiment, the first report includes ueInformationResponse-r 16.

As one embodiment, the first report includes ueAscistationInformationEUTRA-r 16.

For one embodiment, the first report includes MBMSIntestrIndication-r 17.

For one embodiment, the first report includes ueAscistationinformation-r 17.

As an embodiment, the logical channel occupied by the first report includes a DCCH.

For one embodiment, the logical channel occupied by the first report includes a CCCH.

As an embodiment, the Physical Channel occupied by the first report includes a PUSCH (Physical Uplink Shared Channel).

As an embodiment, the first signaling indicates that the transmission of the first traffic is switched from the first radio bearer to the second radio bearer.

As an embodiment, the first signaling indicates that the QoS flow included by the first traffic changes from being associated with the PDCP entity associated with the first radio bearer to being associated with the PDCP entity associated with the second radio bearer.

As an embodiment, the first signaling indicates that the mapped QoS flow of the second radio bearer includes a QoS flow included by the first traffic.

As an embodiment, the first signaling indicates, by an SDAP-Config cell, that the QoS flow of the first traffic is added to the mapped QoS flow of the second radio bearer.

As an embodiment, the first signaling indicates that the QoS flow of the first traffic is added to the mapped QoS flow of the second radio bearer through a mappedQoS-flowtoadd cell.

As an embodiment, the sentence "the first signaling indicates establishment of the second radio bearer for the first service" includes the following meanings: the first signaling indicates establishment of the second radio bearer.

As an embodiment, the sentence "the first signaling indicates establishment of the second radio bearer for the first service" includes the following meanings: the second radio bearer is an existing radio bearer, and the first signaling indicates that the QoS flow of the first traffic is mapped to the second radio bearer.

As an embodiment, the first signaling indicates that the transmission of the first service is switched from the second radio bearer to the first radio bearer.

As an embodiment, the first signaling indicates that the QoS flow included by the first traffic changes from being associated with the PDCP entity associated with the second radio bearer to being associated with the PDCP entity associated with the first radio bearer.

As an embodiment, the first signaling indicates that the mapped QoS flow of the first radio bearer includes a QoS flow included by the first traffic.

As an embodiment, the first signaling indicates, by an SDAP-Config cell, that the QoS flow of the first traffic is added to the mapped QoS flow of the first radio bearer.

As an embodiment, the first signaling indicates, through a mappedQoS-flowtoadd cell, that the QoS flow of the first traffic is added to the mapped QoS flow of the first radio bearer.

As an embodiment, the first signaling indicates that the QoS flow of the first traffic is released from the mapped QoS flow of the first radio bearer through a mappedQoS-flowtorelease cell.

As an embodiment, the first signaling indicates to release the first radio bearer.

As an embodiment, the first signaling indicates to release mapping of the first radio bearer and the QoS flow of the first traffic.

As an embodiment, the first signaling indicates that the second radio bearer is released.

As an embodiment, the first signaling indicates to release mapping of the second radio bearer and the QoS flow of the first traffic.

As an embodiment, the first condition includes the reception of the first traffic being switched from the first radio bearer to the second radio bearer.

As an example, the sentence "the first condition includes a transition of the reception of the first traffic from the first radio bearer to the second radio bearer" includes the following meanings: and the first node receives the first service through the second radio bearer.

As an embodiment, the sentence "the first condition includes that the reception of the first service is converted from the first radio bearer to the second radio bearer" includes the following meaning: the first node starts receiving the first traffic over the second radio bearer.

As an example, the sentence "the first condition includes a transition of the reception of the first traffic from the first radio bearer to the second radio bearer" includes the following meanings: the second radio bearer is established.

As an example, the sentence "the first condition includes a transition of the reception of the first traffic from the first radio bearer to the second radio bearer" includes the following meanings: a PDCP entity associated with the second radio bearer is established.

As an example, the sentence "the first condition includes a transition of the reception of the first traffic from the first radio bearer to the second radio bearer" includes the following meanings: a PDCP entity of the second radio bearer is established.

As an embodiment, the sentence "the first condition includes that the reception of the first service is converted from the first radio bearer to the second radio bearer" includes the following meaning: the first radio bearer is determined as a secondary bearer and the first radio bearer is determined as a primary bearer.

As an embodiment, the sentence "the first condition includes that the reception of the first service is converted from the first radio bearer to the second radio bearer" includes the following meaning: the first node receiving an explicit indication that reception of the first traffic is to be switched from the first radio bearer to the second radio bearer.

As an example, the sentence "the first condition includes a transition of the reception of the first traffic from the first radio bearer to the second radio bearer" includes the following meanings: stopping receiving the first service from the first radio bearer and starting receiving the first service from the second radio bearer.

As an embodiment, the sentence "the first condition includes that the reception of the first service is converted from the first radio bearer to the second radio bearer" includes the following meaning: ceasing to receive the first traffic from the first radio bearer, the second radio bearer having been established.

As an example, the sentence "the first condition includes a transition of the reception of the first traffic from the first radio bearer to the second radio bearer" includes the following meanings: stopping receiving the first traffic from the first radio bearer, the PDCP entity of the second radio bearer having been established.

As an embodiment, the sentence "the first condition includes that the reception of the first service is converted from the first radio bearer to the second radio bearer" includes the following meaning: the first node requests to receive the first service over the second radio bearer.

As an example, the sentence "the first condition includes a transition of the reception of the first traffic from the first radio bearer to the second radio bearer" includes the following meanings: the first node receives the first service by a non-unicast bearer, and a serving cell of the first node indicates that the first service needs to be received by using a unicast bearer.

Example 2

Embodiment 2 illustrates a schematic diagram of a network architecture according to the present application, as shown in fig. 2.

Fig. 2 illustrates a diagram of a network architecture 200 for 5G NR, LTE (Long-Term Evolution), and LTE-a (Long-Term Evolution-enhanced) systems. The 5G NR or LTE network architecture 200 may be referred to as a 5GS (5G System)/EPS (Evolved Packet System) 200 or some other suitable terminology. The 5GS/EPS 200 may include one or more UEs (User Equipment) 201, NG-RANs (next generation radio access networks) 202, 5 GCs (5G Core networks )/EPCs (Evolved Packet cores) 210, HSS (Home Subscriber Server)/UDMs (Unified Data Management) 220, and internet services 230. The 5GS/EPS may interconnect with other access networks, but these entities/interfaces are not shown for simplicity. As shown, the 5GS/EPS provides packet switched services, however those skilled in the art will readily appreciate that the various concepts presented throughout this application may be extended to networks providing circuit switched services or other cellular networks. The NG-RAN includes NR node b (gNB)203 and other gnbs 204. The gNB203 provides user and control plane protocol termination towards the UE 201. The gnbs 203 may be connected to other gnbs 204 via an Xn interface (e.g., backhaul). The gNB203 may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a Basic Service Set (BSS), an Extended Service Set (ESS), a TRP (transmitting receiving node), or some other suitable terminology. The gNB203 provides the UE201 with an access point to the 5GC/EPC 210. Examples of the UE201 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a Personal Digital Assistant (PDA), a satellite radio, non-terrestrial base station communications, satellite mobile communications, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a drone, an aircraft, a narrowband internet of things device, a machine type communication device, a terrestrial vehicle, an automobile, a wearable device, or any other similar functioning device. Those skilled in the art may also refer to UE201 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. The gNB203 is connected to the 5GC/EPC210 through an S1/NG interface. The 5GC/EPC210 includes MME (Mobility Management Entity)/AMF (Authentication Management domain)/SMF (Session Management Function) 211, other MME/AMF/SMF214, S-GW (serving Gateway)/UPF (User Plane Function) 212, and P-GW (Packet data Network Gateway)/UPF 213. The MME/AMF/SMF211 is a control node that handles signaling between the UE201 and the 5GC/EPC 210. In general, the MME/AMF/SMF211 provides bearer and connection management. All user IP (Internet protocol) packets are transported through the S-GW/UPF212, which S-GW/UPF212 itself is connected to the P-GW/UPF 213. The P-GW provides UE IP address allocation as well as other functions. The P-GW/UPF213 is connected to the internet service 230. The internet service 230 includes an operator-corresponding internet protocol service, and may specifically include the internet, an intranet, an IMS (IP Multimedia Subsystem), and a packet-switched streaming service.

As an embodiment, the UE201 corresponds to the first node in this application.

As an embodiment, the UE201 supports transmission in a non-terrestrial network (NTN).

As an embodiment, the UE201 supports transmission in a large delay-difference network.

As an embodiment, the UE201 supports V2X transmission.

As an embodiment, the UE201 supports MBS transmissions.

As an embodiment, the UE201 supports MBMS transmission.

As an embodiment, the gNB203 corresponds to the second node in this application.

As one embodiment, the gNB203 supports transmissions over a non-terrestrial network (NTN).

As an embodiment, the gNB203 supports transmission in large latency difference networks.

As an embodiment, the gNB203 supports V2X transmissions.

As an embodiment, the gNB203 supports MBS transmissions.

As an embodiment, the gNB203 supports MBMS transmission.

Example 3

Embodiment 3 shows a schematic diagram of an embodiment of a radio protocol architecture for the user plane and the control plane according to the present application, as shown in fig. 3. Fig. 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300, fig. 3 showing the radio protocol architecture for the control plane 300 between a first node (UE, satellite or aircraft in a gNB or NTN) and a second node (gNB, satellite or aircraft in a UE or NTN), or two UEs, in three layers: layer 1, layer 2 and layer 3. Layer 1(L1 layer) is the lowest layer and implements various PHY (physical layer) signal processing functions. The L1 layer will be referred to herein as PHY 301. Layer 2(L2 layer) 305 is above PHY301 and is responsible for the link between the first and second nodes and the two UEs through PHY 301. The L2 layer 305 includes a MAC (Medium Access Control) sublayer 302, an RLC (Radio Link Control) sublayer 303, and a PDCP (Packet Data Convergence Protocol) sublayer 304, which terminate at the second node. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by ciphering data packets and provides handoff support between second nodes to the first node. The RLC sublayer 303 provides segmentation and reassembly of upper layer packets, retransmission of lost packets, and reordering of packets to compensate for out-of-order reception due to HARQ. The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating the various radio resources (e.g., resource blocks) in one cell between the first nodes. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in layer 3(L3 layer) in the Control plane 300 is responsible for obtaining Radio resources (i.e., Radio bearers) and configuring the lower layers using RRC signaling between the second node and the first node. The radio protocol architecture of the user plane 350 includes layer 1(L1 layer) and layer 2(L2 layer), the radio protocol architecture in the user plane 350 for the first and second nodes is substantially the same for the physical layer 351, the PDCP sublayer 354 in the L2 layer 355, the RLC sublayer 353 in the L2 layer 355, and the MAC sublayer 352 in the L2 layer 355 as the corresponding layers and sublayers in the control plane 300, but the PDCP sublayer 354 also provides header compression for upper layer packets to reduce radio transmission overhead. The L2 layer 355 in the user plane 350 further includes an SDAP (Service Data Adaptation Protocol) sublayer 356, and the SDAP sublayer 356 is responsible for mapping between QoS streams and Data Radio Bearers (DRBs) to support diversity of services. Although not shown, the first node may have several upper layers above the L2 layer 355. Also included are a network layer (e.g., IP layer) that terminates at the P-GW on the network side and an application layer that terminates at the other end of the connection (e.g., far end UE, server, etc.).

As an example, the wireless protocol architecture in fig. 3 is applicable to the first node in this application.

As an example, the radio protocol architecture in fig. 3 is applicable to the second node in this application.

As an embodiment, the first signaling in this application is formed in the PHY301 or the MAC302 or the RRC 306.

As an embodiment, the first report in this application is in the MAC302, RRC306, PDCP304, or RLC 303.

As an embodiment, the first service in this application is generated at a layer or an application layer above the SDAP356 or PDCP354 or L2 layer 355.

As an embodiment, the second signaling in this application is in the PHY301 or MAC302 or RRC 306.

As an embodiment, the first information in the present application is the PHY301, the MAC302, or the RRC 306.

As an example, the first set of data in this application is generated at a layer or application layer above the SDAP356 or PDCP354 or L2 layer 355.

Example 4

Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to the present application, as shown in fig. 4. Fig. 4 is a block diagram of a first communication device 450 and a second communication device 410 communicating with each other in an access network.

The first communications device 450 includes a controller/processor 459, a memory 460, a data source 467, a transmit processor 468, a receive processor 456, a multi-antenna transmit processor 457, a multi-antenna receive processor 458, a transmitter/receiver 454, and an antenna 452.

The second communication device 410 includes a controller/processor 475, a memory 476, a receive processor 470, a transmit processor 416, a multiple antenna receive processor 472, a multiple antenna transmit processor 471, a transmitter/receiver 418, and an antenna 420.

In transmission from the second communication device 410 to the first communication device 450, at the second communication device 410, upper layer data packets from the core network are provided to a controller/processor 475. The controller/processor 475 implements the functionality of layer L2. In transmissions from the second communications device 410 to the first communications device 450, the controller/processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation to the first communications device 450 based on various priority metrics. The controller/processor 475 is also responsible for retransmission of lost packets, and signaling to the first communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (i.e., the physical layer). The transmit processor 416 implements coding and interleaving to facilitate Forward Error Correction (FEC) at the second communication device 410, as well as mapping of signal constellation based on various modulation schemes (e.g., Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding, including codebook-based precoding and non-codebook based precoding, and beamforming processing on the coded and modulated symbols to generate one or more spatial streams. Transmit processor 416 then maps each spatial stream to subcarriers, multiplexes with reference signals (e.g., pilots) in the time and/or frequency domain, and then uses an Inverse Fast Fourier Transform (IFFT) to generate the physical channels carrying the time-domain multicarrier symbol streams. The multi-antenna transmit processor 471 then performs transmit analog precoding/beamforming operations on the time domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multicarrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream that is then provided to a different antenna 420.

In a transmission from the second communications apparatus 410 to the first communications apparatus 450, each receiver 454 receives a signal through its respective antenna 452 at the first communications apparatus 450. Each receiver 454 recovers information modulated onto a radio frequency carrier and converts the radio frequency stream into a baseband multi-carrier symbol stream provided to a receive processor 456. Receive processor 456 and multi-antenna receive processor 458 implement the various signal processing functions of the L1 layer. A multi-antenna receive processor 458 performs receive analog precoding/beamforming operations on the baseband multi-carrier symbol stream from the receiver 454. Receive processor 456 converts the baseband multicarrier symbol stream after the receive analog precoding/beamforming operation from the time domain to the frequency domain using a Fast Fourier Transform (FFT). In the frequency domain, the physical layer data signals and the reference signals to be used for channel estimation are demultiplexed by the receive processor 456, and the data signals are subjected to multi-antenna detection in the multi-antenna receive processor 458 to recover any spatial streams destined for the first communication device 450. The symbols on each spatial stream are demodulated and recovered at a receive processor 456 and soft decisions are generated. The receive processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communications device 410 on the physical channel. The upper layer data and control signals are then provided to a controller/processor 459. The controller/processor 459 implements the functionality of the L2 layer. The controller/processor 459 may be associated with a memory 460 that stores program codes and data. Memory 460 may be referred to as a computer-readable medium. In transmissions from the second communications device 410 to the second communications device 450, the controller/processor 459 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer packets from the core network. The upper layer packet is then provided to all protocol layers above the L2 layer. Various control signals may also be provided to L3 for L3 processing.

In a transmission from the first communications device 450 to the second communications device 410, a data source 467 is used at the first communications device 450 to provide upper layer data packets to a controller/processor 459. The data source 467 represents all protocol layers above the L2 layer. Similar to the send function at the second communications apparatus 410 described in the transmission from the second communications apparatus 410 to the first communications apparatus 450, the controller/processor 459 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocation, implementing L2 layer functions for the user plane and control plane. The controller/processor 459 is also responsible for retransmission of lost packets and signaling to said second communications device 410. A transmit processor 468 performs modulation mapping, channel coding, and digital multi-antenna spatial precoding by a multi-antenna transmit processor 457 including codebook-based precoding and non-codebook based precoding, and beamforming, and the transmit processor 468 then modulates the resulting spatial streams into multi-carrier/single-carrier symbol streams, which are provided to different antennas 452 via a transmitter 454 after analog precoding/beamforming in the multi-antenna transmit processor 457. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a radio frequency symbol stream and provides the radio frequency symbol stream to the antenna 452.

In a transmission from the first communication device 450 to the second communication device 410, the functionality at the second communication device 410 is similar to the receiving functionality at the first communication device 450 described in the transmission from the second communication device 410 to the first communication device 450. Each receiver 418 receives an rf signal through its respective antenna 420, converts the received rf signal to a baseband signal, and provides the baseband signal to a multi-antenna receive processor 472 and a receive processor 470. The receive processor 470 and the multiple antenna receive processor 472 collectively implement the functionality of the L1 layer. Controller/processor 475 implements the L2 layer functions. The controller/processor 475 may be associated with a memory 476 that stores program codes and data. Memory 476 may be referred to as a computer-readable medium. In transmission from the first communication device 450 to the second communication device 410, the controller/processor 475 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer packets from the UE 450. Upper layer data packets from the controller/processor 475 may be provided to a core network.

As an embodiment, the first communication device 450 apparatus includes: at least one processor and at least one memory including computer program code; the at least one memory and the computer program code configured to, for use with the at least one processor, the first communication device 450 apparatus at least: receiving a first service through a first radio bearer; receiving a first signaling, wherein the first signaling indicates to establish a second radio bearer of the first service; sending a first report; receiving the first traffic over at least the latter of both the first radio bearer and the second radio bearer; wherein the first report is transmitted when a first condition is satisfied; the first condition comprises a transition of reception of the first traffic from the first radio bearer to the second radio bearer; the first radio bearer and the second radio bearer are different in bearer type, and the bearer type includes a non-unicast bearer and a unicast bearer; the first report is used to indicate SDUs related to the first service and received over the first radio bearer, the first report being higher layer control information.

As an embodiment, the first communication device 450 includes: a memory storing a program of computer readable instructions that when executed by at least one processor result in actions comprising: receiving a first service through a first radio bearer; receiving a first signaling, wherein the first signaling indicates to establish a second radio bearer of the first service; sending a first report; receiving the first traffic over at least the latter of both the first radio bearer and the second radio bearer; wherein the first report is sent when a first condition is met; the first condition comprises a transition of reception of the first traffic from the first radio bearer to the second radio bearer; the first radio bearer and the second radio bearer are different in bearer type, and the bearer type includes a non-unicast bearer and a unicast bearer; the first report is used to indicate SDUs related to the first service and received over the first radio bearer, the first report being higher layer control information.

As an embodiment, the second communication device 410 apparatus includes: at least one processor and at least one memory including computer program code; the at least one memory and the computer program code are configured for use with the at least one processor. The second communication device 410 means at least: sending a first signaling, wherein the first signaling indicates to establish a second radio bearer of a first service; the first service is sent over a first radio bearer; receiving a first report; transmitting the first traffic over at least the latter of both the first radio bearer and the second radio bearer; wherein a recipient of the first signaling sends the first report when a first condition is met; the first condition comprises a transition of reception of the first traffic from the first radio bearer to the second radio bearer; the first radio bearer and the second radio bearer are different in bearer type, and the bearer type includes a non-unicast bearer and a unicast bearer; the first report is used to indicate SDUs related to the first service and received over the first radio bearer, the first report being higher layer control information.

As an embodiment, the second communication device 410 apparatus includes: a memory storing a program of computer readable instructions that when executed by at least one processor result in actions comprising: sending a first signaling, wherein the first signaling indicates to establish a second radio bearer of a first service; the first service is sent over a first radio bearer; receiving a first report; transmitting the first traffic over at least the latter of both the first radio bearer and the second radio bearer; wherein a recipient of the first signaling sends the first report when a first condition is satisfied; the first condition comprises a transition of reception of the first traffic from the first radio bearer to the second radio bearer; the first radio bearer and the second radio bearer are different in bearer type, and the bearer type includes a non-unicast bearer and a unicast bearer; the first report is used to indicate SDUs related to the first service and received over the first radio bearer, the first report being higher layer control information.

As an embodiment, the first communication device 450 corresponds to a first node in the present application.

As an embodiment, the second communication device 410 corresponds to a second node in the present application.

For one embodiment, the first communication device 450 is a UE.

As an embodiment, the first communication device 450 is a vehicle-mounted terminal.

For one embodiment, the second communication device 410 is a base station.

For one embodiment, the second communication device 410 is a UE.

For one embodiment, the second communication device 410 is a satellite.

For one embodiment, receiver 456 (including antenna 460), receive processor 452, and controller/processor 490 are used to receive the first signaling.

For one embodiment, receiver 456 (including antenna 460), receive processor 452, and controller/processor 490 are used to receive the second signaling.

For one embodiment, receiver 456 (including antenna 460), receive processor 452, and controller/processor 490 are used to receive the first set of data in this application.

For one embodiment, receiver 456 (including antenna 460), receive processor 452, and controller/processor 490 are used to receive the first traffic in this application.

For one embodiment, a transmitter 456 (including an antenna 460), a transmit processor 455, and a controller/processor 490 are used to transmit the first information in this application.

For one embodiment, a transmitter 456 (including an antenna 460), a transmit processor 455, and a controller/processor 490 are used to send the first report in this application.

For one embodiment, a transmitter 416 (including an antenna 420), a transmit processor 412, and a controller/processor 440 are used to transmit the first signaling.

For one embodiment, transmitter 416 (including antenna 420), transmit processor 412, and controller/processor 440 are used to send the second signaling in this application.

For one embodiment, transmitter 416 (including antenna 420), transmit processor 412, and controller/processor 440 are used to transmit the first traffic in this application.

For one embodiment, transmitter 416 (including antenna 420), transmit processor 412, and controller/processor 440 are used to transmit the first set of data in this application.

For one embodiment, receiver 416 (including antenna 420), receive processor 412, and controller/processor 440 are used to receive the first report in this application.

For one embodiment, receiver 416 (including antenna 420), receive processor 412, and controller/processor 440 are used to receive the first information in this application.

Example 5

Embodiment 5 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in fig. 5. In fig. 5, U01 corresponds to the first node of the present application, N02 corresponds to the second node of the present application, and it is specifically noted that the sequence in the present example does not limit the sequence of signal transmission and the sequence of implementation in the present application, and the steps in F51 and F52 are optional.

ForFirst node U01In step S5101, by first wirelessBearing and receiving a first service; receiving a second signaling in step S5102; transmitting the first information in step S5103; receiving a first signaling in step S5104, where the first signaling indicates to establish a second radio bearer for the first service; sending a first report in step S5105; receiving the first traffic over the second radio bearer in step S5106.

For theSecond node N02Sending the first service through the first radio bearer in step S5201; transmitting the second signaling in step S5202; receiving the first information in step S5203; transmitting the first signaling in step S5204; receiving the first report in step S5205; the first traffic is sent over the second radio bearer in step S5206.

In embodiment 5, the first node U01, receiving the first traffic over at least the latter of the first radio bearer and the second radio bearer; when a first condition is met, the first node U01 sending the first report; the first condition comprises a transition of reception of the first traffic from the first radio bearer to the second radio bearer; the first radio bearer and the second radio bearer are different in bearer type, and the bearer type includes a non-unicast bearer and a unicast bearer; the first report is used to indicate SDUs related to the first service and received over the first radio bearer, the first report being higher layer control information.

As an embodiment, the first report is RRC signaling, the first report including a first identification used to determine PDCP SDUs related to the first service and received after a first missing PDCP SDU over the first radio bearer.

As an embodiment, the first report is sent by RRC signaling.

As an embodiment, the first identity is a field in the first report.

As an embodiment, the first identifier includes an SN (Sequence Number) Number.

For one embodiment, the first identification includes a PDCP SN.

As an embodiment, the first identifier relates to a length of a downlink SN of the PDCP of the first radio bearer.

As an embodiment, the first identifier includes HFN (Hyper Frame Number).

As one embodiment, the first identity includes a COUNT.

As an embodiment, a state variable of the PDCP associated with the first radio bearer is used to determine the first identity.

As an embodiment, the sentence "PDCP SDU related to the first service and received after the first missing PDCP SDU carried by the first radio" includes the following meanings: the first missing PDCP SDU is data of the first service.

As an embodiment, the sentence "PDCP SDU related to the first service and received after the first missing PDCP SDU carried by the first radio" includes the following meanings: the first missing PDCP SDU is user plane data of the first service.

As an embodiment, the sentence "PDCP SDU related to the first service and received after the first missing PDCP SDU carried by the first radio" includes the following meanings: the first missing PDCP SDU belongs to a receive window of a PDCP associated with the first radio bearer.

As an embodiment, the sentence "PDCP SDU related to the first service and received after the first missing PDCP SDU carried by the first radio" includes the following meanings: the first missing PDCP SDU is within a receive window of the PDCP associated with the first radio bearer.

As an embodiment, the sentence "PDCP SDU related to the first service and received after the first missing PDCP SDU carried over the first radio" includes the following meanings: and determining the COUNT value corresponding to the first lost PDCP SDU as the first identifier.

As an embodiment, the sentence "PDCP SDU related to the first service and received after the first missing PDCP SDU carried by the first radio" includes the following meanings: the COUNT value and a fixed offset corresponding to the first missing PDCP SDU are determined as the first identifier.

As an embodiment, the sentence "PDCP SDU related to the first service and received after the first missing PDCP SDU carried by the first radio" includes the following meanings: the next value of the COUNT value corresponding to the first missing PDCP SDU is determined as the first identity.

As an embodiment, the sentence "PDCP SDU related to the first service and received after the first missing PDCP SDU carried by the first radio" includes the following meanings: a PDCP SDU after the PDCP SDU having the largest COUNT value is considered lost, and the first identifier is a maximum value of the COUNT values of all PDCP SDUs related to the first service received through the first radio bearer.

As an embodiment, the sentence "PDCP SDU related to the first service and received after the first missing PDCP SDU carried by the first radio" includes the following meanings: a PDCP SDU after the PDCP SDU having the largest COUNT value is considered lost, and the first identifier is a value next to a maximum value of COUNT values among all PDCP SDUs related to the first service received through the first radio bearer.

For one embodiment, the first identifier comprises RX _ DELIV.

For one embodiment, the first flag comprises RX _ NEXT.

For one embodiment, the first identification comprises RX _ REORD.

As an embodiment, the first report is RRC signaling, the first report including a second identifier used to determine a first time window corresponding to a last SDU received over the first radio bearer and related to the first service.

As an embodiment, a first missing PDCP SDU related to the first service and carried over the first radio is control signaling.

As an embodiment, a first missing PDCP SDU related to the first service and carried by the first radio is RRC signaling.

As an embodiment, a first missing PDCP SDU related to the first service and carried over the first radio bearer is RRC signaling transmitted over a control logical channel related to the first service.

As an embodiment, the time window is determined by a Modification Period (Modification Period) of a control channel related to the first traffic, which is transmitted through the first radio bearer.

As an embodiment, the time window is equal to a Modification Period (Modification Period) of a control channel related to the first traffic, which is sent through the first radio bearer.

As an embodiment, the time window is determined by a Repetition Period (Repetition Period) of a control channel related to the first service transmitted through the first radio bearer.

As an embodiment, the time window is equal to a Repetition Period (Repetition Period) of a control channel related to the first service sent by the first radio bearer.

As an embodiment, the time window is equal to a Modification Period (Modification Period) of a control channel related to the first service sent over the first radio bearer plus a fixed time offset.

As an embodiment, the time window is equal to a Modification Period (Modification Period) of a control channel related to the first service sent over the first radio bearer plus a fixed time offset, the fixed time offset being z milliseconds, where z is a positive integer.

As an embodiment, the time window is determined by a Modification Period (Modification Period) of a traffic channel related to the first traffic, which is transmitted through the first radio bearer.

As an embodiment, the time window is equal to a Modification Period (Modification Period) of a traffic channel related to the first traffic, which is transmitted through the first radio bearer.

As an embodiment, the time window is determined by a Repetition Period (Repetition Period) of a traffic channel related to the first service transmitted through the first radio bearer.

As an embodiment, the time window is equal to a Repetition Period (Repetition Period) of a traffic channel related to the first service sent by the first radio bearer.

As an embodiment, the time window is equal to a Modification Period (Modification Period) of a traffic channel related to the first service sent over the first radio bearer plus a fixed time offset.

As an embodiment, the time window is equal to a Modification Period (Modification Period) of a traffic channel related to the first service sent over the first radio bearer plus a fixed time offset, the fixed time offset being z milliseconds, where z is a positive integer.

As one embodiment, the control channel related to the first service includes an MCCH.

As an embodiment, the control channel related to the first service comprises an SC-MCCH.

As one embodiment, the traffic channel related to the first traffic includes MTCH.

As one embodiment, the traffic channel related to the first traffic includes an SC-MTCH.

As one embodiment, the first indication comprises an indication of the first time window.

As an embodiment, the identification of the first time window comprises an ID of the first time window.

For one embodiment, the identification of the first time window includes a TransactionIdentifier for the first time window.

As an embodiment, the identification of the first time window comprises an RRC-TransactionIdentifier of the first time window.

As an embodiment, the identification of the first time window comprises an sfn (system Frame number) of the first time window.

As an embodiment, the identification of the first time window comprises an hfn (hyper Frame number) of the first time window.

In one embodiment, the identification of the first window of time includes a first SFN of the first window of time.

As one embodiment, the identification of the first time window includes a last SFN of the first time window.

As an example, the sentence "the first time window is a time window related to the first service and corresponding to a last SDU received over the first radio bearer" includes the following meanings: the last SDU associated with the first service and received over the first radio bearer is an SDU transmitted over a control channel.

As an example, the sentence "the first time window is a time window related to the first service and corresponding to a last SDU received over the first radio bearer" includes the following meanings: the last SDU related to the first service and received over the first radio bearer is an SDU for RRC signaling.

As an embodiment, the sentence "the first time window is a time window related to the first service and corresponding to a last SDU received over the first radio bearer" includes the following meaning: the last SDU related to the first service and received over the first radio bearer is an SDU transmitted over MCCH.

As an example, the sentence "the first time window is a time window related to the first service and corresponding to a last SDU received over the first radio bearer" includes the following meanings: the last SDU related to the first service and received over the first radio bearer is an SDU transmitted over SC-MCCH.

As an example, the sentence "the first time window is a time window related to the first service and corresponding to a last SDU received over the first radio bearer" includes the following meanings: the time window to which the last of the SDUs belongs is the first time window.

As an example, the sentence "the first time window is a time window related to the first service and corresponding to a last SDU received over the first radio bearer" includes the following meanings: the last one of the SDUs is transmitted within the first time window.

As an example, the sentence "the first time window is a time window related to the first service and corresponding to a last SDU received over the first radio bearer" includes the following meanings: the last one of the SDUs is received within the first time window.

As an example, the sentence "the first time window is a time window related to the first service and corresponding to a last SDU received over the first radio bearer" includes the following meanings: and the sending time of the last SDU is equal to the starting time of the first time window.

As an example, the sentence "the first time window is a time window related to the first service and corresponding to a last SDU received over the first radio bearer" includes the following meanings: the receiving time of the last SDU is equal to the starting time of the first time window.

As an example, the sentence "the first time window is a time window related to the first service and corresponding to a last SDU received over the first radio bearer" includes the following meanings: the sending time of the last SDU is equal to the ending time of the first time window.

As an example, the sentence "the first time window is a time window related to the first service and corresponding to a last SDU received over the first radio bearer" includes the following meanings: and the receiving time of the last SDU is equal to the termination time of the first time window.

As an embodiment, the first report is a PDCP status report, the first set of state variables is a subset of a set of all state variables of a PDCP entity associated with the second radio bearer, and the first signaling indicates that a value of a state variable in the first set of state variables is determined by a value of a state variable of a PDCP entity associated with the first radio bearer; the first node generates the first report according to the PDCP entity associated with the second radio bearer, and the first node sends the first report through a radio bearer of which the bearer type is a unicast bearer in the first radio bearer and the second radio bearer.

As an embodiment, the first report is a PDCP status report.

As an embodiment, a RadioBearerConfig is used to configure the first radio bearer, the first radio bearer being associated with the PDCP entity at the RadioBearerConfig.

As an embodiment, a RadioBearerConfig is used to configure the first radio bearer, the configuration of the first radio bearer and the PDCP entity being associated at the RadioBearerConfig.

As an embodiment, the RadioBearerConfig is used for configuring the first radio bearer, which is associated at the RadioBearerConfig with the configuration of one PDCP entity by drb-Identity.

As an embodiment, the serving cell of the first node U01 configures the first radio bearer and the PDCP entity associated with the first radio bearer by RRC signaling.

As an embodiment, a RadioBearerConfig is used to configure the second radio bearer, the first radio bearer and the PDCP entity being associated at the RadioBearerConfig.

As an embodiment, a RadioBearerConfig is used to configure the second radio bearer, the configuration of the first radio bearer and the PDCP entity being associated at the RadioBearerConfig.

As an embodiment, a RadioBearerConfig is used for configuring the second radio bearer, the first radio bearer being associated with the configuration of one PDCP entity at the RadioBearerConfig by drb-Identity.

As an embodiment, the serving cell of the first node U01 configures the second radio bearer and the PDCP entity associated with the first radio bearer by RRC signaling.

As an embodiment, the first set of state variables is a set of all state variables of the PDCP entity associated with the second radio bearer.

As an embodiment, the first set of state variables includes only part of the state variables in the set of all state variables of the PDCP entity associated with the second radio bearer.

As one embodiment, the first radio bearer adopts a UM mode.

As an embodiment, the first radio bearer adopts an AM mode.

As an embodiment, the second radio bearer adopts an AM mode.

As an embodiment, the second radio bearer adopts a UM mode.

As an embodiment, the first radio bearer is a non-unicast bearer, and adopts a UM mode; the second radio bearer is a unicast bearer, and adopts an am (acknowledged mode) mode.

As an embodiment, the first radio bearer is a non-unicast bearer, and adopts a UM mode; the second radio bearer is a unicast bearer, and adopts a um (unowledged mode) mode.

As an embodiment, the state variable of the PDCP entity associated with the second radio bearer is a non-negative integer.

As an embodiment, the state variable of the PDCP entity associated with the second radio bearer comprises TX _ NEXT.

As an embodiment, the state variable of the PDCP entity associated with the second radio bearer comprises RX _ NEXT.

As an embodiment, the state variable of the PDCP entity with which the second radio bearer is associated comprises RX _ DELIV.

As an embodiment, the state variable of the PDCP entity associated with the second radio bearer comprises RX _ REORD.

As an embodiment, the state variable of the PDCP entity with which the second radio bearer is associated includes COUNT.

As an embodiment, the state variable of the PDCP entity associated with the second radio bearer comprises an HFN.

For one embodiment, the PDCP-SN-SizeUL of the PDCP entity associated with the first radio bearer and the PDCP-SN-SizeUL of the PDCP entity associated with the second radio bearer are configured to be the same.

For one embodiment, the PDCP-SN-SizeUL of the PDCP entity associated with the first radio bearer and the PDCP-SN-SizeUL of the PDCP entity associated with the second radio bearer are configured differently.

For one embodiment, the PDCP-SN-SizeDL of the PDCP entity associated with the first radio bearer and the PDCP-SN-SizeUL of the PDCP entity associated with the second radio bearer are configured to be the same.

As an embodiment, the PDCP-SN-SizeDL of the PDCP entity associated with the first radio bearer and the PDCP-SN-SizeUL of the PDCP entity associated with the second radio bearer are configured differently.

As an embodiment, the discardTimer of the PDCP entity associated with the first radio bearer and the discardTimer of the PDCP entity associated with the second radio bearer are configured to be different.

As an embodiment, the t-Reordering of the PDCP entity associated with the first radio bearer and the t-Reordering of the PDCP entity associated with the second radio bearer are configured to be different.

As an embodiment, the benefits of the parameters of the PDCP entity associated with the first radio bearer being configured differently from the corresponding parameters of the PDCP entity associated with the second radio bearer include: the bearer types of the first radio bearer and the second radio bearer are different, and therefore, the functions are different, and different parameters need to be configured for them, which is beneficial to implementing the sub-functions.

As an embodiment, the value of the state variable in the first set of state variables is determined by the value of the homonymous state variable of the PDCP entity with which the first radio bearer is associated.

As an embodiment, the value of the state variable in the first state variable set is determined by the value of the state variable corresponding to the PDCP entity associated with the first radio bearer.

As an embodiment, the benefits of the parameters of the PDCP entity associated with the first radio bearer being configured differently from the corresponding parameters of the PDCP entity associated with the second radio bearer include: when the first radio bearer and the second radio bearer have different modes, i.e., one using AM mode and one using UM mode, in which case the bearer using AM mode can support a certain degree of link recovery, it is necessary to use longer SNs, i.e., pdcp-SN-SizeUL and pdcp-SN-SizeDL, for UM mode, there is no need for a long SN since there is no need to recover earlier transmitted data packets.

As an embodiment, the benefits of the parameters of the PDCP entity associated with the first radio bearer being configured differently from the corresponding parameters of the PDCP entity associated with the second radio bearer include: when the modes of the first radio bearer and the second radio bearer are different, namely one uses AM mode and one uses UM mode, as the AM mode supports data recovery, a longer buffer ordering may be used to implement sequential delivery (In sequence delivery); while UM mode preferably supports Out of order delivery (Out of sequence delivery) because data cannot be recovered.

As an embodiment, the first set of state variables of the PDCP entity associated with the second radio bearer includes a value of a state variable equal to a value of a state variable of the PDCP entity associated with the first radio bearer.

As an embodiment, the initial value of the state variable included in the first state variable set of the PDCP entity associated with the second radio bearer is set to the value of the state variable of the PDCP entity associated with the first radio bearer.

As an embodiment, an initial value of a state variable other than the first state variable group of the PDCP entity associated with the second radio bearer is set to 0.

As one embodiment, the first set of state variables includes only TX _ NEXT.

As one embodiment, the first set of state variables includes only state variables other than TX _ NEXT.

As one embodiment, the first set of state variables includes only RX _ NEXT and RX _ DELIV.

As an embodiment, the first set of state variables comprises RX _ REORD only.

As an embodiment, the first set of state variables includes only RX _ NEXT and RX _ DELIV and RX _ REORD.

As an embodiment, the first set of state variables includes only COUNT.

As an embodiment, the first set of state variables includes only RX _ NEXT and RX _ DELIV and COUNT.

As an embodiment, the first set of state variables includes only RX _ NEXT and RX _ DELIV and RX _ REORD and COUNT.

As an embodiment, the first set of state variables includes only RX _ NEXT and RX _ DELIV if the second radio bearer is AM mode and the first radio bearer is UM mode.

As an embodiment, if the second radio bearer is AM mode and the first radio bearer is UM mode, the first set of state variables includes only RX _ NEXT and RX _ DELIV and COUNT.

As an embodiment, the first set of state variables includes only RX _ NEXT and RX _ DELIV and RX _ REORD if the second radio bearer is AM mode and the first radio bearer is UM mode.

As an embodiment, if the second radio bearer is AM mode and the first radio bearer is UM mode, the first state variable set includes only RX _ NEXT and RX _ DELIV and RX _ REORD and COUNT.

As an embodiment, the first set of state variables includes only COUNT if the second radio bearer is UM mode and the first radio bearer is UM mode.

As an embodiment, the state variable included in the first state variable group relates to whether the mode of the second radio bearer and the first radio bearer is the same.

As an embodiment, when the PDCP-SN-SizeDL of the PDCP entity associated with the second radio bearer is smaller than the PDCP-SN-SizeDL of the PDCP entity associated with the first radio bearer, the value of the state variable belonging to the first state variable group of the PDCP entity associated with the second radio bearer is a truncated value of the state variable corresponding to the PDCP entity associated with the first radio bearer.

As a sub-embodiment of this embodiment, the length of the truncation value is equal to the difference between the PDCP-SN-SizeDL of the PDCP entity associated with the first radio bearer and the PDCP-SN-SizeDL of the PDCP entity associated with the second radio bearer.

As a sub-embodiment of this embodiment, the truncation of the truncation value is a low-order truncation.

As a sub-embodiment of this embodiment, the truncation of the truncation value is a high order truncation.

As an embodiment, when the PDCP-SN-SizeDL of the PDCP entity associated with the second radio bearer is smaller than the PDCP-SN-SizeDL of the PDCP entity associated with the first radio bearer, the value of the HFN part of the state variable belonging to the first state variable set of the PDCP entity associated with the second radio bearer is equal to the value of the HFN part of the state variable corresponding to the PDCP entity associated with the first radio bearer, and the value of the SN of the state variable belonging to the first state variable set of the PDCP entity associated with the second radio bearer is a truncated value of the SN part of the state variable corresponding to the PDCP entity associated with the first radio bearer.

As an embodiment, when the PDCP-SN-SizeDL of the PDCP entity associated with the second radio bearer is greater than the PDCP-SN-SizeDL of the PDCP entity associated with the first radio bearer, the value of the HFN part of the state variable belonging to the first state variable set of the PDCP entity associated with the second radio bearer is equal to the value of the HFN part of the state variable corresponding to the PDCP entity associated with the first radio bearer, and the value of the SN of the state variable belonging to the first state variable set of the PDCP entity associated with the second radio bearer is zero-padded by the SN part of the state variable corresponding to the PDCP entity associated with the first radio bearer.

As a sub-embodiment of this embodiment, the length of the zero padding obtained by zero padding the SN part is equal to the difference between the PDCP-SN-sizeddl of the PDCP entity associated with the second radio bearer and the PDCP-SN-sizeddl of the PDCP entity associated with the first radio bearer.

As a sub-embodiment of this embodiment, the zero padding obtained by the partial zero padding of SN is a low truncation.

As a sub-embodiment of this embodiment, the zero padding obtained by padding zeros partially in the SN is a high-order truncation.

As an embodiment, the first report is a PDCP status report, the first node U01 generates the first report according to a PDCP entity associated with the first radio bearer, and the first node U01 sends the first report over a radio bearer of which the bearer type is a unicast bearer among the first radio bearer and the second radio bearer.

As an embodiment, the first report is a PDCP status report, and the first node U01 generates the first report according to a status variable of a PDCP entity associated with the first radio bearer.

As an embodiment, the first report is a PDCP status report, and the first node U01 generates the first report according to the COUNT of the PDCP entity associated with the first radio bearer.

As an embodiment, the first report is a PDCP status report, and the first node U01 generates the first report according to RX _ NEXT and RX _ DELIV of a PDCP entity associated with the first radio bearer.

As one embodiment, the serving cell of the first node U01 indicates that the first radio bearer is associated with the second radio bearer.

As an embodiment, the serving cell of the first node U01 instructs the first report to be generated according to the PDCP entity with which the first radio bearer is associated.

As an embodiment, the serving cell of the first node U01 indicates the identity of the radio bearer used for generating the first report, which is the identity of the first radio bearer.

As an embodiment, the serving cell of the first node U01 indicates the drb-Identity of the radio bearer used to generate the first report, which is the Identity of the first radio bearer.

As an embodiment, the serving cell of the first node U01 indicates mrb-Identity of the radio bearer used to generate the first report, the mrb-Identity being the Identity of the first radio bearer.

As an embodiment, the serving cell of the first node U01 indicates the sc-mrb-Identity of the radio bearer used to generate the first report, the sc-mrb-Identity being an Identity of the first radio bearer.

As an embodiment, the serving cell of the first node U01 indicates the scmrb-Identity of the radio bearer used to generate the first report, which is the Identity of the first radio bearer.

As an embodiment, the PDCP entity associated with the second radio bearer takes into account that the generation of the first report is according to the first radio bearer.

As an embodiment, the first report is sent as a PDCP status report of the first radio bearer when the first radio bearer is a unicast bearer.

As an embodiment, the first report is sent as a PDCP status report of the second radio bearer when the second radio bearer is a unicast bearer.

As an embodiment, when the first radio bearer is a unicast bearer, the PDCP entity of the first radio bearer generates the first report and transmits the generated first report.

As one embodiment, when the first radio bearer is a unicast bearer, the PDCP entity of the first radio bearer generates the first report and transmits the generated first report when the first condition is satisfied.

As an embodiment, when the first radio bearer is a unicast bearer, the PDCP entity of the second radio bearer generates the first report according to the PDCP entity of the first radio bearer and transmits the generated first report.

As an embodiment, when the first condition is satisfied when the first radio bearer is a unicast bearer, the PDCP entity of the second radio bearer generates the first report according to the PDCP entity of the first radio bearer and transmits the generated first report.

Example 5a

Embodiment 5a is based on embodiment 5 and is directed to a scenario in which a serving cell of the first node U01 decides to switch a radio bearer for the first traffic from a unicast bearer to a non-unicast bearer. The steps required in example 5a, but not shown in detail, can be referred to example 5, with reference to figure 5. It is shown to be particularly noted that in example 5a, step S5103 is not necessary; the second node sends the first traffic over the second radio bearer in step S5206.

As one embodiment, the first radio bearer is a unicast bearer.

As one embodiment, the first radio bearer is a DRB.

As an embodiment, the second signaling is sent by means of unicast.

As an embodiment, the second signaling is transmitted through a downlink DCCH channel.

As an embodiment, the second signaling is RRC signaling.

As an embodiment, the second signaling is a MAC CE.

As an embodiment, the second signaling is a rrcreeconfiguration message.

As an embodiment, the second signaling is an RRCConnectionReconfiguration message.

As an embodiment, the second signaling is a SIB.

As an embodiment, the second signaling indicates that the transmission of the first traffic is switched from the first radio bearer to the second radio bearer.

As an embodiment, the second signaling is sent in a unicast manner, and the second signaling carries control information related to a multicast service.

As an embodiment, the second signaling is sent in a unicast manner, and the second signaling carries an SIB related to a multicast service.

As an embodiment, the second signaling is sent in a unicast manner, and the second signaling carries an SC-MTCH configuration related to multicast traffic.

As an embodiment, the second signaling is sent in a unicast manner, and the second signaling carries a configuration of QoS flow related to the first service.

As an embodiment, the second signaling indicates that the first radio bearer is released.

As an embodiment, the second signaling indicates suspension of the first radio bearer.

As an embodiment, the second signaling indicates that QoS flow of the first traffic is no longer mapped to the first radio bearer.

As an embodiment, the first signaling indicates that the sending of the first service is switched from the first radio bearer to the second radio bearer, then step S5202 and step S5102 are not required.

As one embodiment, the second radio bearer is a non-unicast bearer.

As one embodiment, the second radio bearer is a broadcast bearer.

As an embodiment, the second radio bearer is a multicast bearer.

As an embodiment, the second radio bearer is an MRB bearer.

As one embodiment, the second radio bearer is an SC-MRB bearer.

As an embodiment, the sentence "the second signaling indicates that the transmission of the first traffic is switched from the first radio bearer to the second radio bearer" includes the following meanings: the second signaling indicates that the transmission of the first traffic is switched from the first radio bearer to the second radio bearer.

As an embodiment, the sentence "the second signaling indicates that the transmission of the first traffic is switched from the first radio bearer to the second radio bearer" includes the following meanings: the second signaling indicates that the first traffic begins to be transmitted on the second radio bearer.

As an embodiment, the sentence "the second signaling indicates that the transmission of the first traffic is switched from the first radio bearer to the second radio bearer" includes the following meaning: the configuration of the first service is contained in a SIB relating to multicast and on a control channel relating to multicast services.

As an embodiment, the sentence "the second signaling indicates that the transmission of the first traffic is switched from the first radio bearer to the second radio bearer" includes the following meanings: the configuration of the first service is included in the SIB related to the multicast and is included in the transmission channel scheduling information related to the multicast service.

As an embodiment, the first signaling is higher layer signaling transmitted on a control channel related to multicast traffic.

As an embodiment, the first signaling is RRC signaling transmitted in a broadcast manner.

As an embodiment, the first signaling is RRC signaling transmitted by a unicast manner.

As an embodiment, the first signaling is a rrcreeconfiguration message.

As an embodiment, the first signaling is an RRCConnectionReconfiguration message.

For one embodiment, the first signaling comprises RRC signaling transmitted on an MCCH channel.

For one embodiment, the first signaling comprises RRC signaling transmitted on a SC-MCCH channel.

As one embodiment, the first signaling includes a SIB.

As an embodiment, the first signaling includes a SIB related to a multicast service.

For one embodiment, the first signaling comprises sc-mtch-scheduling info.

As an embodiment, the first report includes a PDCP status report.

As an embodiment, the first report includes a PDCP status report, the first report generated by a PDCP entity associated with the first radio bearer of the first node U01.

As an embodiment, the first report includes a PDCP status report, the first report being sent by the first radio bearer.

As an embodiment, the first radio bearer is suspended after the first report is sent out.

As an embodiment, the first radio bearer is released after the first report is sent out.

As an embodiment, the first radio bearer is reserved after the first report is sent out.

As an embodiment, the first report is RRC signaling.

As one embodiment, the first report is a control plane message.

As one embodiment, the first report includes mbmsinterrestindication.

As an embodiment, the first report includes ueAssistanceInformation.

For one embodiment, the first report includes dedicatedSIBRequest-r 16.

For one embodiment, the first report includes ueInformationResponse-r 16.

For one embodiment, the first report includes MBMSIntestrIndication-r 17.

For one embodiment, the first report includes ueAscistationinformation-r 17.

For one embodiment, the first report includes mbmsinterrestindication 1.

For one embodiment, the first report includes mbmsinterrestindication 2.

For one embodiment, the second node N02 sends the first traffic over the second radio bearer.

Example 5b

Embodiment 5b is based on embodiment 5 and the scenario for which the serving cell of the first node U01 decides to switch the radio bearer for the first traffic from a non-unicast bearer to a unicast bearer. The steps required in example 5b, but not shown in detail, can be referred to example 5, with reference to figure 5.

As one embodiment, the first radio bearer is a non-unicast bearer.

As one embodiment, the first radio bearer is a broadcast bearer.

As an embodiment, the first radio bearer is a multicast bearer.

As one embodiment, the first radio bearer is an MRB bearer.

As one embodiment, the first radio bearer is an SC-MRB bearer.

As an embodiment, the second signaling is higher layer signaling transmitted on a control channel related to multicast traffic.

As an embodiment, the second signaling is RRC signaling transmitted by a broadcast manner.

As an embodiment, the second signaling is RRC signaling transmitted by unicast.

As an embodiment, the second signaling is a rrcreeconfiguration message.

For one embodiment, the second signaling comprises RRC signaling transmitted on an MCCH channel.

For one embodiment, the second signaling comprises RRC signaling transmitted on a SC-MCCH channel.

As one embodiment, the second signaling includes a SIB.

As an embodiment, the second signaling includes a SIB related to a multicast service.

For one embodiment, the second signaling comprises sc-mtch-scheduling info.

As an embodiment, the sentence "the second signaling indicates that the transmission of the first traffic is switched from the first radio bearer to the second radio bearer" includes the following meanings: the second signaling indicates to release the first radio bearer.

As an embodiment, the sentence "the second signaling indicates that the transmission of the first traffic is switched from the first radio bearer to the second radio bearer" includes the following meanings: the second signaling indicates suspension of the first radio bearer.

As an embodiment, the sentence "the second signaling indicates that the transmission of the first traffic is switched from the first radio bearer to the second radio bearer" includes the following meanings: the second signaling indicates that QoS flow of the first traffic is no longer mapped to the first radio bearer.

As an embodiment, the sentence "the second signaling indicates that the transmission of the first traffic is switched from the first radio bearer to the second radio bearer" includes the following meanings: the second signaling indicates that the bearer type of the first service changes.

As an embodiment, the sentence "the second signaling indicates that the transmission of the first traffic is switched from the first radio bearer to the second radio bearer" includes the following meaning: the second signaling indicates that the bearer type of the first traffic is changed from a non-multicast bearer to a unicast bearer.

As an embodiment, the sentence "the second signaling indicates that the transmission of the first traffic is switched from the first radio bearer to the second radio bearer" includes the following meanings: the configuration of the first service is contained only in the SIB and not on a control channel related to the multicast service.

As an embodiment, the sentence "the second signaling indicates that the transmission of the first traffic is switched from the first radio bearer to the second radio bearer" includes the following meaning: the configuration of the first service is contained only in the SIB and not in the transport channel scheduling information related to the multicast service.

As an embodiment, the first information is used to trigger the first signaling.

As one embodiment, the first information includes RRC signaling.

As one embodiment, the first information includes a MAC CE.

As an embodiment, the physical channel occupied by the first information includes a PUSCH.

As an embodiment, the first information indicates that reception of the first service is requested.

As an embodiment, the first information indicates that the first service is requested to be received through a unicast bearer.

As an embodiment, the first information indicates a request to establish a unicast bearer to receive the first service.

For one embodiment, the first information includes a RRCSetupRequest message.

For one embodiment, the first information includes a RRCResumeRequest message.

For one embodiment, the first information includes an RRCResumeRequest1 message.

For one embodiment, the first node U01 is in RRC connected mode to receive the second radio bearer.

As an embodiment, the first signaling is sent by means of unicast.

As an embodiment, the first signaling is transmitted through a downlink DCCH channel.

As an embodiment, the first signaling is RRC signaling.

As an embodiment, the first signaling is a MAC CE.

As an embodiment, the first signaling is a rrcreeconfiguration message.

As an embodiment, the first signaling indicates establishment of the second radio bearer.

As an embodiment, the first signaling indicates that QoS flow of the first traffic is mapped to the second radio bearer.

For one embodiment, the first report includes a PDCP status report.

As an embodiment, the first report is generated according to a PDCP entity associated with the first radio bearer.

As an embodiment, the first report is sent over the second radio bearer.

As one embodiment, the first report includes RRC signaling.

As an embodiment, the first report and the first information are multiplexed within the same PDU.

As an embodiment, the first information carries the first report.

As one embodiment, the second radio bearer is a unicast bearer.

As one embodiment, the second radio bearer is a DRB.

As an embodiment, the second node N02 sends the first service through the second radio bearer in step S5206.

For one embodiment, the first node U01 receives the first traffic through the second radio bearer in step S5106.

Example 5c

Embodiment 5c is based on embodiment 5 and is directed to a scenario in which the first node U01 switches from a cell transmitting the first traffic over a unicast bearer to another cell transmitting the first traffic over a non-unicast bearer. The steps required in example 5c, but not shown in detail, can be referred to example 5, with reference to figure 5. In particular, in example 5c, step S5206 is not required.

As one embodiment, the first radio bearer is a unicast bearer.

As one embodiment, the first radio bearer is a DRB.

As an embodiment, the second signaling comprises higher layer signaling.

As an embodiment, the second signaling comprises RRC signaling.

As an embodiment, the second signaling comprises rrcreeconfiguration.

As an embodiment, the second signaling comprises RRCConnectionReconfiguration.

As an embodiment, the second signaling comprises MBMSCountingRequest.

As an embodiment, the second signaling comprises mbscouting request.

As an embodiment, the second signaling includes SC-PTMCountingRequest.

For one embodiment, the second signaling includes a ueInformationRequest-r 9.

As an embodiment, the second signaling includes a ueInformationRequest.

For one embodiment, the second signaling includes a ueInformationRequest-r 17.

As one embodiment, the first information includes RRC signaling.

As one embodiment, the first information includes a MAC CE.

As an embodiment, the first information indicates that the first service is being received.

As an embodiment, the first information includes MBMSCountingResponse.

As an embodiment, the first information comprises mbscouting response.

As an embodiment, the first information includes SC-PTMCountingResponse.

As an embodiment, the second node N02 has the information that the first node U01 is receiving the first traffic, then step S5203 and step S5103 are not required.

As an embodiment, the context of the first node U01 owned by the second node N02 includes information that the first node U01 is receiving the first traffic, then steps S5203 and S5103 are not needed.

As an embodiment, the first signaling comprises rrcreeconfiguration.

As an embodiment, the first signaling comprises RRCConnectionReconfiguration.

As an embodiment, the first signaling comprises ReconfigurationWithSync.

As an embodiment, the first signaling includes a SIB for a target cell of the first node U01.

As an embodiment, the first signaling comprises a SIB for multicast service related of a target cell of the first node U01.

As an embodiment, the first signaling includes a SIB for a target cell of the first node U01 related to the first service.

As an embodiment, the first signaling includes control information related to multicast traffic of a target cell of the first node U01.

For one embodiment, the first signaling comprises control signaling transmitted on MCCH of a target cell of the first node U01.

For one embodiment, the first signaling comprises an RRC message transmitted on MCCH of a target cell of the first node U01.

For one embodiment, the first signaling comprises control signaling transmitted on a SC-MCCH for a target cell of the first node U01.

For one embodiment, the first signaling comprises an RRC message transmitted on SC-MCCH of a target cell of the first node U01.

As an embodiment, the first signaling comprises configuration information of a target cell of the first node U01 related to the second radio bearer.

As an embodiment, the first signaling includes configuration information of a target cell of the first node U01 for establishing the second radio bearer of the first service.

As an embodiment, the first node U01 establishes the second radio bearer related to the first service according to the indication of the first signaling.

For one embodiment, the first node U01 sends the first report before receiving the first signaling.

As an embodiment, the first node U01 sends the first report after receiving the first signaling.

As an embodiment, the first signaling triggers the first report.

As an embodiment, the first report triggers the first signaling.

As an embodiment, the first node U01 receives the first service through the second radio bearer in a target cell.

As an embodiment, the target cell of the first node U01 sends the first service through the second radio bearer.

As one embodiment, the second radio bearer is a non-unicast bearer.

As an example, the benefits of the above approach include: when the first node U01 performs cell switching, it carries multicast service configuration information of neighboring cells, which can help the first node U01 to quickly establish a bearer, thereby reducing the possibility of time delay and data interruption.

As an example, the benefits of the above approach include: when the first node U01 performs cell handover, by sending the first report related to the reception situation, the base station of the first node is favorable to control the first service transmission in the local cell and is also favorable to better configure the second radio bearer.

Example 6

Embodiment 6 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in fig. 6. In fig. 6, U11 corresponds to a first node of the present application, N12 corresponds to a second node of the present application, and N13 is a first bearer cell, and it is specifically noted that the sequence in the present example does not limit the sequence of signal transmission and the sequence of implementation in the present application.

For theFirst node U11In step S6101, a first service is received through a first radio bearer; receiving a first signaling in step S6102; sending a first report in step S6103; receiving the first service through a second radio bearer in step S6104.

For theSecond node N12Sending the first signaling in step S6201; receiving the first report in step S6202; in step S6203, the first service is sent through the second radio bearer.

ForFirst bearer cell N13In step S6301, the first service is sent through the first radio bearer.

In embodiment 6, the first node U11, receiving the first traffic over at least the latter of the first radio bearer and the second radio bearer; when a first condition is met, the first node U11 sending the first report; the first condition comprises a transition of reception of the first traffic from the first radio bearer to the second radio bearer; the first radio bearer and the second radio bearer are different in bearer type, and the bearer type includes a non-unicast bearer and a unicast bearer; the first report is used to indicate SDUs related to the first service and received over the first radio bearer, the first report being higher layer control information.

As an embodiment, the first bearer Cell N13 is a Source Cell (Source Cell) of the first node U11, and the second node N12 is a Target Cell (Target Cell) of the first node U11.

For one embodiment, the first node U11 switches the second node N12 from the first bearer cell N13.

As an embodiment, the first bearer cell N13 sends the first service through the first radio bearer.

For one embodiment, the second node N12 sends the first traffic over the second radio bearer.

As an embodiment, the first bearer cell N13 sends the first traffic to the first node U11 only over the first radio bearer.

As an embodiment, the second node N12 only sends the first traffic over the second radio bearer.

As one embodiment, the second radio bearer is a broadcast bearer.

As an embodiment, the second radio bearer is a multicast bearer.

As an embodiment, the second radio bearer is an MRB bearer.

As one embodiment, the second radio bearer is an SC-MRB bearer.

As an embodiment, the second radio bearer is a DRB bearer identified as a multicast bearer.

As one embodiment, the first radio bearer is a DRB bearer.

As an embodiment, the first radio bearer is a DRB bearer that is not identified as a multicast bearer.

For one embodiment, the first node U11 is handed over by the first bearer cell N13 to the second node N12.

As an embodiment, the first signaling is RRC signaling transmitted by unicast.

As an embodiment, the first signaling comprises a rrcreeconfiguration message.

As an embodiment, the first signaling comprises RadioBearerConfig.

For one embodiment, the first signaling comprises RadioBearerConfig 1.

For one embodiment, the first signaling comprises RadioBearerConfig 2.

For one embodiment, the first signaling comprises RadioBearerConfig 3.

As one embodiment, the first signaling includes a SIB.

As one embodiment, the first signaling comprises sc-mtch-scheduling info.

As an embodiment, the first radio bearer is released during handover, and the first report is RRC signaling.

As an embodiment, the first radio bearer is released during handover, the first report is a PDCP status report, and the first report is sent over a bearer other than the first radio bearer and the second radio bearer.

As an embodiment, the first radio bearer is not released during handover, the first report is a PDCP status report, and the first report is sent over the first radio bearer.

As an embodiment, the first radio bearer is not released in a handover procedure, the first report is RRC signaling, and the first report is sent through a radio bearer other than the first radio bearer and the second radio bearer.

As an embodiment, the first signaling indicates establishment of a second radio bearer for the first service.

For one embodiment, the first report includes a PDCP status report.

As an embodiment, the first report includes a PDCP status report, the first report generated by a PDCP entity associated with the first radio bearer of the first node U11.

As one embodiment, the first radio bearer is reserved after handover.

As an embodiment, the first report is RRC signaling.

As one embodiment, the first report is a control plane message.

As an embodiment, the first report comprises mbmsinterrestindication.

As an embodiment, the first report includes ueAssistanceInformation.

For one embodiment, the first report includes dedicatedSIBRequest-r 16.

As one embodiment, the first report includes ueInformationResponse-r 16.

As an example, the first report includes ueAssistanceInformationEUTRA-r 16.

For one embodiment, the first report includes MBMSIntestrIndication-r 17.

For one embodiment, the first report includes ueAssistanceInformation-r 17.

For one embodiment, the first report includes ueAscistationinformation-r 17.

For one embodiment, the first report includes mbmsinterrestindication 1.

For one embodiment, the first report includes mbmsinterrestindication 2.

As an embodiment, the second node sends the first traffic through the first radio bearer and the second radio bearer simultaneously.

As an embodiment, the second node sends different data packets of the first service through the first radio bearer and the second radio bearer simultaneously.

As an embodiment, the second node sends data of the first traffic over the first radio bearer, which is not received by the first node U11 over the second radio bearer.

As an embodiment, the second node sends the first service through the first radio bearer and the second radio bearer simultaneously, and a state variable of a PDCP entity of the first radio bearer and a state variable of the second radio bearer are kept synchronized.

Example 7

Embodiment 7 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in fig. 7. In fig. 7, U21 corresponds to a first node of the present application, N22 corresponds to a second node of the present application, and N23 is a first bearer cell, which particularly illustrates that the sequence in the present example does not limit the sequence of signal transmission and the sequence of implementation in the present application. Wherein the steps in F71 are optional.

For theFirst node U21In step S7101, a first service is received through a first radio bearer; receiving a second signaling in step S7102; transmitting first information in step S7103; receiving a first signaling in step S7104; transmitting a first report in step S7105; the first service is received through a second radio bearer in step S7106.

ForSecond node N22Transmitting the second signaling in step S7201; receiving the first information in step S7202; transmitting the first signaling in step S7203; receiving the first report in step S7204; transmitting the first service through the second radio bearer in step S7205And (5) transaction.

For theFirst bearer cell N23In step S7301, the first service is transmitted through the first radio bearer.

In embodiment 7, the first node U21 receiving the first traffic over at least the latter of the first radio bearer and the second radio bearer; when a first condition is met, the first node U21 sending the first report; the first condition comprises a transition of reception of the first traffic from the first radio bearer to the second radio bearer; the first radio bearer and the second radio bearer are different in bearer type, and the bearer type comprises a non-unicast bearer and a unicast bearer; the first report is used to indicate SDUs related to the first service and received over the first radio bearer, the first report being higher layer control information.

As an embodiment, the first bearer Cell N23 is a Source Cell (Source Cell) of the first node U21, and the second node N22 is a Target Cell (Target Cell) of the first node U21.

For one embodiment, the first node U21 switches the second node N22 from the first bearer cell N23.

As an embodiment, the first bearer cell N23 sends the first service through the first radio bearer.

For one embodiment, the second node N22 sends the first traffic over the second radio bearer.

As an embodiment, the first bearer cell N23 only sends the first traffic over the first radio bearer.

As an embodiment, the second node N22 sends the first traffic to the first node U21 only over the second radio bearer.

As one embodiment, the first radio bearer is a broadcast bearer.

As an embodiment, the first radio bearer is a multicast bearer.

As one embodiment, the first radio bearer is an MRB bearer.

As an embodiment, the first radio bearer is an SC-MRB bearer.

As an embodiment, the first radio bearer is a DRB bearer identified as a multicast bearer.

As one embodiment, the second radio bearer is a DRB bearer.

As an embodiment, the second radio bearer is a DRB bearer that is not identified as a multicast bearer.

As one embodiment, the second signaling includes a SIB.

As an embodiment, the second signaling comprises a SIB related to multicast traffic.

For one embodiment, the second signaling comprises sc-mtch-scheduling info.

As an embodiment, the sentence "the second signaling indicates that the transmission of the first traffic is switched from the first radio bearer to the second radio bearer" includes the following meanings: the second signaling indicates that a receiver of the first service needs to establish a new radio bearer to receive the first service.

As an embodiment, the sentence "the second signaling indicates that the transmission of the first traffic is switched from the first radio bearer to the second radio bearer" includes the following meanings: the second signaling indicates that a recipient of the first service needs to establish the second radio bearer to receive the first service.

As an embodiment, the sentence "the second signaling indicates that the transmission of the first traffic is switched from the first radio bearer to the second radio bearer" includes the following meanings: the second signaling indicates that the bearer type of the first traffic is changed from a non-multicast bearer to a unicast bearer.

As an embodiment, the sentence "the second signaling indicates that the transmission of the first traffic is switched from the first radio bearer to the second radio bearer" includes the following meaning: the second signaling indicates that a bearer type of the first traffic is different from a type of the first radio bearer used by the first node.

As an embodiment, the sentence "the second signaling indicates that the transmission of the first traffic is switched from the first radio bearer to the second radio bearer" includes the following meaning: the configuration of the first service is contained only in the SIB and not on a control channel related to the multicast service.

As an embodiment, the sentence "the second signaling indicates that the transmission of the first traffic is switched from the first radio bearer to the second radio bearer" includes the following meanings: the configuration of the first service is contained only in the SIB and not in the transport channel scheduling information related to the multicast service.

As an embodiment, the second signaling comprises higher layer signaling.

As an embodiment, the second signaling comprises RRC signaling.

As an embodiment, the second signaling comprises MBMSCountingRequest.

As an embodiment, the second signaling comprises mbscouting request.

As an embodiment, the second signaling includes SC-PTMCountingRequest.

For one embodiment, the second signaling includes a ueInformationRequest-r 9.

As an embodiment, the second signaling includes a ueInformationRequest.

For one embodiment, the second signaling includes a ueInformationRequest-r 17.

In one embodiment, the first information indicates a request to establish a unicast bearer to receive the first service.

For one embodiment, the first information includes a RRCSetupRequest message.

For one embodiment, the first information includes a RRCResumeRequest message.

For one embodiment, the first information includes a RRCResumeRequest1 message.

As one embodiment, the first information includes RRC signaling.

For one embodiment, the first information includes a MAC CE.

As an embodiment, the first information comprises MBMSCountingResponse.

As an embodiment, the first information comprises mbscouting response.

As an embodiment, the first information includes SC-PTMCountingResponse.

For one embodiment, the first information includes an MBMSServiceRequest.

As an embodiment, the first information includes an SC-PTMSServiceRequest.

As one embodiment, the first information includes mbmsinterrestindication.

For one embodiment, the first information includes mbmsinterrestindication 1.

For one embodiment, the first information includes SC-ptmenthestination 1.

As one embodiment, the first signaling comprises higher layer signaling.

As one embodiment, the first signaling comprises RRC signaling.

As an embodiment, the first signaling comprises rrcreeconfiguration.

As an embodiment, the first signaling comprises RRCConnectionReconfiguration.

As an embodiment, the first signaling indicates establishment of the second radio bearer for the first service.

As one embodiment, the first signaling indicates a configuration of the second radio bearer.

As an embodiment, the first report is RRC signaling.

As one embodiment, the first report is a control plane message.

As one embodiment, the first report includes mbmsinterrestindication.

As an embodiment, the first report includes ueAssistanceInformation.

As an embodiment, the first report includes dedicatedSIBRequest-r 16.

As one embodiment, the first report includes ueInformationResponse-r 16.

For one embodiment, the first report includes MBMSIntestrIndication-r 17.

For one embodiment, the first report includes ueAscistationinformation-r 17.

For one embodiment, the first report includes ueAssistanceInformation-r 17.

For one embodiment, the first report includes mbmsinterrestindication 1.

For one embodiment, the first report includes mbmsinterrestindication 2.

For one embodiment, the first report includes a PDCP status report.

As an embodiment, the first report includes a PDCP status report, the first report being generated according to a PDCP entity associated with the first radio bearer of the first node U21.

As an embodiment, the first report includes a PDCP status report, the first report being sent by the second radio bearer.

As an embodiment, the first report is a PDCP status report, the first state variable set is a subset of a set of all state variables of the PDCP entity associated with the second radio bearer, and the first signaling indicates that a value of a state variable in the first state variable set is determined by a value of a state variable corresponding to the PDCP entity associated with the first radio bearer; the first node U21 generates the first report according to the PDCP entity associated with the second radio bearer, the first node U21 sends the first report over the second radio bearer.

Example 8

Embodiment 8 illustrates a schematic diagram of a first time window according to an embodiment of the present application, as shown in fig. 8.

As one embodiment, the first time window includes a period of time that is continuous in the time domain.

For one embodiment, the first time window includes L1 time slots, where L1 is a positive integer.

As an embodiment, one time slot represents one time unit, and the first time window is composed of one time slot.

As an embodiment, one time slot represents one time unit, and the first time window is composed of a plurality of time slots having the same time length.

As an embodiment, the L1 is 1024, and the L1 slots are consecutive.

As an example, the L1 is 10240 and the L1 slots are consecutive.

For an embodiment, the L1 is smaller than 1024, there is at least one slot interval, and there is one slot before the slot interval and one slot after the slot interval respectively belonging to the first time window.

As an embodiment, the L1 is smaller than 10240, there is at least one slot interval, and there is one slot before the slot interval and one slot after the slot interval respectively belonging to the first time window.

As an example, the duration of the first time slot does not exceed 10485.76 seconds (second).

As an embodiment, the duration of the first time slot does not exceed 10.24 seconds (second).

As an embodiment, the duration of the first time slot does not exceed 10 milliseconds (millisecond).

As an embodiment, the duration of the first time slot does not exceed 5 milliseconds (millisecond).

As an example, the duration of the first time slot does not exceed 1 millisecond (millisecond).

As an embodiment, the duration of the first time slot does not exceed 0.5 milliseconds (millisecond).

As one embodiment, the first slot includes 1 multicarrier symbol.

As one embodiment, the first slot includes 7 multicarrier symbols.

As one embodiment, the first slot includes 14 multicarrier symbols.

As an embodiment, the first slot includes 140 multicarrier symbols.

As an embodiment, the multicarrier symbol is an OFDM (Orthogonal Frequency-division Multiplexing) symbol.

As an embodiment, the multi-carrier symbol is a CP-OFDM (Cyclic Prefix-Orthogonal Frequency-division Multiplexing) symbol.

As an embodiment, the multicarrier symbols are SC-FDMA (Single Carrier-frequency division multiple access) symbols.

As an embodiment, the multicarrier symbol is an fbmc (filter Bank multicarrier) symbol.

As an embodiment, the multi-carrier symbol is a DFT-S-OFDM (Discrete Fourier transform-Spread-Orthogonal Frequency Division multiple g) symbol.

As an embodiment, the Multi-Carrier symbol is a UFMC (Universal Filtered Multi-Carrier) symbol.

As an embodiment, the multicarrier symbol is a gfdm (generalized frequency division multiplexing) symbol.

Example 9

Embodiment 9 illustrates a schematic diagram in which a first report is used to determine that a first data set is transmitted through a second radio bearer according to an embodiment of the present application, as shown in fig. 9.

As an embodiment, the first report is used to indicate SDUs related to the first service and received over the first radio bearer.

As an embodiment, the sender of the first service receives the first report and then determines the first data set according to an internal algorithm.

As an embodiment, the first report indicates data that has been sent over the first radio bearer and that has not been received by the first node, and the sender of the first service sends the data that has not been received by the first node as the first set of data over the second radio bearer.

As an embodiment, the sender of the first service determines, as the first data set, data that is related to the first service and that belongs within a specific time window in SDUs received over the first radio bearer, which are indicated by the first report.

As a sub-embodiment of this embodiment, the one particular time window comprises L2 frames, where L2 is a positive integer.

As a sub-embodiment of this embodiment, the one particular time window comprises 1024 frames.

As a sub-embodiment of this embodiment, the one specific time window includes the last MCCH modification period.

As a sub-embodiment of this embodiment, the one particular time window comprises the last SC-MCCH modification period.

As a sub-embodiment of this embodiment, the one specific time window includes a last SC-MCCH modification period.

As a sub-embodiment of this embodiment, the one particular time window comprises the last SC-MTCH scheduling period.

As a sub-embodiment of this embodiment, the one specific time window is determined by the QoS of the first traffic, and only data packets smaller than the maximum delay requirement are included in the first data set.

As an embodiment, the first report is a PDCP status report, and the first data set includes all non-received PDCU SDUs indicated by the first report.

As an embodiment, the first report is a PDCP status report, and the first set of data includes PDCU SDUs for which part indicated by the first report was not received.

Example 10

Embodiment 10 illustrates a schematic diagram in which a first report is used to indicate an SDU related to a first service and received through a first radio bearer according to an embodiment of the present application, as shown in fig. 10.

As an embodiment, the SDUs related to the first service and received over the first radio bearer comprise PDCP SDUs of a user plane of the first service.

As an embodiment, the first report indicates SDUs related to a first service and received over a first radio bearer, and the sender of the first service determines SDUs not received by the first node from the first report.

As an embodiment, the first report indicates SDUs related to a first service and not received over a first radio bearer, and a sender of the first service determines SDUs that have been received by the first node from the first report.

As an embodiment, the first report indicates SDUs related to the first service and received over the first radio bearer and SDUs related to the first service and not received over the first radio bearer.

As one embodiment, the first report includes RRC signaling.

As an embodiment, the first report indicates a sequence number of a last received PDCP SDU.

As an embodiment, the first report indicates a largest one of COUNT values of the received PDCP SDUs.

As an embodiment, the SDU related to the first service and received through the first radio bearer includes an SDU of a multicast service SIB related to the first service.

As a sub-embodiment of this embodiment, the first report indicates a time window of the multicast service SIB, the time window corresponds to a modification period of the multicast service SIB, and data of the first service within the time window and before the time window of the multicast service SIB is considered to have been correctly received.

As an embodiment, the SDU related to the first service and received over the first radio bearer includes an SDU of an RRC message on a multicast control channel related to the first service.

As a sub-embodiment of this embodiment, the first report indicates a time window of an RRC message on the multicast control channel, the time window corresponds to a modification period of the RRC message on the multicast control channel, and data of the first service within and before the time window of the RRC message on the multicast control channel is considered to have been correctly received.

As an embodiment, the SDUs related to the first service and received over the first radio bearer comprise SDUs on a multicast traffic channel related to the first service.

As a sub-embodiment of this embodiment, the first report indicates a time window of SDUs on the multicast traffic channel, the time window corresponds to a scheduling period of SDUs on the multicast traffic channel, and data of the first service within the time window and before the time window of SDUs on the multicast traffic channel is considered to have been correctly received.

Example 11

Embodiment 11 illustrates a block diagram of a processing apparatus for use in a first node according to an embodiment of the present application; as shown in fig. 11. In fig. 11, a processing means 1100 in a first node comprises a first receiver 1101 and a first transmitter 1102. In the case of the embodiment 11, however,

a first receiver 1101 that receives a first service through a first radio bearer; receiving a first signaling, wherein the first signaling indicates to establish a second radio bearer of the first service;

a first transmitter 1102 that transmits a first report;

the first receiver 1101 receiving the first traffic over at least the latter of both the first radio bearer and the second radio bearer;

wherein the first transmitter 1102 transmits the first report when a first condition is met; the first condition comprises a transition of reception of the first traffic from the first radio bearer to the second radio bearer; the first radio bearer and the second radio bearer are different in bearer type, and the bearer type includes a non-unicast bearer and a unicast bearer; the first report is used to indicate SDUs related to the first service and received over the first radio bearer, the first report being higher layer control information.

As an embodiment, the first report is RRC signaling, the first report including a second identification used to determine a first time window corresponding to a last SDU received over the first radio bearer and relating to the first traffic.

As an embodiment, the first report is a PDCP status report, the first set of state variables is a subset of a set of all state variables of the PDCP entity associated with the second radio bearer, and the first signaling indicates that values of the state variables in the first set of state variables are determined by values of the state variables of the PDCP entity associated with the first radio bearer; the first transmitter 1102 generates the first report according to the PDCP entity associated with the second radio bearer, and the first transmitter 1102 transmits the first report through a radio bearer of which the bearer type is a unicast bearer among the first radio bearer and the second radio bearer.

As an embodiment, the first report is a PDCP status report, the first transmitter 1102 generates the first report according to a PDCP entity associated with the first radio bearer, and the first transmitter 1102 transmits the first report through a radio bearer of which the bearer type is a unicast bearer among the first radio bearer and the second radio bearer.

For one embodiment, the first receiver 1101 receives a second signaling;

As an embodiment, the first transmitter 1102 transmits first information, and the first information is used for triggering the first signaling.

As an embodiment, the first receiver 1101 receives a first set of data over the first radio bearer and the second radio bearer, respectively, and the first report is used to determine that the first set of data is sent over the second radio bearer.

As an embodiment, the first node is a User Equipment (UE).

As an embodiment, the first node is a terminal supporting a large delay difference.

As an embodiment, the first node is a terminal supporting NTN.

As an embodiment, the first node is an aircraft.

As an embodiment, the first node is a vehicle-mounted terminal.

As an embodiment, the first node is a relay.

As an embodiment, the first node is a ship.

As an embodiment, the first node is an internet of things terminal.

As an embodiment, the first node is a terminal of an industrial internet of things.

As an embodiment, the first node is a device supporting low-latency highly reliable transmission.

For one embodiment, the first receiver 1101 includes at least one of the antenna 452, the receiver 454, the receive processor 456, the multiple antenna receive processor 458, the controller/processor 459, the memory 460, or the data source 467 of embodiment 4.

For one embodiment, the first transmitter 1102 includes at least one of the antenna 452, the transmitter 454, the transmit processor 468, the multi-antenna transmit processor 457, the controller/processor 459, the memory 460, or the data source 467 of embodiment 4.

Example 12

Embodiment 12 illustrates a block diagram of a processing apparatus for use in a second node according to an embodiment of the present application; as shown in fig. 12. In fig. 12, the processing means 1200 in the second node comprises a second transmitter 1201 and a second receiver 1202. In the case of the embodiment 12, however,

a second transmitter 1201, configured to send a first signaling, where the first signaling indicates establishment of a second radio bearer for a first service; the first service is sent over a first radio bearer;

a second receiver 1202 that receives the first report;

As an embodiment, the first report is a PDCP status report, the first set of state variables is a subset of a set of all state variables of the PDCP entity associated with the second radio bearer, and the first signaling indicates that values of the state variables in the first set of state variables are determined by values of the state variables of the PDCP entity associated with the first radio bearer; a sender of the first report generates the first report according to the PDCP entity associated with the second radio bearer, and the sender of the first report sends the first report through a radio bearer of which the bearer type is a unicast bearer in the first radio bearer and the second radio bearer.

As an embodiment, the first report is a PDCP status report, a sender of the first report generates the first report according to a PDCP entity associated with the first radio bearer, and the sender of the first report sends the first report through a radio bearer of which the bearer type is a unicast bearer among the first radio bearer and the second radio bearer.

As an embodiment, the second transmitter 1201 transmits a second signaling;

For one embodiment, the second receiver 1202 receives first information, which is used to trigger the first signaling.

As an embodiment, the second transmitter 1201 transmits a first set of data over the first and second radio bearers, respectively, and the first report is used to determine that the first set of data is transmitted over the second radio bearer.

As an embodiment, the second node is a base station.

As one embodiment, the second node is a satellite.

As an embodiment, the second node is a UE (user equipment).

For one embodiment, the second node is a gateway.

As an embodiment, the second node is a base station supporting a large delay difference.

For one embodiment, the second transmitter 1201 includes at least one of the antenna 420, the transmitter 418, the transmit processor 416, the multi-antenna transmit processor 471, the controller/processor 475, and the memory 476 of embodiment 4.

For one embodiment, the second receiver 1202 includes at least one of the antenna 420, the receiver 418, the receive processor 470, the multiple antenna receive processor 472, the controller/processor 475, and the memory 476 of embodiment 4.

It will be understood by those skilled in the art that all or part of the steps of the above methods may be implemented by a program instructing relevant hardware, and the program may be stored in a computer-readable storage medium, such as a read-only memory, a hard disk, or an optical disk. Alternatively, all or part of the steps of the above embodiments may be implemented by using one or more integrated circuits. Accordingly, the module units in the above embodiments may be implemented in a hardware form, or may be implemented in a form of software functional modules, and the present application is not limited to any specific form of combination of software and hardware. User equipment, terminal and UE in this application include but not limited to unmanned aerial vehicle, Communication module on the unmanned aerial vehicle, remote control aircraft, the aircraft, small aircraft, the cell-phone, the panel computer, the notebook, vehicle Communication equipment, wireless sensor, network card, thing networking terminal, the RFID terminal, NB-IoT terminal, MTC (Machine Type Communication) terminal, eMTC (enhanced MTC) terminal, the data card, network card, vehicle Communication equipment, low-cost cell-phone, low-cost panel computer, satellite Communication equipment, ship Communication equipment, wireless Communication equipment such as NTN user equipment. The base station or the system device in the present application includes, but is not limited to, a macro cell base station, a micro cell base station, a home base station, a relay base station, a gNB (NR node B) NR node B, a TRP (Transmitter Receiver Point), an NTN base station, a satellite device, a flight platform device, and other wireless communication devices.

The above description is only a preferred embodiment of the present application, and is not intended to limit the scope of the present application. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A first node for wireless communication, comprising:

a first receiver for receiving a first service through a first radio bearer; receiving a first signaling, wherein the first signaling indicates that a second radio bearer of the first service is established;

a first transmitter to transmit a first report;

wherein the first transmitter transmits the first report when a first condition is satisfied; the first condition comprises a transition of reception of the first traffic from the first radio bearer to the second radio bearer; the first radio bearer and the second radio bearer are different in bearer type, and the bearer type includes a non-unicast bearer and a unicast bearer; the first report is used to indicate SDUs related to the first service and received over the first radio bearer, the first report being higher layer control information; the first radio bearer is a unicast bearer and the second radio bearer is a non-unicast bearer.

2. The first node of claim 1,

the first radio bearer adopts a UM mode and the second radio bearer adopts an AM mode.

3. The first node according to claim 1 or 2,

the first report is RRC signaling, the first report including a second identification used to determine a first time window, the first time window being a time window corresponding to a last SDU received over the first radio bearer and related to the first service.

4. The first node according to claim 1 or 2,

the first state variable group comprises at least part of state variables in a set formed by all state variables of the PDCP entity associated with the second radio bearer; the value of the state variable included in the first set of state variables of the PDCP entity associated with the second radio bearer is equal to the value of the state variable of the PDCP entity associated with the first radio bearer; an initial value of a state variable other than the first state variable group of the PDCP entity associated with the second radio bearer is set to 0.

5. The first node of claim 1,

the first report is a PDCP status report, the first transmitter generates the first report according to a PDCP entity associated with the first radio bearer, and the first transmitter transmits the first report through a radio bearer of which the bearer type is a unicast bearer among the first radio bearer and the second radio bearer.

6. The first node of claim 4,

the PDCP-SN-SizeDL of the PDCP entity associated with the first radio bearer and the PDCP-SN-SizeUL of the PDCP entity associated with the second radio bearer are configured to be different.

7. The first node of claim 1, comprising:

the first transmitter, which transmits first information, the first information being used to trigger the first signaling; the first information includes a rrcresemequest message or a rrcresemequest 1 message.

8. A second node for wireless communication, comprising:

the second transmitter is used for transmitting a first signaling, and the first signaling indicates that a second radio bearer of the first service is established; the first service is sent through a first radio bearer;

a second receiver receiving the first report;

wherein a recipient of the first signaling sends the first report when a first condition is satisfied; the first condition comprises a transition of the reception of the first traffic from the first radio bearer to the second radio bearer; the first radio bearer and the second radio bearer are different in bearer type, and the bearer type comprises a non-unicast bearer and a unicast bearer; the first report is used to indicate SDUs related to the first service and received over the first radio bearer, the first report being higher layer control information; the first radio bearer is a unicast bearer and the second radio bearer is a non-unicast bearer.

9. The second node of claim 8,

10. The second node according to claim 8 or 9,

11. The second node according to claim 8 or 9,

12. The second node of claim 8,

the first report is a PDCP status report, a sender of the first report generates the first report according to a PDCP entity associated with the first radio bearer, and the sender of the first report sends the first report through a radio bearer of which the bearer type is a unicast bearer among the first radio bearer and the second radio bearer.

13. The second node of claim 11,

the PDCP-SN-SizeDL of the PDCP entity associated with the first radio bearer and the PDCP-SN-SizeUL of the PDCP entity associated with the second radio bearer are configured differently.

14. The second node of claim 8, comprising:

sending first information, the first information being used to trigger the first signaling; the first information includes a rrcresemequest message or a rrcresemequest 1 message.

15. A method in a first node used for wireless communication, comprising:

receiving a first service through a first radio bearer; receiving a first signaling, wherein the first signaling indicates to establish a second radio bearer of the first service;

sending a first report;

wherein the first report is transmitted when a first condition is satisfied; the first condition comprises a transition of reception of the first traffic from the first radio bearer to the second radio bearer; the first radio bearer and the second radio bearer are different in bearer type, and the bearer type comprises a non-unicast bearer and a unicast bearer; the first report is used to indicate SDUs related to the first service and received over the first radio bearer, the first report being higher layer control information; the first radio bearer is a unicast bearer and the second radio bearer is a non-unicast bearer.

16. The method in a first node according to claim 15,

17. The method in a first node according to claim 15 or 16,

18. The method in a first node according to claim 15 or 16,

19. The method in a first node according to claim 15,

the first report is a PDCP status report, the first report is generated according to a PDCP entity associated with the first radio bearer, and the first report is transmitted through a radio bearer of which the bearer type is a unicast bearer among the first radio bearer and the second radio bearer.

20. The method in a first node according to claim 18,

21. A method in a first node according to claim 15, comprising:

22. A method in a second node used for wireless communication, comprising:

sending a first signaling, wherein the first signaling indicates that a second radio bearer of a first service is established; the first service is sent over a first radio bearer;

receiving a first report;

wherein a recipient of the first signaling sends the first report when a first condition is satisfied; the first condition comprises a transition of reception of the first traffic from the first radio bearer to the second radio bearer; the first radio bearer and the second radio bearer are different in bearer type, and the bearer type includes a non-unicast bearer and a unicast bearer; the first report is used to indicate SDUs related to the first service and received over the first radio bearer, the first report being higher layer control information; the first radio bearer is a unicast bearer and the second radio bearer is a non-unicast bearer.

23. The method in a second node according to claim 22,

the first radio bearer adopts a UM mode, and the second radio bearer adopts an AM mode.

24. Method in a second node according to claim 22 or 23,

25. Method in a second node according to claim 22 or 23,

26. The method in a second node according to claim 22,

27. The method in a second node according to claim 22,

28. A method in a second node according to claim 22, comprising:

receiving first information, the first information being used to trigger the first signaling; the first information includes a rrcresemequest message or a rrcresemequest 1 message.