CN113938841B

CN113938841B - Method and device used in node of wireless communication

Info

Publication number: CN113938841B
Application number: CN202010672869.6A
Authority: CN
Inventors: 张晓博
Original assignee: Shanghai Langbo Communication Technology Co Ltd
Current assignee: Shanghai Langbo Communication Technology Co Ltd
Priority date: 2020-07-14
Filing date: 2020-07-14
Publication date: 2022-10-28
Anticipated expiration: 2040-07-14
Also published as: CN113938841A

Abstract

The invention discloses a method and an apparatus in a node used for wireless communication. The first node monitors the state of the first link and determines whether a condition in the first condition set is met; when any condition in the first condition set is met and the first DRB does not bear the MBMS service, releasing the first DRB; and when any condition in the first condition set is met and the first DRB bears the MBMS service, reserving the first DRB. By reserving the DRB, the method and the device can reduce the reconfiguration frequency of the DRB and reduce signaling overhead.

Description

Method and apparatus in a node used for wireless communication

Technical Field

The present application relates to transmission methods and apparatuses in wireless communication systems, and more particularly, to multicast and broadcast related transmission schemes and apparatuses 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 various application scenarios, research on New air interface technology (NR, new Radio) (or Fifth Generation, 5G) is decided on 3GPP (3 rd Generation Partner Project, third Generation partnership Project) RAN (Radio Access Network) #72 clubs, and standardization Work on NR starts on 3GPP RAN #75 clubs that pass through NR.

Relay communication is a common method in cellular network communication, and data of a source node reaches a remote node through forwarding of a relay node. The source node and the remote node are typically a base station device and a user equipment, and the relay node may be a network device or a user equipment. Common relay communications include layer 1 relay that forwards information bits recovered at a physical layer, and layer 2 relay that forwards information bits recovered at a layer 2.

D2D (Device to Device) or V2X (Vehicle to outside) is an important application scenario in cellular communication, and can implement direct communication between two communication terminals. In the 3GPP (3 rd Generation Partner Project) 4G and 5G standards, D2D/V2X was introduced.

Broadcast (Broadcast)/Multicast (Multicast) transmission techniques are widely used in cellular systems, such as MBMS (Multimedia Broadcast Multicast Service) in 4G LTE (Long Term Evolution). The broadcast/multicast transmission is mainly characterized in that the network equipment can simultaneously transmit the same broadcast/multicast data to a plurality of terminal nodes, and the broadcast/multicast transmission has important value in scenes such as broadcast television, disaster early warning, emergency service, industrial control, vehicle networking and the like. In LTE MBMS, an eNB schedules a plurality of terminal nodes to receive a PDSCH (Physical Downlink Shared Channel) or a PMCH (Physical Multicast Channel) including broadcast/Multicast data through one PDCCH (Physical Downlink Control Channel). The broadcast/multicast-related identifiers include SC-RNTI (Single Cell RNTI ), SC-N-RNTI (Single Cell Notification RNTI, single Cell Notification RNTI) and G-RNTI (Group RNTI ).

The standardization of the provision of Multicast and broadcast services by NR in SC-PTM (Single Cell Point-to-multi iPoint) was started at the 3gpp ran #86 session through WI (Work Item) of NR Multicast.

Disclosure of Invention

The inventor finds out through research that there is no solution on how to perform DRB management when MBMS service is transmitted by means of unicast on the sidelink.

In view of the above, the present application discloses a solution. It should be noted that, although the above description uses the scenario of communication between the network device and the terminal device as an example, the present application is also applicable to other communication scenarios (for example, the scenario of terminal-to-terminal communication), and achieves similar technical effects. Furthermore, the adoption of a unified solution for different scenarios (including but not limited to scenarios of communication between network devices and terminals and terminal-to-terminal communication) also helps to reduce hardware complexity and cost. Without conflict, embodiments and features in embodiments in a first node of the present application may be applied to a second node and vice versa. The embodiments and features of the embodiments of the present application may be combined with each other arbitrarily without conflict.

As an example, the term (telematics) in the present application is explained with reference to the definition of the specification protocol TS36 series of 3 GPP.

As an example, the terms in the present application are explained with reference to the definitions of the 3GPP specification protocol TS38 series.

As an example, the terms in the present application are explained with reference to the definitions of the 3GPP specification protocol TS37 series.

As an example, the terms in this application are interpreted with reference to the definition of the IEEE (Institute of Electrical and Electronics Engineers) specification protocol.

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

monitoring the state of the first link to determine whether a condition in the first condition set is satisfied; when any condition in the first condition set is met and the first DRB does not bear the MBMS service, releasing the first DRB; when any condition in the first condition set is met and the first DRB bears the MBMS service, reserving the first DRB;

wherein the first link is a sidelink and the second node is a communication node of the first link, the second node being identified by a first identity; the first DRB belongs to a first link; the first set of conditions includes at least one of a maximum number of RLC retransmissions for the second node for the destination and a maximum number of consecutive HARQ DTX's for the second node.

As an embodiment, the first link is a Unicast (Unicast) link.

For one embodiment, the second node is a destination communication node of the first link.

As an embodiment said first identity comprises a link layer identity.

As an embodiment, the first identity comprises a number of information bits being a positive integer multiple of 8.

As one embodiment, the first identity identifies a destination communication node of the first link.

As an embodiment, the act of determining whether a condition in the first set of conditions is met is performed at the RRC layer.

As one embodiment, the behavior monitoring the state of the first link includes: monitoring the number of RLC retransmissions destined for the second node.

As one embodiment, the behavior monitoring the state of the first link includes: monitoring a number of consecutive HARQ DTX of the second node.

As an embodiment, the phrase is determined by receiving an indication of an RLC entity for the second node to reach a maximum number of RLC retransmissions for the destination.

As an embodiment, the number of consecutive HARQ DTX's for the second node is for the first node.

As an embodiment, the phrase the maximum number of consecutive HARQ DTX counts of the second node is determined by receiving an indication of a MAC entity.

Specifically, according to an aspect of the present application, the method is characterized in that the act of reserving the first DRB includes:

continuing to monitor the status of the first link, suspending sending data packets via the first DRB until a first signal is received, the first signal being sent by a correspondent node of the first identity.

As one embodiment, the destination of the first signal is the first node.

As an example, the destination of the first signal is a link layer identity maintained by the first node.

Specifically, according to one aspect of the present application, the method is characterized by further comprising:

releasing the first DRB when any one condition in a second condition set is met;

wherein the second condition set comprises at least one of the first timer timeout, the SRB2 integrity check failure, and the SRB3 integrity check failure.

As one embodiment, the first timer is T400.

As an embodiment, the first timer is started when the first node sends a first message; the first timer is stopped when the first node receives a response to the first message.

As a sub-embodiment of the above embodiment, the first message is an RRC message.

For one embodiment, the first timer is started when any one of the first set of conditions is satisfied.

Specifically, according to an aspect of the present application, the method is characterized by further comprising:

when the first DRB is reserved, the SRB belonging to the first link is reserved; when the first DRB is released, the SRB belonging to the first link is released.

As an embodiment, the SRB belonging to the first link includes at least one of SRB0, SRB1, SRB2, and SRB3.

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

a first receiver for monitoring the state of the first link and determining whether a condition in the first set of conditions is satisfied; when any condition in the first condition set is met and the first DRB does not bear the MBMS service, releasing the first DRB; when any condition in the first condition set is met and the first DRB bears the MBMS service, reserving the first DRB;

As an embodiment, the present application has the following advantages: by reserving the DRB, the reconfiguration times of the DRB can be reduced, and the signaling overhead is reduced.

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 illustrates a process flow diagram for a first node according to one 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 a radio protocol architecture of a user plane and a control plane according to an embodiment of the present application;

fig. 4 shows a schematic diagram of a first communication device and a second communication device according to an embodiment of the application;

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

FIG. 6 shows a block diagram of a processing arrangement for use in the first node;

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 of the present application can be arbitrarily combined with each other without conflict.

Example 1

Embodiment 1 illustrates a processing flow diagram of a first node of an embodiment of the present application, as shown in fig. 1. In fig. 1, each block represents a step. In particular, the order of steps in the blocks does not represent a specific temporal sequence between the various steps.

In embodiment 1, a first node in the present application monitors the state of a first link in step S101, and determines whether a condition in a first condition set is satisfied; in step S102, when any condition in the first condition set is satisfied and the first DRB does not carry the MBMS service, releasing the first DRB; in step S103, when any condition in the first condition set is satisfied and the first DRB carries the MBMS service, the first DRB is reserved.

Wherein said first link is a sidelink and the second node is a communication node of said first link, said second node being identified by a first identity; the first DRB belongs to a first link; the first set of conditions includes at least one of a maximum number of RLC retransmissions for the second node for the destination and a maximum number of consecutive HARQ DTX's for the second node.

As one embodiment, the behavior monitoring the state of the first link includes: monitoring a number of consecutive HARQ DTX for any RB of the first link.

As one embodiment, the behavior monitoring the state of the first link includes: monitoring the number of RLC retransmissions of any RB of the first link.

As one embodiment, the behavior monitoring the state of the first link includes: receiving a channel quality measurement report for the first link.

As one embodiment, the behavior monitoring the state of the first link includes: monitoring a channel quality of the first link.

As a sub-embodiment of the foregoing embodiment, the channel Quality of the first link is indicated by at least one of RSRP (Reference Signal Receiving Power), RSRQ (Reference Signal Receiving Quality), and RSSI (Received Signal Strength Indication).

As a sub-embodiment of the above embodiment, the channel quality of the first link is obtained based on measurements on data signals or reference signals.

For one embodiment, the phrase the state of the first link includes: a number of RLC retransmissions destined for the second node.

As one embodiment, the phrase state of the first link includes: the number of continuous HARQ (Hybrid Automatic Repeat reQuest) DTX (Discontinuous transmission) of the second node.

As an embodiment, the act of determining whether a condition in the first set of conditions is satisfied is performed at an RRC layer.

As an embodiment, the act of determining whether a condition in the first set of conditions is met is performed at an upper layer of the RLC layer.

As an embodiment, the first DRB is used for communication between the first node and the second node.

As one embodiment, the act of releasing the first DRB comprises: releasing at least one of the PDCP entity of the first DRB and the SDAP entity of the first DRB.

As one embodiment, the act of releasing the first DRB comprises: and releasing the RLC entity and the corresponding logical channel of the first DRB.

As one embodiment, the act of reserving the first DRB includes continuing to send data packets through the first DRB.

As an embodiment, the act of reserving the first DRB includes continuing to transmit MBMS traffic only through the first DRB.

As an embodiment, the action of reserving the first DRB includes continuing to transmit data packets of the MBMS service only through the first DRB.

As one embodiment, the act of reserving the first DRB includes maintaining configuration information of the first DRB.

As a sub-embodiment of the foregoing embodiment, the configuration information of the first DRB includes at least one of a PDCP entity configuration, an SDAP entity configuration, an RLC entity configuration, and a logical channel configuration of the first DRB.

As one embodiment, the acts of reserving the first DRB include maintaining a first SRB over which configuration information for the first DRB is sent.

As a sub-embodiment of the above embodiment, the first SRB is SRB0.

As a sub-embodiment of the above embodiment, the first SRB is SRB1.

As a sub-embodiment of the above embodiment, the first SRB is SRB2.

As a sub-embodiment of the above embodiment, the first SRB is SRB3.

As one embodiment, the act of retaining the first DRB includes maintaining configuration information of the first DRB but no longer sending data packets through the first DRB.

As an embodiment, the act of reserving the first DRB includes maintaining configuration information of the first DRB but not sending MBMS services through the first DRB.

As an embodiment, the action of reserving the first DRB includes maintaining configuration information of the first DRB, but no longer transmitting data packets of the MBMS service through the first DRB.

As one embodiment, the act of reserving the first DRB includes maintaining a first SRB over which configuration information for the first DRB is sent.

As a sub-embodiment of the foregoing embodiment, the configuration information of the first DRB includes at least one of a PDCP entity configuration of the first DRB, an SDAP entity configuration of the first DRB, and a MAC configuration of the first DRB.

As an embodiment, when the first DRB is reserved, the SRB belonging to the first link is reserved.

As an embodiment, when the first DRB is released, the SRB belonging to the first link is released.

As an embodiment, when the first DRB is reserved, it is considered that the PC5-RRC connection destined for the second node is reserved.

As a sub-embodiment of the foregoing embodiment, the SRB belonging to the first link includes at least one of SRB0, SRB1, SRB2, and SRB3.

As an embodiment, when all the conditions in the first condition set are not satisfied, the data packet is continuously transmitted through the first DRB.

As an embodiment, when all conditions in the first condition set are not satisfied, the first DRB is retained.

As an embodiment, the first link is a Unicast (Unicast) link.

As an embodiment, the first identity comprises a link layer identity.

As an embodiment, the first identity identifies a destination communication node of the first link.

As an embodiment, the second node receives the MBMS service through the first DRB.

As an embodiment, the second node receives a data packet of the MBMS service through the first DRB.

As a sub-embodiment of the above embodiment, the RLC entity is an RLC entity of a secondary link.

As a sub-embodiment of the above embodiment, the MAC entity is a MAC entity of the sidelink.

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 the 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 UE (User Equipment) 201, ng-RAN (next generation radio access network) 202,5gc (5G Core network )/EPC (Evolved Packet Core) 210, hss (Home Subscriber Server), home Subscriber Server)/UDM (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 bs (gnbs) 203 and other gnbs 204. The gNB203 provides user and control plane protocol terminations towards the UE 201. The gnbs 203 may connect 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/EPC210. 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 via an S1/NG interface. The 5GC/EPC210 includes MME (Mobility Management entity)/AMF (Authentication Management Field)/SMF (session Management Function) 211, other MME/AMF/SMF214, S-GW (Service 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/EPC210. 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/UPF213. 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 and the UE241 are connected through a PC5 Reference Point (Reference Point).

As an embodiment, the ProSe function 250 is connected with the UE201 and the UE241 through PC3 reference points, respectively.

As an embodiment, the ProSe function 250 is connected with the ProSe application server 230 through a PC2 reference point.

As an embodiment, the ProSe application server 230 is connected to the ProSe application of the UE201 and the ProSe application of the UE241 through a PC1 reference point, respectively.

As an embodiment, the UE201 and the gNB203 are connected through a Uu interface.

As an embodiment, the wireless link between the UE201 and the UE241 corresponds to a Sidelink (SL) in the present application.

As an embodiment, the radio link from the UE201 to the NR node B is an uplink.

As an embodiment, the radio link from the NR node B to the UE201 is the downlink.

As an embodiment, the first node and the second node in this application are the UE201 and the UE241, respectively.

As an embodiment, the UE201 supports sidelink transmission.

As an embodiment, the UE201 supports a PC5 interface.

As an embodiment, the UE201 supports the Uu interface.

As an embodiment, the UE201 supports relay transmission.

As an embodiment, the UE241 supports relay transmission.

For one embodiment, the UE241 supports sidelink transmission.

As an embodiment, the UE241 supports a PC5 interface.

As an embodiment, the gNB203 supports the Uu interface.

As an example, the gNB203 supports Integrated Access and Backhaul (IAB).

As an example, the gNB203 is a macro cellular (MarcoCellular) base station.

As an embodiment, the gNB203 is a Micro Cell (Micro Cell) base station.

As an embodiment, the gNB203 is a pico cell (PicoCell) base station.

As an embodiment, the gNB203 is a home base station (Femtocell).

As an embodiment, the gNB203 is a base station device supporting a large delay difference.

As an example, the gNB203 is a flight platform device.

As an embodiment, the gNB203 is a satellite device.

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 radio protocol architecture for the user plane 350 and the control plane 300, fig. 3 showing the radio protocol architecture for the first node (RSU in UE or V2X, in-vehicle device or in-vehicle communication module) and the second node (gNB, RSU in UE or V2X, in-vehicle device or in-vehicle communication module), or the control plane 300 between 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 PHY301. Layer 2 (L2 layer) 305 is above the PHY301, and is responsible for the link between the first and second nodes and the two UEs through the PHY301. 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 data ciphering and integrity protection, and the PDCP sublayer 304 also provides handover support for a second node by a first node. The RLC sublayer 303 provides segmentation and reassembly of packets, retransmission of missing packets by ARQ, and the RLC sublayer 303 also provides duplicate packet detection and protocol error detection. The MAC sublayer 302 provides mapping between logical and transport channels and multiplexing of logical 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. A 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), and the radio protocol architecture for the first and second nodes in the user plane 350 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 a Service Data Adaptation Protocol (SDAP) sublayer 356, and the SDAP sublayer 356 is responsible for mapping between QoS streams and Data Radio Bearers (DRBs) to support Service diversity. Although not shown, the first node may have several upper layers above the L2 layer 355, including 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 embodiment, the entities of the multiple sub-layers of the control plane in fig. 3 constitute an SRB (Signaling Radio bearer) in the vertical direction.

As an embodiment, the entities of the multiple sub-layers of the control plane in fig. 3 constitute a DRB (data radio bearer) in the vertical direction.

The radio protocol architecture of fig. 3 applies to the first node in this application as an example.

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

As an example, the

L2 layer

305 or 355 belongs to a higher layer.

As an embodiment, the RRC sublayer 306 in the L3 layer belongs to a higher layer.

As an example, the PDCP sublayer 354 belongs to a higher layer.

As an example, the SDAP sublayer 356 belongs to higher layers.

As an embodiment, the L3 layer belongs to a higher layer.

As an example, the acts described herein determine whether a condition in the first set of conditions is satisfied is performed at RRC306.

As an example, the phrase in this application is determined by receiving an indication of an

RLC sublayer

303 or 353 entity for the second node to reach a maximum number of RLC retransmissions for the destination.

As an embodiment, the phrase herein is determined by receiving an indication of the

MAC sublayer

302 or 352 entity that the maximum number of consecutive HARQ DTX's of the second node has been reached.

As an embodiment, the first signal in this application is generated in the RRC306.

As an embodiment, the first signal in this application is generated in the

MAC sublayer

302 or 352.

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 410 and a second communication device 450 communicating with each other in an access network.

The first communications 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.

The second 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.

In the transmission from the first communication device 410 to the second communication device 450, at the first communication device 410, upper layer data packets from the core network are provided to the controller/processor 475. The controller/processor 475 implements the functionality of the L2 layer. In transmissions from the first 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 second communications device 450 based on various priority metrics. The controller/processor 475 is also responsible for retransmission of lost packets and signaling to the second 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 450 and 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 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 that carry 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 first communications device 410 to the second communications device 450, at the second communications device 450, each receiver 454 receives a signal through its respective antenna 452. 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 streams from 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 second 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 first 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 functions 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 first 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 second communications device 450 to the first communications device 410, a data source 467 is used at the second 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 first communications apparatus 410 described in the transmission from the first communications apparatus 410 to the second 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 first communications device 410. The transmit processor 468 performs modulation mapping, channel coding, and digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming, by the multi-antenna transmit processor 457, and then the transmit processor 468 modulates the resulting spatial streams into multi-carrier/single-carrier symbol streams, which are provided to the different antennas 452 via the 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 that is provided to the antenna 452.

In a transmission from the second communication device 450 to the first communication device 410, the functionality at the first communication device 410 is similar to the receiving functionality at the second communication device 450 described in the transmission from the first communication device 410 to the second 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. The 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 transmissions from the second communications device 450 to the first communications 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 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 first communication device 450 means at least: monitoring the state of the first link to determine whether a condition in the first condition set is satisfied; when any condition in the first condition set is met and the first DRB does not bear the MBMS service, releasing the first DRB; when any condition in the first condition set is met and the first DRB bears the MBMS service, reserving the first DRB; wherein the first link is a sidelink and the second node is a communication node of the first link, the second node being identified by a first identity; the first DRB belongs to a first link; the first set of conditions includes at least one of a maximum number of RLC retransmissions for the second node for the destination and a maximum number of consecutive HARQ DTX's for the second node.

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: monitoring the state of the first link to determine whether a condition in the first set of conditions is satisfied; when any condition in the first condition set is met and the first DRB does not bear the MBMS service, releasing the first DRB; when any condition in the first condition set is met and the first DRB bears the MBMS service, reserving the first DRB; wherein the first link is a sidelink and the second node is a communication node of the first link, the second node being identified by a first identity; the first DRB belongs to a first link; the first set of conditions includes at least one of a maximum number of RLC retransmissions for the second node for the destination and a maximum number of consecutive HARQ DTX's for the second node.

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.

As an embodiment, the first node in this application includes the first communication device 450, and the second node in this application includes the second communication device 410.

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

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

As an example, the first communication device 450 is a gNB.

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

As one example, at least one of the antenna 452, the receiver 454, the multi-antenna receive processor 458, the receive processor 456, the controller/processor 459, the memory 460, the data source 467 may be used to monitor the status of the first link.

As one example, at least one of the antenna 452, the receiver 454, the multi-antenna receive processor 458, the receive processor 456, the controller/processor 459, the memory 460, the data source 467 may be utilized to receive the first signal as described herein.

As one example, at least one of { the antenna 420, the receiver 418, the multi-antenna reception processor 472, the reception processor 470, the controller/processor 475, the memory 476} is used for transmitting the first signal in the present 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, the order of the steps in the blocks does not represent a specific chronological relationship between the individual steps. In fig. 5, the steps in the dashed box F1 and the dashed box F2 are optional.

For theFirst node U1Monitoring the status of the first link in step S5101, and determining whether a condition in the first condition set is satisfied; when any condition in the first condition set is satisfied and the first DRB does not carry the MBMS service, releasing the first DRB in step S5102; when any condition in the first condition set is satisfied and the first DRB carries the MBMS service, jumping to step S5103 to retain the first DRB; continuing to monitor the status of the first link, suspending sending of data packets through the first DRB until a first signal is received in step S5104; releasing the first DRB when any one of the conditions in the second condition set is satisfied in step S5105;

for theSecond node U2In step S5201, a first signal is transmitted;

wherein the first link is a sidelink and the second node is a communication node of the first link, the second node being identified by a first identity; the first DRB belongs to a first link; the first set of conditions includes at least one of a maximum number of RLC retransmissions for the second node destined for the second node and a maximum number of consecutive HARQ DTX for the second node; the second condition set comprises at least one of the first timer is overtime, the SRB2 integrity check fails, and the SRB3 integrity check fails.

As an embodiment, the first node and the second node are connected through a Uu interface.

As an embodiment, the first node and the second node are connected through a PC5 interface.

As an embodiment, the destination of the first signal is the first node.

As an embodiment, the first signal is transmitted on a PUSCH (Physical uplink Shared Channel).

As an embodiment, the first signal is transmitted on a psch (Physical Sidelink Shared Channel).

As an embodiment, the first signal is transmitted on a PSCCH (Physical Sidelink Control Channel).

As an embodiment, the first signal is transmitted on a PSFCH (Physical Sidelink Feedback Channel).

As an embodiment, the first signal comprises a keep-alive message.

As an embodiment, the first signal includes an RRC signaling.

As an embodiment, the first signal includes one MAC PDU (Protocol Data Unit).

As an embodiment, after receiving the first signal, the first node resumes sending data packets through the first DRB.

As an embodiment, the first DRB carries an MBMS service.

As an embodiment, when any condition in the first condition set is satisfied and the first DRB carries the MBMS service, the first timer is started.

As one embodiment, the first timer is T400.

As a sub-embodiment of the above-mentioned embodiments, the first message comprises an rrcreconconfigurationsidelink message.

As a sub-embodiment of the above, the response of the first message comprises

RRCReconfigurationCompleteSidelink message.

As an embodiment, the phrase SRB2 integrity check failure is determined by receiving an indication of a lower layer.

As an embodiment, the phrase SRB3 integrity check failure is determined by receiving an indication of a lower layer.

As a sub-embodiment of the above embodiment, the lower layer includes a PDCP layer.

As an embodiment, the first node is in an RRC connected state.

For one embodiment, the first node is in an RRC idle state.

For one embodiment, the first node is in an RRC inactive state.

Example 6

Embodiment 6 illustrates a block diagram of a processing apparatus used in a first node, as shown in fig. 6. In embodiment 6, the first node processing apparatus 600 includes a first transmitter 601 and a first receiver 602.

The first receiver 602, monitoring the status of the first link, determining whether a condition in the first set of conditions is satisfied; when any condition in the first condition set is met and the first DRB does not bear the MBMS service, releasing the first DRB; when any condition in the first condition set is met and the first DRB bears the MBMS service, reserving the first DRB;

in embodiment 6, said first link is a sidelink, the second node is a communication node of said first link, said second node is identified by a first identity; the first DRB belongs to a first link; the first set of conditions includes at least one of a maximum number of RLC retransmissions for the second node for the destination and a maximum number of consecutive HARQ DTX's for the second node.

As an embodiment, the first link is a Unicast (Unicast) link.

As an embodiment, the first identity comprises a link layer identity.

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

The first transmitter 601 includes, for one embodiment, the antenna 452, the transmitter/receiver 454, the multi-antenna transmitter processor 457, the transmit processor 468, the controller/processor 459, the memory 460, and the data source 467 of fig. 4 of the present application.

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

For one embodiment, the first receiver 602 includes the antenna 452, the receiver 454, the multiple antenna receive processor 458, the receive processor 456, the controller/processor 459, the memory 460, and the data source 467 of fig. 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 instructing relevant hardware through a program, 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 foregoing embodiments may be implemented in the form of hardware, or may be implemented in the form of software functional modules, and the present application is not limited to any specific combination of software and hardware. The first node in this application includes but not limited to wireless communication devices such as cell-phone, panel computer, notebook, network card, low-power consumption equipment, eMTC equipment, NB-IoT equipment, vehicle communication equipment, aircraft, unmanned aerial vehicle, telecontrolled aircraft. The second node in this application includes but not limited to wireless communication devices such as cell-phone, panel computer, notebook, network card, low-power consumption equipment, eMTC equipment, NB-IoT equipment, vehicle communication equipment, aircraft, unmanned aerial vehicle, remote control plane. The third node in this application includes but not limited to cell-phone, panel computer, notebook, network card, low-power consumption equipment, eMTC equipment, NB-IoT equipment, vehicle communication equipment, aircraft, unmanned aerial vehicle, wireless communication equipment such as telecontrolled aircraft. User equipment or UE or terminal in this application include but not limited to cell-phone, panel computer, notebook, network card, low-power consumption equipment, eMTC equipment, NB-IoT equipment, vehicle communication equipment, aircraft, unmanned aerial vehicle, wireless communication equipment such as telecontrolled aircraft. The base station device, the base station or the network side 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, an eNB, a gNB, a transmission and reception node TRP, a GNSS, a relay satellite, a satellite base station, an air base station, 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:

wherein the first link is a sidelink, the second node is a communication node of the first link, and the second node has a first identity; the first DRB belongs to a first link; the first set of conditions includes at least one of a maximum number of RLC retransmissions for the second node for the destination and a maximum number of consecutive HARQ DTX's for the second node.

2. The first node of claim 1, wherein the act of reserving the first DRB comprises:

continuing to monitor the status of the first link, suspending transmission of data packets via the first DRB until a first signal is received, the first signal being transmitted by the first identity-enabled communication node.

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

releasing the first DRB when any condition in a second condition set is met;

4. The first node according to any of claims 1 to 3, comprising:

5. The first node according to any of claims 1 to 4, comprising:

the first identity comprises a link layer identity.

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

monitoring the state of the first link to determine whether a condition in the first set of conditions is satisfied; when any condition in the first condition set is met and the first DRB does not bear the MBMS service, releasing the first DRB; when any condition in the first condition set is met and the first DRB bears the MBMS service, reserving the first DRB;

7. The method in a first node of claim 6, wherein the act of reserving the first DRB comprises:

8. The method in the first node according to claim 6 or 7, further comprising:

releasing the first DRB when any condition in a second condition set is met;

9. The method in the first node according to any of claims 6-8, further comprising:

10. A method in a first node according to any of claims 6-9, comprising:

the first identity comprises a link layer identity.