Method and device for cell switching in wireless communication

Abstract

Disclosed are a method and device for cell handover in wireless communication, comprising: receiving a first signaling, the first signaling configuring a first radio bearer, a first RLC bearer and a second RLC bearer, the first radio bearer being a multicast broadcast service radio bearer, the second radio bearer being a multicast broadcast service radio bearer, the first RLC bearer being a multicast broadcast service radio bearer, and the second RLC bearer being a multicast broadcast service radio bearer; both the first RLC bearer and the second RLC bearer serve the first radio bearer, an RLC entity corresponding to the first RLC bearer is configured as PTM, and an RLC entity corresponding to the second RLC bearer is not configured as PTM; receiving a second signaling, wherein the second signaling indicates cell switching; and performing cell switching, which comprises the step of releasing a logical channel identifier associated with only the first RLC bearer or the second RLC bearer. According to the method and the device, LTM cell switching can be better supported, misoperation can be avoided, and continuity of data communication is guaranteed.

Description

Technical Field

[0001] The present application relates to a method for cell switching in a cellular wireless communication system, and in particular to a mobility management cell switching triggered by layer 1 and layer 2. Background Art

[0002] In the future, the application scenarios of wireless communication systems will become more and more diversified, and different application scenarios will put forward different performance requirements for the system. In order to meet the different performance requirements of various application scenarios, the 3GPP (3rd Generation Partner Project) RAN (Radio Access Network) #72 plenary meeting decided to study the new radio (NR) (or Fifth Generation, 5G) technology, and the NR WI (Work Item) was passed at the 3GPP RAN #75 plenary meeting, and the standardization work on NR began.

[0003] In communication, both LTE (Long Term Evolution) and 5G NR involve accurate reception of reliable information, optimized energy efficiency, determination of information validity, flexible resource allocation, scalable system structure, efficient non-access layer information processing, low service interruption and drop rate, and support for low power consumption. This is of great significance to the normal communication between base stations and user equipment, the reasonable scheduling of resources, and the balancing of system loads. It can be said to be the cornerstone of high throughput, meeting the communication needs of various services, improving spectrum utilization, and improving service quality. It is indispensable for eMBB (ehanced Mobile BroadBand), URLLC (Ultra Reliable Low Latency Communication) and eMTC (enhanced Machine Type Communication). At the same time, in IIoT (Industrial Internet of Things), V2X (Vehicular to X), device to device, unlicensed spectrum communication, user communication quality monitoring, network planning and optimization, TN (Territial Network), dual connectivity system, wireless resource management and multi-antenna codebook selection, signaling design, neighbor management, business management, and beamforming, there are extensive demands. Information transmission methods are divided into broadcast and unicast. Both transmission methods are essential for 5G systems because they are very helpful in meeting the above requirements.

[0004] As the scenarios and complexity of the system continue to increase, higher requirements are placed on reducing interruption rates, reducing latency, enhancing reliability, enhancing system stability, business flexibility, and power saving. At the same time, compatibility between different versions of different systems also needs to be considered during system design. Summary of the invention

[0005] Researchers have found that LTM (L1 / L2 Triggered Mobility) cell switch has significant technical progress compared to traditional cell switch based on layer 3, which can greatly shorten the switching delay and better ensure the continuity of data transmission. The reason why LTM cell switch can achieve the above technical progress is that it adopts the combination of layer 1 / layer 2 and layer 3. For many years since the birth of mobile communications, the network only supports cell switch based on layer 3, which shows that it is very technically challenging to support cell switch based on the combination of layer 1 / layer 2 and layer 3. One of these technical challenges is the need for close and smooth interaction and collaboration between the RRC sublayer and the MAC sublayer, and the other is the need to optimize the L2 protocol entity to ensure the continuity of communication. Researchers have found that in the cell switch scenario, especially the LTM cell switch scenario, for the first radio bearer of the broadcast multicast service, it is a problem that needs to be solved to release the logical channel identifiers associated with which RLC bearers serving the first radio bearer.

[0006] In view of the above-mentioned problems, this application provides a solution.

[0007] It should be noted that, in the absence of conflict, the embodiments and features in any node of the present application can be applied to any other node. In the absence of conflict, the embodiments and features in the embodiments of the present application can be arbitrarily combined with each other. At the same time, the method proposed in the present application can also be used to solve other problems in communication, such as NR evolution and problems in 6G systems.

[0008] As an embodiment, the interpretation of the terminology in the present application refers to the definition of the 3GPP specification protocol TS38 series.

[0009] As an example, the interpretation of the terms in the present application refers to the definitions of the TS37 series of specification protocols of 3GPP.

[0010] The present application discloses a method in a first node used for wireless communication, comprising: receiving a first signaling, wherein the first signaling configures a first radio bearer, a first RLC bearer, and a second RLC bearer, wherein the first radio bearer is a multicast broadcast service radio bearer, the first RLC bearer and the second RLC bearer both serve the first radio bearer, an RLC entity corresponding to the first RLC bearer is configured as a PTM, and an RLC entity corresponding to the second RLC bearer is not configured as a PTM;

[0011] Receiving a second signaling indicating a cell switch; performing the cell switch, which includes: releasing a logical channel identifier associated with only the first RLC bearer and the second RLC bearer.

[0012] As an embodiment, the problems to be solved by the present application include: when performing cell switching, especially when performing LTM cell switching, for the first radio bearer of the broadcast multicast service, the logical channel identifiers associated with which RLC bearers serving the first radio bearer are released is a problem that needs to be solved.

[0013] As an embodiment, the benefits of the above method include: ensuring the reception of multicast broadcast services, ensuring the continuity of data during the switching process, avoiding the impact on the target cell receiving the multicast broadcast services through the PTM mode, and increasing the reliability of the system.

[0014] Specifically, according to one aspect of the present application, the cell switching indicated by the second signaling is an LTM cell switching.

[0015] Specifically, according to one aspect of the present application, the first RLC bearer and the second RLC bearer are both configured by the RLC-BearerConfig information block of the first signaling.

[0016] Specifically, according to one aspect of the present application, the release of the logical channel identifier associated with only the former of the first RLC bearer and the second RLC bearer depends on the first radio bearer or one of the first RLC bearers not being configured to continue.

[0017] Specifically, according to one aspect of the present application, a third signaling is received, where the third signaling includes a first parameter and at least one candidate configuration, where the at least one candidate configuration includes a first candidate configuration, and where the first candidate configuration includes a second parameter;

[0018] The second signaling indicates the first candidate configuration; the releasing of the logical channel identifier associated with only the first RLC bearer and the second RLC bearer depends on the second parameter being equal to the first parameter; and the performing of the cell switching includes: setting the value of the second parameter to the value of the first parameter.

[0019] Specifically, according to one aspect of the present application, the performing of cell switching includes: releasing at least one of the RLC entity, state variable, cache and timer associated with only the former of the first RLC bearer and the second RLC bearer.

[0020] Specifically, according to one aspect of the present application, the RLC entity associated with the first RLC bearer is rebuilt.

[0021] Specifically, according to one aspect of the present application, a first status report is sent, wherein the first status report indicates a PDCP SDU that was not received correctly.

[0022] Specifically, according to one aspect of the present application, the target cell configured by the candidate configuration indicated by the second signaling does not support sending the multicast broadcast service carried by the first radio bearer through PTM.

[0023] Specifically, according to one aspect of the present application, the candidate configuration indicated by the second signaling is to configure a second radio bearer, the second radio bearer is a DRB, and only the latter of the first RLC bearer and the second RLC bearer serves the second radio bearer.

[0024] Specifically, according to one aspect of the present application, the first node is a user equipment.

[0025] Specifically, according to one aspect of the present application, the first node is a vehicle-mounted terminal.

[0026] Specifically, according to one aspect of the present application, the first node is a mobile phone.

[0027] The present application discloses a first node used in wireless communication, comprising:

[0028] A first receiver receives a first signaling, wherein the first signaling configures a first radio bearer, a first RLC bearer, and a second RLC bearer, wherein the first radio bearer is a multicast broadcast service radio bearer, the first RLC bearer and the second RLC bearer both serve the first radio bearer, an RLC entity corresponding to the first RLC bearer is configured as a PTM, and an RLC entity corresponding to the second RLC bearer is not configured as a PTM;

[0029] The first processor receives a second signaling indicating a cell switch; and performs the cell switch, which includes: releasing a logical channel identifier associated with only the first RLC bearer and the second RLC bearer.

[0030] As an embodiment, compared with the traditional solution, this application has the following advantages:

[0031] It can better support data continuity in non-RACH LTM cell switching. The main difference between non-RACH LTM cell switching and RACH-based LTM cell switching is that non-RACH LTM does not use and does not require the RACH process, which is conducive to further shortening the delay of LTM cell switching; RACH-based LTM cell switching requires the RACH process.

[0032] The method proposed in the present application can avoid configuration conflicts when the target cell receives MBS (multicast broadcast service, MBS) through PTM, and can also ensure the continuity of PTP transmission as much as possible, shorten the switching delay, and ensure the reception quality of MBS. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Other features, objects and advantages of the present application will become more apparent by reading the detailed description of non-limiting embodiments with reference to the following drawings:

[0034] Figure 1 A schematic diagram showing receiving a first signaling, receiving a second signaling, and performing a cell handover according to an embodiment of the present application is shown;

[0035] Figure 2 A schematic diagram of a network architecture according to an embodiment of the present application is shown;

[0036] Figure 3 A schematic diagram showing an embodiment of a wireless protocol architecture of a user plane and a control plane according to an embodiment of the present application;

[0037] Figure 4 A schematic diagram showing a first communication device and a second communication device according to an embodiment of the present application is shown;

[0038] Figure 5 A flow chart showing wireless signal transmission according to an embodiment of the present application is shown;

[0039] Figure 6 A schematic diagram of a first radio bearer according to an embodiment of the present application is shown;

[0040] Figure 7 A schematic diagram of a first radio bearer according to an embodiment of the present application is shown;

[0041] Figure 8 A schematic diagram showing that releasing a logical channel identifier associated with only the former of a first RLC bearer and a second RLC bearer depends on the first radio bearer or one of the first RLC bearers not being configured to continue according to an embodiment of the present application;

[0042] Fig. 9 A schematic diagram showing that releasing a logical channel identifier associated with only the first of a first RLC bearer and a second RLC bearer depends on a second parameter being equal to a first parameter according to an embodiment of the present application;

[0043] Fig.10 The following is a schematic diagram illustrating a processing device used in a first node according to an embodiment of the present application. Implementation

[0045] The technical solution of the present application will be further described in detail below in conjunction with the accompanying drawings. It should be noted that, unless there is a conflict, the embodiments in the present application and the features in the embodiments can be combined with each other arbitrarily.

[0046] Example 1

[0047] Embodiment 1 illustrates a flowchart of receiving a first signaling, receiving a second signaling, and performing a cell switching according to an embodiment of the present application, as shown in the attached figure. Figure 1 Attached Figure 1 In the figure, each box represents a step. It should be emphasized that the order of the boxes in the figure does not represent the temporal relationship between the steps represented.

[0048] In Embodiment 1, the first node in the present application receives the first signaling in step 101, receives the second signaling in step 102, and performs cell switching in step 103;

[0049] The first signaling configures a first radio bearer, a first RLC bearer and a second RLC bearer, wherein the first radio bearer is a multicast broadcast service radio bearer, the first RLC bearer and the second RLC bearer both serve the first radio bearer, the RLC entity corresponding to the first RLC bearer is configured as PTM, and the RLC entity corresponding to the second RLC bearer is not configured as PTM; the second signaling indicates a cell switch; wherein the execution of the cell switch includes: releasing a logical channel identifier associated with only the former of the first RLC bearer and the second RLC bearer.

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

[0051] As an embodiment, the first node is a terminal.

[0052] As an embodiment, in this field, cell switching includes L3 (Layer-3, layer 3) cell switching and LTM.

[0053] As an embodiment, LTM cell switch is a cell switch triggered by L1 / L2 signaling.

[0054] Typically, the higher layer at which the MAC sublayer performs operations is the RRC sublayer.

[0055] As an embodiment, when the cell is switched, if the first RLC bearer used to receive PTM does not release the logical channel identifier, then after the complete switch, the MBS service will not be received correctly in the new cell because the new cell uses other logical channel identifiers; however, for the second RLC bearer, since the PTP method is adopted, its logical channel identifier can be retained until the new cell continues to use. If it is not retained, it is easy to cause communication interruption or delay during switching.

[0056] As an embodiment, the lower layer when the RRC sublayer performs operations includes at least one of the physical layer, the MAC sublayer, the RLC sublayer, and the PDCP sublayer.

[0057] As an embodiment, the higher layer when the RRC sublayer performs an operation includes a non-access stratum.

[0058] As an embodiment, the higher layer signaling includes RRC signaling or non-access stratum signaling.

[0059] As an embodiment, in the present application, if it is not specifically stated that it is executed in the MAC sublayer, it is executed in the RRC sublayer.

[0060] As an embodiment, access layer security of the first node is activated.

[0061] As an embodiment, the access stratum (AS) includes multiple protocol layers, and the details can be referred to Embodiment 3.

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

[0063] As an embodiment, any parameter in the present application may be either configured by the network or generated by the first node according to an internal algorithm, such as randomly.

[0064] As an embodiment, the values ​​of the timers in the present application are all limited and do not exceed 2560 milliseconds.

[0065] As an embodiment, the value of the timer is the running time when the timer is not interfered with.

[0066] As an example, the value of any parameter in the present application, including but not limited to the value of a timer and the value of a counter, is limited unless otherwise stated.

[0067] As a sub-embodiment of this embodiment, the upper limit of the value of any parameter in this application is 1024 times of 65536.

[0068] As a sub-embodiment of this embodiment, the upper limit of the value of any parameter in this application is 65536 or 65535.

[0069] As a sub-embodiment of this embodiment, the upper limit of the value of any parameter in this application is 1024.

[0070] As a sub-embodiment of this embodiment, the upper limit of the value of any parameter in this application is 640 or 320.

[0071] As an embodiment, the present application is directed to NR.

[0072] As an embodiment, the present application is directed to a NR evolved wireless communication network.

[0073] As an embodiment, the serving cell refers to the cell where the UE resides. Performing a cell search includes the UE searching for a suitable cell of the selected PLMN (Public Land Mobile Network) or SNPN (Stand-alone Non-Public Network), selecting the suitable cell to provide available services, and monitoring the control channel of the suitable cell. This process is defined as residing on the cell; that is, a residing cell is the serving cell of the UE relative to the UE. Residing on a cell in the RRC idle state or the RRC inactive state has the following benefits: it enables the UE to receive system messages from the PLMN or SNPN; after registration, if the UE wishes to establish an RRC connection or continue a suspended RRC connection, the UE can do so by performing initial access on the control channel of the residing cell; the network can page the UE; and the UE can receive ETWS (Earthquake and Tsunami Warning System) and CMAS (Commercial Mobile Alert System) notifications.

[0074] As an embodiment, for a UE in an RRC connected state that is not configured with CA / DC (carrier aggregation / dual connectivity), there is only one service cell including a primary cell. For a UE in an RRC connected state that is configured with CA / DC (carrier aggregation / dual connectivity), the service cell is used to indicate a set of cells including a special cell (SpCell) and all cells from the small cell. The primary cell (Primary Cell) is an MCG (Master Cell Group) cell that operates on the main frequency. The UE performs an initial connection establishment process or initiates connection reconstruction on the primary cell. For dual connection operations, the special cell refers to the PCell (Primary Cell) of the MCG or the PSCell (Primary SCGCell) of the SCG (Secondary Cell Group); if it is not a dual connection operation, the special cell refers to the PCell.

[0075] As an embodiment, the operating frequency of the SCell (Secondary Cell) is a secondary frequency.

[0076] As an embodiment, the first node is only configured with MCG.

[0077] As an example, individual contents of an information element are referred to as fields.

[0078] As an embodiment, MR-DC (Multi-Radio Dual Connectivity) refers to dual connectivity between E-UTRA and NR nodes, or dual connectivity between two NR nodes.

[0079] As an embodiment, in MR-DC, the wireless access node that provides the control plane connection to the core network is the master node, which may be a master eNB, a master ng-eNB, or a master gNB.

[0080] As an embodiment, MCG refers to a group of service cells associated with a master node in MR-DC, including SpCells, and may also, optionally, include one or more SCells.

[0081] As an embodiment, PCell is the SpCell of MCG.

[0082] As an embodiment, the PSCell is the SpCell of the SCG.

[0083] As an embodiment, in MR-DC, the control plane connection to the core network is not provided, and the radio access node that provides additional resources to the UE is a slave node. The slave node can be an en-gNB, a slave ng-eNB or a slave gNB.

[0084] As an embodiment, in MR-DC, a group of service cells associated with a slave node is a SCG (secondary cell group), including a SpCell and, optionally, one or more SCells.

[0085] As an embodiment, the SpCell is a PCell or the SpCell is a PSCell.

[0086] As an embodiment, in the RRC inactive state, DC is not used.

[0087] As an example, in the RRC inactive state, CA is typically not used.

[0088] As an embodiment, the RRC information block refers to an information block (information element) in an RRC message.

[0089] As an embodiment, SSB may be referred to as SS\PBCH, or SS block.

[0090] As an embodiment, L1 is layer 1 (Layer-1) or physical layer.

[0091] As an example, L2 is Layer-2

[0092] As an embodiment, the present application is directed to NR and NR evolved networks, such as 6G networks.

[0093] As an embodiment, one RRC information block may include one or more RRC information blocks.

[0094] As an embodiment, an RRC information block may not include any RRC information block, but only include at least one parameter.

[0095] As an embodiment, the radio bearer includes at least a signaling radio bearer and a data radio bearer.

[0096] As an embodiment, a radio bearer is a service or an interface of a service provided by the PDCP sublayer to a higher layer.

[0097] As a sub-embodiment of this embodiment, the higher layer includes one of the RRC sublayer, NAS, and SDAP layer.

[0098] As an embodiment, the signaling radio bearer is a service or an interface of services provided by PDCP to a higher layer.

[0099] As a sub-embodiment of this embodiment, the higher layer includes an RRC sublayer, at least the former in NAS.

[0100] As an embodiment, the data radio bearer is a service or an interface of services provided by PDCP to a higher layer.

[0101] As a sub-embodiment of this embodiment, the higher layer includes the SDAP layer, at least the former in NAS.

[0102] As an embodiment, the RLC bearer is a service or service interface provided by the RLC sublayer to the PDCP sublayer.

[0103] As an embodiment, after the first node establishes an RRC connection with the network, the first node enters an RRC connection state.

[0104] As a sub-embodiment of this embodiment, the network is a Radio Access Network (RAN).

[0105] As an embodiment, when the first node does not establish an RRC connection with the network, the first node is in an RRC idle state.

[0106] As a sub-embodiment of this embodiment, the network is a Radio Access Network (RAN).

[0107] As an embodiment, when the RRC connection established between the first node and the network is suspended, the first node enters an RRC inactive state.

[0108] As a sub-embodiment of this embodiment, the network is a Radio Access Network (RAN).

[0109] As an embodiment, different functions are supported in different RRC states.

[0110] As an embodiment, only very limited functions are supported in the non-RRC connected state.

[0111] As an embodiment, the non-RRC connected state is or includes an RRC idle state.

[0112] As an embodiment, the non-RRC connected state is or includes an RRC inactive state.

[0113] As an embodiment, the first node is not in limited service mode.

[0114] As an embodiment, the method proposed in the present application and the scenario based thereon are not aimed at emergency services.

[0115] As an embodiment, the first signaling is RRC signaling.

[0116] As an embodiment, the first signaling is higher layer signaling.

[0117] As an embodiment, the advantage of the first signaling being RRC signaling is that, compared with MAC CE (control element) and DCI (downlink control information), RRC signaling is more reliable.

[0118] As an embodiment, those skilled in the art should understand that the first node may send feedback of the first signaling.

[0119] As an embodiment, the first signaling is RRCReconfiguration.

[0120] As an embodiment, the first signaling is sent via SRB1 (signaling radio bearer 1).

[0121] As an embodiment, the first radio bearer is an MRB (MBS radio bearer).

[0122] As an embodiment, the first radio bearer is used to transmit multicast services.

[0123] As an embodiment, the first radio bearer is a multicast MRB.

[0124] As an embodiment, in this field, MRB and DRB (data radio bearer) are different, DRB is unicast, MRB supports multicast; and DRB is for one user, while MRB can be for all users in a cell; the data of DRB is scrambled by C-RNTI, while the data of MRB can be scrambled by G-RNTI; the DRX (discontinuous reception) associated with MRB is also different from the DRX associated with DRB.

[0125] As an embodiment, unlike DRB, the first radio bearer does not use encryption and integrity protection at the PDCP sublayer.

[0126] As an embodiment, the first RLC bearer corresponds to an RLC entity.

[0127] As an embodiment, the second RLC bearer corresponds to an RLC entity.

[0128] As an embodiment, the first RLC bearer and the second RLC bearer correspond to different RLC entities.

[0129] As an embodiment, the first RLC bearer is not configured to serve radio bearers other than the first radio bearer.

[0130] As an embodiment, the second RLC bearer is not configured to serve any radio bearer other than the first radio bearer.

[0131] As an embodiment, the serving the first radio bearer includes: processing the PDU of the first radio bearer.

[0132] As an embodiment, the serving the first radio bearer includes: processing the PDCP PDU of the first radio bearer.

[0133] As an embodiment, the serving the first radio bearer includes: encapsulating the data of the first radio bearer and submitting it to a lower layer.

[0134] As an embodiment, the serving the first radio bearer includes: receiving an indication of a PDCP entity corresponding to the first radio bearer.

[0135] As an embodiment, the serving the first radio bearer includes: indicating to a PDCP entity corresponding to the first radio bearer whether the data of the first radio bearer has been sent successfully.

[0136] As an embodiment, the serving the first radio bearer includes: encapsulating the data of the first radio bearer and submitting it to a lower layer.

[0137] As an embodiment, the serving the first radio bearer includes: receiving data of the first radio bearer and submitting it to a PDCP entity corresponding to the first radio bearer.

[0138] As an embodiment, the serving the first radio bearer includes: reliably transmitting data of the first radio bearer.

[0139] As an embodiment, the serving first radio bearer includes: a mapping relationship exists between the first radio bearer and the first RLC bearer.

[0140] As an embodiment, the serving first radio bearer includes: a mapping relationship exists between the first radio bearer and the second RLC bearer.

[0141] As an embodiment, the first signaling explicitly indicates that the radio bearer of the first RLC bearer service is the first radio bearer.

[0142] As an embodiment, the first signaling explicitly indicates that the radio bearer served by the second RLC bearer is the first radio bearer.

[0143] As an embodiment, the first signaling configures the first radio bearer, the first RLC bearer and the second RLC bearer, including: configuring the first radio bearer, configuring the first RLC bearer and configuring the second RLC bearer.

[0144] As an embodiment, configuring the first radio bearer includes: configuring parameters of the first radio bearer.

[0145] As an embodiment, the parameter of the first radio bearer includes an identifier.

[0146] As an embodiment, the parameter of the first radio bearer includes an identifier of the MBS session served.

[0147] As an embodiment, the parameter of the first radio bearer includes the type of the first radio bearer.

[0148] As an embodiment, the type of the first radio bearer is MRB.

[0149] As an embodiment, configuring the first radio bearer includes configuring the PDCP corresponding to the first radio bearer.

[0150] As an embodiment, the configuring of the PDCP corresponding to the first radio bearer includes configuring whether to re-establish the PDCP.

[0151] As an embodiment, the configuring of the PDCP corresponding to the first radio bearer includes configuring whether to restore the PDCP.

[0152] As an embodiment, configuring PDCP includes: configuring the size of the sequence number used by PDCP.

[0153] As an embodiment, configuring PDCP includes: configuring header compression used by PDCP.

[0154] As an embodiment, configuring PDCP includes: configuring at least one timer of PDCP.

[0155] As an embodiment, the configuring the first RLC bearer includes: configuring a logical channel identifier of the first RLC.

[0156] As an embodiment, the configuring of the first RLC bearer includes: configuring the logical channel identifier of the first RLC to be the first logical channel identifier.

[0157] As an embodiment, the configuring of the first RLC bearer includes: indicating whether to reestablish RLC.

[0158] As an embodiment, the configuring the first RLC bearer includes: configuring the RLC mode.

[0159] As an embodiment, the configuring the first RLC bearer includes: configuring a logical channel associated with the first RLC bearer.

[0160] As an embodiment, the configuring the first RLC bearer includes: configuring the radio bearer served by the first RLC bearer to be the first radio bearer.

[0161] As an embodiment, the configuring the first RLC bearer includes: configuring the RLC entity corresponding to the first RLC bearer for PTM reception.

[0162] As an embodiment, the configuring of the second RLC bearer includes: configuring the logical channel identifier of the first RLC.

[0163] As an embodiment, the configuring of the second RLC bearer includes: configuring the logical channel identifier of the first RLC to be the second logical channel identifier.

[0164] As an embodiment, the configuring of the second RLC bearer includes: indicating whether to reestablish RLC.

[0165] As an embodiment, the configuring the second RLC bearer includes: configuring the RLC mode.

[0166] As an embodiment, the configuring the second RLC bearer includes: configuring a logical channel associated with the second RLC bearer.

[0167] As an embodiment, the configuring of the second RLC bearer includes: configuring the radio bearer served by the second RLC bearer to be the first radio bearer.

[0168] As an embodiment, the configuring of the second RLC bearer does not include: configuring the RLC entity corresponding to the second RLC bearer for PTM reception.

[0169] As an embodiment, the first radio bearer is a multicast MRB.

[0170] As an embodiment, the isPTM-Entity field in the first signaling used to configure the first RLC bearer indicates that the RLC entity associated with the first RLC bearer is used for PTM reception.

[0171] As an embodiment, the value of isPTM-Entity used to configure the first RLC bearer in the first signaling is enabled.

[0172] As an embodiment, the first signaling does not include the isPTM-Entity field used to configure the second RLC bearer.

[0173] As an embodiment, the domain used to configure the second RLC bearer in the first signaling lacks isPTM-Entity.

[0174] As an embodiment, the value of isPTM-Entity used to configure the first RLC bearer in the first signaling is disabled.

[0175] As an embodiment, the first signaling indicates that the second RLC bearer is used for PTP transmission.

[0176] As an embodiment, the first signaling indicates that the second RLC bearer is used for PTP sending and / or receiving.

[0177] As an embodiment, when an RLC bearer is not configured for PTM reception, the RLC bearer is used for PTP reception and / or transmission.

[0178] As an embodiment, the isPTM-Entity for the second RLC bearer does not appear in the first signaling to indicate that the RLC entity associated with the second RLC bearer is used for sending and / or receiving PTP.

[0179] As an embodiment, one RLC bearer is associated with only one RLC entity.

[0180] As an embodiment, the RLC associated with an RLC bearer is used for either PTM or PTP.

[0181] As an embodiment, the first radio bearer is associated with only one RLC bearer for PTM reception.

[0182] As an embodiment, the RLC entity associated with the first RLC bearer is not the RLC entity associated with the second RLC bearer.

[0183] As an embodiment, the logical channel identifier includes an extended logical channel identifier.

[0184] As an embodiment, the first logical channel identifier is an extended logical channel identifier.

[0185] As an embodiment, the second logical channel identifier is not an extended logical channel identifier.

[0186] As an embodiment, the performing of cell switching includes: performing LTM cell switching.

[0187] As an embodiment, the performing of cell switching includes: applying the candidate configuration indicated by the second signaling.

[0188] As an embodiment, the first node receives at least one candidate configuration before receiving the second signaling.

[0189] As an embodiment, the receiving of at least one candidate configuration is performed at the RRC sublayer.

[0190] As an embodiment, any of the at least one candidate configuration is an RRC configuration.

[0191] As an embodiment, the at least one candidate configuration includes at most 8 candidate configurations.

[0192] As an embodiment, any one of the at least one candidate configuration has a configuration identifier.

[0193] As an embodiment, the at least one candidate configuration belongs to a list included in an RRC message.

[0194] As an embodiment, the at least one candidate configuration belongs to LTM-Config.

[0195] As an embodiment, the at least one candidate configuration belongs to ltm-CandidateToAddModList.

[0196] As an embodiment, any of the at least one candidate configuration is for LTM cell switching.

[0197] As an embodiment, any of the at least one candidate configuration is for LTM.

[0198] As an embodiment, any one of the at least one candidate configuration is for an LTM candidate cell.

[0199] As an embodiment, the at least one candidate configuration needs to be stored in a state variable after being received.

[0200] As an embodiment, any one of the at least one candidate configuration is an LTM-Candidate.

[0201] As an embodiment, the at least one candidate configuration includes at least 2 candidate configurations.

[0202] As an embodiment, the at least one candidate configuration includes a limited number of candidate configurations.

[0203] As an embodiment, the at least one candidate configuration includes multiple candidate configurations.

[0204] As an embodiment, the ltm-CandidateConfig of any of the at least one candidate configuration includes an RRC reconfiguration message.

[0205] As an embodiment, the RRC reconfiguration message is an RRC message embedded in each candidate configuration.

[0206] As an embodiment, the RRC reconfiguration message is used for RRC connection reconfiguration.

[0207] As an embodiment, the benefits of using the RRC reconfiguration message include: the RRC connection can be reconfigured differently; it is conducive to faster reconfiguration, shortening the configuration time, saving power, and having better compatibility; and the implementation complexity is low.

[0208] As an embodiment, the RRC reconfiguration message included in any candidate configuration of the at least one candidate configuration configures the target cell.

[0209] As an embodiment, the RRC reconfiguration message included in any candidate configuration of the at least one candidate configuration configures the SpCell of the first node.

[0210] As an embodiment, the RRC reconfiguration message included in any candidate configuration of the at least one candidate configuration configures a cell group.

[0211] As a sub-embodiment of this embodiment, the cell group is MCG or SCG.

[0212] As an embodiment, the RRC reconfiguration message included in any candidate configuration of the at least one candidate configuration configures MCG and SCG.

[0213] As an embodiment, any of the at least one candidate configuration includes an SSB configuration.

[0214] As an embodiment, any one of the at least one candidate configuration indicates whether the included configuration is complete.

[0215] As an embodiment, the RRC reconfiguration message included in the first candidate configuration is incomplete.

[0216] As an embodiment, the RRC reconfiguration message included in the explicit indication of the first candidate configuration is incomplete.

[0217] As an embodiment, the configuration explicitly indicated by the first candidate configuration is incomplete.

[0218] As an embodiment, the included configuration or the included RRC reconfiguration message is incomplete, which is beneficial to reducing signaling overhead.

[0219] As an embodiment, the first candidate configuration is one candidate configuration among the at least one candidate configuration.

[0220] As an embodiment, the second signaling is a MAC sublayer signaling.

[0221] As an embodiment, the second signaling is an LTM signaling.

[0222] As an embodiment, the second signaling is LTM Cell Switch Command MAC CE.

[0223] As an embodiment, the advantage of the second signaling being MAC CE is that it is faster than RRC signaling and is conducive to shortening the delay of LTM cell switching.

[0224] As an embodiment, the advantage of the second signaling being MAC CE is that it has stronger scalability than physical layer signaling.

[0225] As an embodiment, the sender of the second signaling is the same as the sender of the at least one candidate configuration.

[0226] As an embodiment, the sender of the second signaling is different from the sender of the at least one candidate configuration.

[0227] As a sub-embodiment of this embodiment, this method does not need to reconfigure the candidate configuration, thereby reducing signaling overhead.

[0228] As an embodiment, the second signaling is received at the MAC sublayer.

[0229] As an embodiment, the sender of the second signaling is the source cell of the first node.

[0230] As an embodiment, the sender of the second signaling is the SpCell of the first node.

[0231] As an embodiment, the second signaling explicitly indicates the first candidate configuration among the at least one candidate configuration.

[0232] As an embodiment, the second signaling triggers the MAC sublayer of the first node to determine that a non-RACH LTM cell switching is in progress.

[0233] As an embodiment, the first node, in response to receiving the second signaling, applies the first candidate configuration in the RRC sublayer.

[0234] As an embodiment, the second signaling triggers the RRC sublayer of the first node to apply the first candidate configuration.

[0235] As an embodiment, the second signaling includes an identifier of the first candidate configuration.

[0236] As an embodiment, the second signaling only includes an identifier of the first candidate configuration among the at least one candidate configuration.

[0237] As an embodiment, the non-RACH LTM cell switch is a RACH-less LTM cell switch.

[0238] As an embodiment, the non-RACH LTM cell switching being in progress means that the non-RACH LTM cell switching has started but has not yet ended.

[0239] As an embodiment, the non-RACH LTM cell switching in progress means that the non-RACH LTM cell switching is in process.

[0240] As an embodiment, the non-RACH LTM cell handover being performed means that the non-RACH LTM cell handover has not failed.

[0241] As an embodiment, the non-RACH LTM cell switching in progress means that the non-RACH LTM cell switching is not completed.

[0242] As an embodiment, applying the first candidate configuration includes applying each information block in the first candidate configuration.

[0243] As an embodiment, applying the first candidate configuration includes applying the RRCReconfiguration message in the first candidate configuration.

[0244] As an embodiment, applying the first candidate configuration includes applying all configurations in the first candidate configuration.

[0245] As an embodiment, applying the first candidate configuration includes applying all instructions in the first candidate configuration.

[0246] As an embodiment, applying the first candidate configuration includes applying all signaling or information blocks in the RRC reconfiguration message in the first candidate configuration.

[0247] As an embodiment, the first candidate configuration includes a synchronous reconfiguration of a special cell (SpCell) for the first node.

[0248] As an embodiment, the synchronous reconfiguration is Reconfigurationwithsync.

[0249] As an embodiment, the synchronous reconfiguration is used to configure the SpCell.

[0250] As an embodiment, the synchronous reconfiguration is used to configure the target cell of the first node.

[0251] As an embodiment, the RRC reconfiguration message included in each candidate configuration of the at least one candidate configuration includes a synchronization reconfiguration information block.

[0252] As an embodiment, any candidate configuration of the at least one candidate configuration indicates a candidate cell identifier.

[0253] As a sub-embodiment of this embodiment, the cell identifier is a physical cell identifier.

[0254] As an embodiment, any candidate configuration of the at least one candidate configuration includes an early uplink synchronization configuration.

[0255] As an embodiment, any candidate configuration of the at least one candidate configuration indicates whether to reset the entity of layer 2.

[0256] As a sub-embodiment of this embodiment, the layer 2 entity includes at least one of an RLC entity and a PDCP entity.

[0257] As an embodiment, any candidate configuration of the at least one candidate configuration includes a transmission configuration indication.

[0258] As an embodiment, any candidate configuration of the at least one candidate configuration includes an SSB configuration.

[0259] As an embodiment, the RRC reconfiguration includes configuration for a cell group.

[0260] As an embodiment, the RRC reconfiguration includes configuration for a radio bearer.

[0261] As an embodiment, the RRC reconfiguration includes configuration for a beam.

[0262] As an embodiment, the RRC reconfiguration includes configuration for multicast broadcast services.

[0263] As an embodiment, the RRC reconfiguration includes configuration for PUCCH (Physical uplink control channel).

[0264] As an embodiment, the RRC reconfiguration includes configuration for measurement.

[0265] As a sub-embodiment of this embodiment, the configuration for measurement includes configuration of measurement objects and measurement reports.

[0266] As an embodiment, the synchronization reconfiguration includes the C-RNTI of the first node.

[0267] As an embodiment, the synchronous reconfiguration includes the C-RNTI of the first node in the serving cell configured by the corresponding candidate configuration.

[0268] As an embodiment, the synchronous reconfiguration includes configuration of the T304 timer.

[0269] As an embodiment, the synchronous reconfiguration includes SMTC (SSB Measurement timing configuration).

[0270] As an embodiment, the first candidate configuration includes the benefits of synchronous reconfiguration for the special cell of the first node, including: using synchronous reconfiguration is necessary to implement cell switching, and provides the most core configuration in the target cell.

[0271] As an embodiment, the cell configured by the first candidate configuration is a special cell of the first node.

[0272] As an embodiment, the cell configured by the first candidate configuration is the PCell of the first node.

[0273] As an embodiment, the cell configured by the first candidate configuration is the PSCell of the first node.

[0274] As an embodiment, the cell configured by the first candidate configuration is one of the PCell or SPCell of the first node.

[0275] As an embodiment, a MAC entity has at most one ongoing LTM cell switch at the same time.

[0276] As an embodiment, a MAC entity has at most one ongoing non-RACH LTM cell switch at the same time.

[0277] As an embodiment, one MCG has only one MAC entity.

[0278] As an embodiment, one SCG has only one MAC entity.

[0279] As an embodiment, in the MAC sublayer in the present application refers to in a MAC entity.

[0280] As an embodiment, the first node has only one RRC entity.

[0281] As an embodiment, the second signaling indicating cell switching means that upon receiving the second signaling, the first node performs cell switching.

[0282] As an embodiment, the second signaling indicating cell switching means that the second signaling is a switching command.

[0283] As an embodiment, the second signaling indicating cell switching means that the second signaling is a switching command of a MAC sublayer.

[0284] As an embodiment, the meaning of the second signaling indicating cell switching is that the second signaling is an LTM command of the MAC sublayer.

[0285] As an embodiment, the meaning of the second signaling indicating cell switching is: the second signaling indicates the target cell.

[0286] As an embodiment, the second signaling indicating cell switching means that the second signaling indicates the configuration of the target cell.

[0287] As an embodiment, the configuration of the target cell is the first candidate configuration.

[0288] As an embodiment, the meaning of the second signaling indicating cell switching is: the second signaling indicates resources for initiating random access in the target cell.

[0289] As an embodiment, the meaning of the second signaling indicating cell switching is: the second signaling indicates the TCI (transmission configuration indication) of the target cell.

[0290] As an embodiment, the performing of cell switching includes applying the first candidate configuration.

[0291] As an embodiment, concomitant with the releasing of the logical channel identifier associated with only the first RLC bearer and the second RLC bearer, the first node applies the first candidate configuration.

[0292] As an embodiment, after releasing the logical channel identifier associated with only the former of the first RLC bearer and the second RLC bearer, the first node applies the first candidate configuration.

[0293] As an embodiment, the first RLC bearer and the second RLC bearer are both configured by the RLC-BearerConfig information block of the first signaling.

[0294] As an embodiment, the first RLC bearer and the second RLC bearer are respectively configured by two RLC-BearerConfig information blocks in the cell group configuration of the first signaling.

[0295] As an embodiment, the first RLC bearer and the second RLC bearer are respectively configured by two RLC-BearerConfig information blocks included in an RLC bearer configuration list in the cell group configuration of the first signaling.

[0296] As an embodiment, the releasing of the logical channel identifier associated with only the former of the first RLC bearer and the second RLC bearer depends on the first radio bearer or one of the first RLC bearers not being configured to continue.

[0297] As an embodiment, the release of the logical channel identifier associated with only the former of the first RLC bearer and the second RLC bearer depends on the first radio bearer or one of the first RLC bearers not being configured to continue, meaning that the logical channel identifier associated with only the former of the first RLC bearer and the second RLC bearer is released only when the first radio bearer is not configured to continue.

[0298] As an embodiment, the release of the logical channel identifier associated with only the former of the first RLC bearer and the second RLC bearer depends on the first radio bearer or one of the first RLC bearers not being configured to continue, meaning that the logical channel identifier associated with only the former of the first RLC bearer and the second RLC bearer is released only when the first RLC bearer is not configured to continue.

[0299] As an embodiment, the first signaling configures the first radio bearer or the first RLC bearer to continue by indicating continuePTM.

[0300] As an embodiment, if the first signaling does not indicate continuePTM, the first radio bearer or the first RLC bearer is not continued.

[0301] As an embodiment, not being configured to continue refers to not being configured to continue PTM.

[0302] As an embodiment, the performing of cell switching includes: releasing at least one of the RLC entity, state variable, cache and timer associated with only the former of the first RLC bearer and the second RLC bearer.

[0303] As an embodiment, the RLC entity associated with the first RLC bearer is the RLC entity corresponding to the first RLC bearer.

[0304] As an embodiment, the state variables associated with the first RLC bearer include: state variables of the RLC entity corresponding to the first RLC bearer.

[0305] As an embodiment, the state variable associated with the first RLC bearer includes: a state variable used to record the sequence number of the next RLC SDU waiting for confirmation during in-sequence transmission.

[0306] As an embodiment, the state variable associated with the first RLC bearer includes: a state variable for recording a sequence number to be allocated to the next generated PDU in RLC confirmation mode.

[0307] As an embodiment, the state variable associated with the first RLC bearer includes: a sequence number for recording the last completely received RLC SDU during in-sequence transmission.

[0308] As an embodiment, the state variable associated with the first RLC bearer includes: a counter for recording the number of RLC SDU retransmissions that are retransmitted in sequence.

[0309] As an embodiment, the cache associated with the first RLC bearer includes: at least one of a receiving cache and a sending cache.

[0310] As an embodiment, the timer associated with the first RLC bearer includes: a timer for controlling a retransmission poll.

[0311] As an embodiment, the timer associated with the first RLC bearer includes: a timer for detecting RLC PDU loss.

[0312] As an embodiment, the timer associated with the first RLC bearer includes: a timer for prohibiting transmission of an RLC status report.

[0313] As an embodiment, the performing of cell switching includes: releasing at least two of the RLC entities, state variables, caches and timers associated with only the former of the first RLC bearer and the second RLC bearer.

[0314] As an embodiment, the performing of cell switching includes: releasing part of the state variables associated with only the former of the first RLC bearer and the second RLC bearer.

[0315] As an embodiment, the above method has the advantage of resuming PTM transmission as soon as possible after switching.

[0316] As an embodiment, the performing of the cell switching includes: resetting a timer for controlling a control retransmission poll associated with only the former of the first RLC bearer and the second RLC bearer.

[0317] As an embodiment, the performing of the cell switching includes: resetting a timer for detecting RLC PDU loss associated with only the former of the first RLC bearer and the second RLC bearer.

[0318] As an embodiment, the performing of the cell switching includes: resetting a timer associated with only the former of the first RLC bearer and the second RLC bearer for prohibiting the transmission of the RLC status report.

[0319] As an embodiment, the performing of cell switching does not include: releasing the RLC entity associated with the first RLC bearer.

[0320] As an embodiment, the performing of cell switching does not include: releasing at least one state variable of an RLC entity associated with the first RLC bearer.

[0321] As an embodiment, the above method has the advantage of reducing the impact of the switching of the MBS receiving the PTM as much as possible.

[0322] As an embodiment, the target cell configured by the candidate configuration indicated by the second signaling does not support sending the multicast broadcast service carried by the first radio bearer through PTM.

[0323] As an embodiment, when the target cell does not support sending the multicast broadcast service carried by the first wireless bearer through PTM, the method proposed in the present application is conducive to releasing resources, ensuring the continuity of PTP transmission, and reducing or avoiding interruptions.

[0324] As an embodiment, the target cell configured by the candidate configuration indicated by the second signaling supports sending the multicast broadcast service carried by the first radio bearer through PTM.

[0325] As an embodiment, when the target cell supports sending the multicast broadcast service carried by the first wireless bearer through PTM, the method proposed in the present application is conducive to improving compatibility, simplifying LTM operation, avoiding the impact of the current configuration on the target cell, and minimizing the impact of switching data transmission.

[0326] Example 2

[0327] Embodiment 2 illustrates a schematic diagram of a network architecture according to the present application, as shown in the attached Figure 2 shown.

[0328] Attached Figure 2A diagram of a network architecture 200 for 5G NR, LTE (Long-Term Evolution) and LTE-A (Long-Term Evolution Advanced) systems is illustrated. The 5G NR or LTE network architecture 200 may be referred to as 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-RAN (Next Generation Radio Access Network) 202, 5GC (5G Core Network) / EPC (Evolved Packet Core) 210, HSS (Home Subscriber Server) / UDM (Unified Data Management) 220, and Internet services 230. The 5GS / EPS may be interconnected with other access networks, but these entities / interfaces are not shown for simplicity. As shown, 5GS / EPS provides packet-switched services, however, those skilled in the art will readily appreciate that the various concepts presented throughout this application can be extended to networks providing circuit-switched services or other cellular networks. NG-RAN includes NR Node B (gNB) 203 and other gNBs 204. gNB 203 provides user and control plane protocol terminations toward UE 201. gNB 203 can be connected to other gNBs 204 via an Xn interface (e.g., backhaul). gNB 203 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 term. gNB 203 provides an access point to 5GC / EPC 210 for UE 201. Examples of UE 201 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, non-terrestrial base station communications, satellite mobile communications, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, drones, aircraft, narrowband Internet of Things devices, machine type communication devices, land vehicles, cars, wearable devices, or any other similar functional devices. Those skilled in the art may also refer to UE 201 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless 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 term.gNB203 is connected to 5GC / EPC210 via the S1 / NG interface. 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) / UPF213. MME / AMF / SMF211 is the control node that handles signaling between UE201 and 5GC / EPC210. ​​In general, MME / AMF / SMF211 provides bearer and connection management. All user IP (Internet Protocol) packets are transmitted through S-GW / UPF212, which itself is connected to P-GW / UPF213. P-GW provides UE IP address allocation and other functions. P-GW / UPF213 is connected to Internet service 230. Internet service 230 includes operator-corresponding Internet protocol services, which may specifically include Internet, Intranet, IMS (IP Multimedia Subsystem) and packet-switched streaming services.

[0329] As an embodiment, the first node in the present application is UE201.

[0330] As an embodiment, the base station of the second node in the present application is gNB203.

[0331] As an embodiment, the wireless link from the UE201 to the NR Node B is an uplink.

[0332] As an embodiment, the wireless link from the NR Node B to UE201 is a downlink.

[0333] As an embodiment, the UE 201 includes a mobile phone.

[0334] As an embodiment, the UE201 is a dedicated device or special device with communication function.

[0335] As an embodiment, the gNB203 is a micro cell base station.

[0336] As an embodiment, the gNB203 is a pico cell base station.

[0337] As an embodiment, the gNB203 is a base station used in a home network.

[0338] As an embodiment, the gNB203 is a base station used in a private network.

[0339] As an embodiment, the gNB203 is a base station used in an enterprise network.

[0340] Example 3

[0341] Embodiment 3 shows a schematic diagram of an embodiment of a wireless protocol architecture of a user plane and a control plane according to the present application, as shown in the attached Figure 3 shown. Figure 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300, Figure 3The radio protocol architecture of the control plane 300 for a first node (UE, gNB) and a second node (gNB, UE), or between two UEs is shown 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 as PHY301 herein. Layer 2 (L2 layer) 305 is above PHY301 and is responsible for the link between the first node and the second node and the two UEs through 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 multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by encrypting data packets, and provides support for inter-zone mobility of the first node between the second node. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data 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 various radio resources (e.g., resource blocks) in a 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 layer using RRC signaling between the second node and the first node. The PC5-S (PC5 Signaling Protocol) sublayer 307 is responsible for processing the signaling protocol of the PC5 interface. The radio protocol architecture of the user plane 350 includes Layer 1 (L1 layer) and Layer 2 (L2 layer). The radio protocol architecture for the first node and the second node in the user plane 350 is substantially the same as the corresponding layers and sublayers in the control plane 300 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, but the PDCP sublayer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead.The L2 layer 355 in the user plane 350 also includes an SDAP (Service Data Adaptation Protocol) sublayer 356, which is responsible for mapping between QoS flows and data radio bearers (DRBs) to support the diversity of services. SRB can be regarded as a service or interface provided by the PDCP sublayer to a higher layer, such as the RRC sublayer. In the NR system, SRBs include SRB1, SRB2, and SRB3, which are used to transmit different types of control signaling. SRB is a bearer between the UE and the access network, and is used to transmit control signaling including RRC signaling between the UE and the access network. SRB1 has special significance for the UE. After each UE establishes an RRC connection, there will be SRB1 for transmitting RRC signaling. Most of the signaling is transmitted through SRB1. If SRB1 is interrupted or cannot be used, the UE must perform RRC reconstruction. SRB2 is generally only used to transmit NAS signaling or security-related signaling. The UE may not configure SRB3. Except for emergency services, the UE must establish an RRC connection with the network for subsequent communications. Although not shown, the first node may have several upper layers above the L2 layer 355. In addition, it also includes a network layer (e.g., IP layer) terminated at the P-GW on the network side and an application layer terminated at the other end of the connection (e.g., remote UE, server, etc.). The protocol layer may also be referred to as a protocol sublayer. Attached. Figure 3 What is shown is a general protocol layer structure, and the nodes used in this application may lack some protocol layers.

[0342] As an example, Figure 3 The wireless protocol architecture in is applicable to the first node in this application.

[0343] As an example, Figure 3 The wireless protocol architecture in is applicable to the second node in this application.

[0344] As an embodiment, the at least one candidate configuration in the present application is generated in RRC306.

[0345] As an embodiment, the second signaling in the present application is generated by MAC302.

[0346] As an embodiment, the first signaling in the present application is generated in RRC306.

[0347] As an embodiment, the third signaling in the present application is generated in RRC306.

[0348] As an embodiment, the at least one candidate configuration in the present application is generated in RRC306.

[0349] As an embodiment, the first candidate configuration in the present application is generated in RRC306.

[0350] As an embodiment, the DCI in the present application is generated in PHY301.

[0351] As an embodiment, the first status report in the present application is generated by PDCP354.

[0352] Example 4

[0353] Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to an embodiment of the present application, as shown in the attached figure. Figure 4 shown. Figure 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.

[0354] The first communication device 450 includes a controller / processor 459, a memory 460, a data source 467, a transmit processor 468, a receive processor 456, and may optionally also include a multi-antenna transmit processor 457, a multi-antenna receive processor 458, a transmitter / receiver 454 and an antenna 452.

[0355] The second communication device 410 includes a controller / processor 475 , a memory 476 , a receiving processor 470 , a transmitting processor 416 , and may optionally also include a multi-antenna receiving processor 472 , a multi-antenna transmitting processor 471 , a transmitter / receiver 418 and an antenna 420 .

[0356] In the transmission from the second communication device 410 to the first communication device 450, at the second communication device 410, the 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-2) layer. In the transmission from the second communication device 410 to the first communication 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 communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for the 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 constellations 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. The transmit processor 416 then maps each spatial stream to a subcarrier, multiplexes it with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then uses an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain multi-carrier symbol stream. The multi-antenna transmit processor 471 then performs a transmit analog precoding / beamforming operation on the time-domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multi-carrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream, and then provides it to a different antenna 420.

[0357] In the transmission from the second communication device 410 to the first communication device 450, at the first communication device 450, each receiver 454 receives a signal through its corresponding antenna 452. Each receiver 454 recovers the information modulated onto the RF carrier and converts the RF stream into a baseband multi-carrier symbol stream and provides it to the receiving processor 456. The receiving processor 456 and the multi-antenna receiving processor 458 implement various signal processing functions of the L1 layer. The multi-antenna receiving processor 458 performs a receiving analog precoding / beamforming operation on the baseband multi-carrier symbol stream from the receiver 454. The receiving processor 456 uses a fast Fourier transform (FFT) to convert the baseband multi-carrier symbol stream after the receiving analog precoding / beamforming operation from the time domain to the frequency domain. In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receiving processor 456, wherein the reference signal will be used for channel estimation, and the data signal is recovered after multi-antenna detection in the multi-antenna receiving processor 458 to any spatial stream destined for the first communication device 450. The symbols on each spatial stream are demodulated and recovered in the receiving processor 456, and soft decisions are generated. The receiving processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communication device 410 on the physical channel. The upper layer data and control signals are then provided to the 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. The memory 460 may be referred to as a computer-readable medium. In the transmission from the second communication device 410 to the second communication device 450, the controller / processor 459 provides multiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover the upper layer data packets from the core network. The upper layer data packets are then provided to all protocol layers above the L2 layer. Various control signals may also be provided to L3 for L3 processing.

[0358] In the transmission from the first communication device 450 to the second communication device 410, at the first communication device 450, a data source 467 is used to provide upper layer data packets to the controller / processor 459. The data source 467 represents all protocol layers above the L2 layer. Similar to the transmission function at the second communication device 410 described in the transmission from the second communication device 410 to the first communication device 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, and implements L2 layer functions for user plane and control plane. The controller / processor 459 is also responsible for the retransmission of lost packets and signaling to the second communication device 410. The transmit processor 468 performs modulation mapping and channel coding processing, and the multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing. Then, the transmit processor 468 modulates the generated spatial stream into a multi-carrier / single-carrier symbol stream, which is then provided to different antennas 452 via the transmitter 454 after analog precoding / beamforming operations 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 then provides it to the antenna 452.

[0359] In the transmission from the first communication device 450 to the second communication device 410, the function at the second communication device 410 is similar to the reception function 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 a radio frequency signal through its corresponding antenna 420, converts the received radio frequency signal into a baseband signal, and provides the baseband signal to the multi-antenna reception processor 472 and the reception processor 470. The reception processor 470 and the multi-antenna reception processor 472 jointly implement the functions of the L1 layer. The controller / processor 475 implements the L2 layer functions. The controller / processor 475 can be associated with a memory 476 storing program codes and data. The memory 476 can be referred to as a computer-readable medium. In the transmission from the first communication device 450 to the second communication device 410, the controller / processor 475 provides multiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover the upper layer data packets from the UE 450. Upper layer packets from controller / processor 475 may be provided to the core network.

[0360] As an embodiment, the first communication device 450 apparatus includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor, and the first communication device 450 apparatus at least: receives a first signaling, the first signaling configures a first wireless bearer, a first RLC bearer and a second RLC bearer, wherein the first wireless bearer is a multicast broadcast service wireless bearer, the first RLC bearer and the second RLC bearer both serve the first wireless bearer, the RLC entity corresponding to the first RLC bearer is configured as PTM, and the RLC entity corresponding to the second RLC bearer is not configured as PTM; receives a second signaling, the second signaling indicates a cell switching; performs a cell switching, which includes: releasing a logical channel identifier associated with only the former of the first RLC bearer and the second RLC bearer.

[0361] As an embodiment, the first communication device 450 includes: a memory storing a computer-readable instruction program, wherein the computer-readable instruction program generates an action when executed by at least one processor, and the action includes: receiving a first signaling, wherein the first signaling configures a first wireless bearer, a first RLC bearer, and a second RLC bearer, wherein the first wireless bearer is a multicast broadcast service wireless bearer, the first RLC bearer and the second RLC bearer both serve the first wireless bearer, the RLC entity corresponding to the first RLC bearer is configured as PTM, and the RLC entity corresponding to the second RLC bearer is not configured as PTM; receiving a second signaling, wherein the second signaling indicates a cell switching; performing a cell switching, which includes: releasing a logical channel identifier associated with only the former of the first RLC bearer and the second RLC bearer.

[0362] As an embodiment, the first communication device 450 corresponds to the first node in this application.

[0363] As an embodiment, the second communication device 410 corresponds to the second node in this application.

[0364] As an embodiment, the first communication device 450 is a UE.

[0365] As an embodiment, the first communication device 450 is a mobile phone.

[0366] As an embodiment, the second communication device 450 is a relay.

[0367] As an embodiment, the second communication device 410 is a base station.

[0368] As an embodiment, the receiver 454 (including the antenna 452), the receiving processor 456 and the controller / processor 459 are used to receive the at least one candidate configuration in the present application.

[0369] As an embodiment, the receiver 454 (including the antenna 452), the receiving processor 456 and the controller / processor 459 are used to receive the first candidate configuration in the present application.

[0370] As an embodiment, the receiver 454 (including the antenna 452), the receiving processor 456 and the controller / processor 459 are used to receive the first signaling in the present application.

[0371] As an embodiment, the receiver 454 (including the antenna 452), the receiving processor 456 and the controller / processor 459 are used to receive the second signaling in the present application.

[0372] As an embodiment, the receiver 454 (including the antenna 452), the receiving processor 456 and the controller / processor 459 are used to receive the third signaling in the present application.

[0373] As an embodiment, the receiver 454 (including the antenna 452), the receiving processor 456 and the controller / processor 459 are used to receive the DCI in the present application.

[0374] As an embodiment, the transmitter 454 (including the antenna 452), the transmit processor 468 and the controller / processor 459 are used to send the first status report in the present application.

[0375] Example 5

[0376] Embodiment 5 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in the attached Figure 5 Attached Figure 5 In the example, U01 corresponds to the first node of the present application. It is particularly noted that the order in this example does not limit the signal transmission order and implementation order in the present application, wherein the steps in F51 and F52 are optional.

[0377] for First node U01 , receiving the third signaling in step S5101; receiving the first signaling in step S5102; receiving the second signaling in step S5103; performing cell switching in step S5104; and sending the first status report in step S5105.

[0378] for The second node U02 , sending the third signaling in step S5201; sending the first signaling in step S5202; sending the second signaling in step S5203.

[0379] In Example 5, the first signaling configures a first radio bearer, a first RLC bearer and a second RLC bearer, wherein the first radio bearer is a multicast broadcast service radio bearer, the first RLC bearer and the second RLC bearer both serve the first radio bearer, the RLC entity corresponding to the first RLC bearer is configured as PTM, and the RLC entity corresponding to the second RLC bearer is not configured as PTM; the second signaling indicates a cell switching; wherein step S5104 includes: releasing the logical channel identifier associated with only the former of the first RLC bearer and the second RLC bearer.

[0380] As an embodiment, the second node U02 is a base station corresponding to the PCell of the first node U01.

[0381] As an embodiment, the second node U02 is the service cell of the first node or the base station corresponding to the service cell.

[0382] As an embodiment, the second node U02 belongs to a cellular network.

[0383] As an embodiment, the second node U02 corresponds to the source cell.

[0384] As an example, Figure 5 The order in which the steps are numbered is the chronological order.

[0385] As an embodiment, step S5102 is performed earlier than step S5101.

[0386] As an embodiment, step S5102 is performed earlier than step S5103.

[0387] As an embodiment, step S5105 is performed later than step S5104.

[0388] As an embodiment, step S5104 is performed later than step S5103.

[0389] As an embodiment, the method proposed in the present application is also applicable to the situation where the senders of the third signaling and the second signaling are different.

[0390] As an embodiment, the second node U02 sends at least one candidate configuration through the third signaling.

[0391] As an embodiment, the at least one RRC message includes an RRC reconfiguration message.

[0392] As an embodiment, the at least one RRC message includes an RRCReconfiguration message.

[0393] As an embodiment, before step S5101, the first node U01 indicates to the second node U02 that LTM cell switching is supported.

[0394] As an embodiment, before step S5101, the first node U01 indicates to the second node U02 that non-RACH LTM cell switching is supported.

[0395] As an embodiment, before step S5101, the first node U01 indicates to the second node U02 that UE-based timing advance is supported.

[0396] As an embodiment, the second signaling is control signaling of the MAC sublayer.

[0397] As an embodiment, the second signaling is MAC CE.

[0398] As an embodiment, the second signaling is LTM cell switch command MAC CE.

[0399] As an embodiment, the second signaling is received after receiving the third signaling.

[0400] As an embodiment, the logical channel corresponding to the second signaling is fixed.

[0401] As an embodiment, in response to receiving the second signaling, the first node U01 applies the first candidate configuration in the RRC sublayer.

[0402] As an embodiment, the first candidate configuration is one of the at least one candidate configuration.

[0403] As an embodiment, the at least one candidate configuration includes multiple candidate configurations.

[0404] As an embodiment, the at least one candidate configuration includes at most 8 candidate configurations.

[0405] As an embodiment, applying the first candidate configuration in the RRC sublayer includes starting the first timer.

[0406] As an embodiment, applying the first candidate configuration at the RRC sublayer includes instructing the MAC sublayer to reset the MAC sublayer.

[0407] As an embodiment, the cell handover is an LTM cell handover.

[0408] As an embodiment, after receiving the second signaling, the MAC sublayer of the first node indicates to the RRC sublayer that the LTM cell switching is triggered.

[0409] As an embodiment, after receiving the indication that the LTM cell switching is triggered, the RRC sublayer determines whether to use UE-based timing advance according to implementation.

[0410] As an embodiment, after receiving the indication that the LTM cell switching is triggered, the RRC sublayer determines whether to use the UE-based timing advance according to whether the target cell and the source cell belong to the same cell group.

[0411] As an embodiment, when the LTM target cell and the source cell belong to the same cell group, the RRC sublayer instructs the MAC sublayer to use UE-based timing advance; when the LTM target cell and the source cell do not belong to the same cell group, the RRC sublayer does not instruct the MAC sublayer to use UE-based timing advance.

[0412] As an embodiment, when the LTM target cell and the source cell belong to the same control unit (CU), the RRC sublayer instructs the MAC sublayer to use UE-based timing advance; when the LTM target cell and the source cell do not belong to the same CU, the RRC sublayer does not instruct the MAC sublayer to use UE-based timing advance.

[0413] As an embodiment, when the LTM target cell and the source cell belong to the same data unit (DU), the RRC sublayer instructs the MAC sublayer to use UE-based timing advance; when the LTM target cell and the source cell do not belong to the same DU, the RRC sublayer does not instruct the MAC sublayer to use UE-based timing advance.

[0414] As an embodiment, whether step S5104 adopts non-RACH-based LTM cell switching depends on whether the MAC sublayer is instructed by the RRC sublayer to use UE-based timing advance.

[0415] As an embodiment, the MAC entity of the present application is a MAC entity that receives the second signaling.

[0416] As an embodiment, the meaning of MAC sublayer reset in the present application is equal to MAC entity reset or MAC reset.

[0417] As an embodiment, the first node U01 monitors the PDCCH during the active time of the MAC sublayer.

[0418] As an embodiment, the first node U01 is required to monitor the PDCCH during the active time of the MAC sublayer.

[0419] As an embodiment, the first node U01 is required to monitor the PDCCH only during the active time of the MAC sublayer.

[0420] As an embodiment, the active time of the MAC sublayer includes the time when non-RACH LTM cell switching is in progress.

[0421] As an embodiment, the active time of the MAC sublayer is the active time of the MAC or the active time of the MAC entity.

[0422] As an embodiment, when non-RACH LTM cell switching is not in progress, the MAC sublayer of the first node U01 is not in active time.

[0423] As an embodiment, when non-RACH LTM cell switching is not in progress, the MAC sublayer of the first node U01 is not in active time when no other events that can be determined as active time are in progress.

[0424] As an embodiment, the above method has the following benefits: timely determining that non-RACH LTM cell switching is not in progress, which is beneficial to stop monitoring PDCCH, thereby facilitating power saving.

[0425] As an embodiment, when executing step S5104, monitoring of the PDCCH continues until there is no need to monitor the PDCCH position.

[0426] As an embodiment, monitoring the PDCCH refers to monitoring the PDCCH of the target cell.

[0427] As an embodiment, in step S5105, the first node U01 sends the first status report to the target cell.

[0428] As an embodiment, after successfully completing the cell switching, the first node sends the first status report.

[0429] As an embodiment, after the cell switching fails, the first node sends the first status report.

[0430] As an embodiment, sending the first status report is beneficial to the continuity of data transmission and reduces the interruption time.

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

[0432] As an embodiment, the first status report indicates a sequence number of a PDCP SDU that was not received correctly.

[0433] As an embodiment, the first status report indicates the incorrectly received PDCP SDU by indicating the sequence number of the last consecutive correctly received PDCP SDU.

[0434] As an embodiment, the cell switching includes: reestablishing the RLC entity associated with the first RLC bearer.

[0435] As an embodiment, the reestablishing the RLC entity associated with the first RLC bearer is performed after the performing of the cell switching.

[0436] As an embodiment, the reestablishing the RLC entity associated with the first RLC bearer is performed after performing LTM cell switching.

[0437] As an embodiment, the reestablishing the RLC entity associated with the first RLC bearer is performed after applying the first candidate configuration.

[0438] As an embodiment, the cell switching does not include: reestablishing the RLC entity associated with the second RLC bearer.

[0439] Example 6

[0440] Embodiment 6 illustrates a schematic diagram of a first radio bearer according to an embodiment of the present application, as shown in the attached figure. Figure 6 shown.

[0441] Attached Figure 6 The protocol structure required for receiving an MBS session is shown in FIG. Figure 6 It is attached Figure 3 Supplement, attached Figure 6 The dashed boxes indicate optional features, and the solid lines indicate features that need to be supported.

[0442] As an embodiment, the first node may simultaneously receive one or more MBS sessions, where the MBS sessions correspond to one or more QoS flows.

[0443] As an embodiment, the QoS flow is a service provided by the SDAP layer to a higher layer of the SDAP layer.

[0444] As an embodiment, the QoS flow is mapped to the PDCP sublayer through a radio bearer. The radio bearer is a service provided by the PDCP sublayer to the SDAP layer. Figure 6 In the embodiment, there are three MRBs, namely MRB0, MRB1 and MRB2. The method proposed in the present application does not limit the number of MRBs used simultaneously.

[0445] As an embodiment, each radio bearer corresponds to a PDCP entity.

[0446] As an embodiment, any PDCP entity corresponds to a radio bearer.

[0447] As an embodiment, the first radio bearer corresponds to an attached Figure 6 MRB2 in.

[0448] As an embodiment, the service provided by the RLC sublayer to the PDCP sublayer is the RLC bearer.

[0449] As an embodiment, the first RLC bearer is associated with an attached Figure 6 The first logical channel.

[0450] As an embodiment, the second RLC bearer is associated with an attached Figure 6 The second logical channel.

[0451] As an embodiment, the first RLC bearer corresponds to an RLC entity.

[0452] As an embodiment, the second RLC bearer corresponds to an RLC entity.

[0453] As an embodiment, the first RLC bearer and the second RLC bearer correspond to one RLC entity respectively.

[0454] As an embodiment, any RLC entity uniquely corresponds to one RLC bearer.

[0455] As an embodiment, any RLC bearer is uniquely associated with one logical channel, for example, the first RLC bearer is associated with the first logical channel but not with the second logical channel, and the second RLC bearer is associated with the second logical channel but not with the first logical channel.

[0456] As an embodiment, the first RLC bearer is used for PTM reception.

[0457] As an embodiment, the first RLC bearer being used for PTM reception means that the RLC entity corresponding to the second RLC bearer is configured for PTM reception.

[0458] As an embodiment, the second RLC bearer is not configured for PTM reception.

[0459] As an embodiment, the second RLC bearer is not configured for PTM reception, which means that the second RLC bearer is used for PTP reception and / or transmission.

[0460] As an embodiment, the second RLC bearer is not configured for PTM reception meaning that the RLC entity corresponding to the second RLC bearer is not configured for PTM reception.

[0461] As an embodiment, the logical channel is an interface between the MAC sublayer and the RLC sublayer.

[0462] As an embodiment, the logical channel is a service provided by the MAC sublayer to the RLC sublayer.

[0463] As an embodiment, a cell group has only one MAC entity, that is, an MCG has one MAC entity, and each cell of the MCG uses the MAC entity of this MCG.

[0464] As a sub-embodiment of this embodiment, the second signaling is directed to MCG.

[0465] As an embodiment, the SCG has a MAC entity, and each cell of the SCG uses the MAC entity of the SCG.

[0466] As a sub-embodiment of this embodiment, the second signaling is directed to the SCG.

[0467] As an embodiment, G-RNTI is used for scheduling the first logical channel.

[0468] As an embodiment, C-RNTI is used for scheduling the second logical channel.

[0469] As an embodiment, C-RNTI is not used for scheduling the first logical channel.

[0470] As an embodiment, the scheduling of the second logical channel does not use G-RNTI.

[0471] Example 7

[0472] Embodiment 7 illustrates a schematic diagram of a first radio bearer according to an embodiment of the present application, as shown in the attached figure. Figure 7 shown.

[0473] As an example, Figure 7 An example is shown in which the target cell does not support PTM transmission. The method proposed in the present application is also applicable to the case in which the target cell supports PTM transmission, and has additional benefits when the target cell supports PTM.

[0474] As an example, Figure 7 Part (a) shows the protocol structure of the first node in the source cell; Figure 7 Part (b) in FIG. 1 shows the protocol structure of the first node in the target cell.

[0475] As an embodiment, in the source cell, the first node is configured with a first RLC bearer and a second RLC bearer, which correspond to the attached Figure 7 There are two RLC entities, RLC-1 and RLC-2.

[0476] As an embodiment, when the target cell does not support PTM transmission, the PDCP entity corresponding to the first radio bearer is not rebuilt when performing cell switching.

[0477] As an embodiment, the PDCP entity corresponding to the first radio bearer is not rebuilt, which is beneficial to reducing the switching delay and ensuring the continuity of data transmission.

[0478] As an embodiment, when the target cell does not support PTM transmission, when performing cell switching, the former of the first RLC bearer and the second radio bearer is released.

[0479] As an embodiment, when the target cell does not support PTM transmission, the logical channel identifier associated with the first RLC bearer is released when performing cell switching.

[0480] As an embodiment, when the target cell does not support PTM transmission, the RLC entity corresponding to the first RLC bearer is released when performing cell switching.

[0481] As an embodiment, when the target cell does not support PTM transmission, when performing cell switching, the former of the second RLC bearer and the second radio bearer is maintained.

[0482] As an embodiment, when the target cell does not support PTM transmission, when performing cell switching, the logical channel identifier associated with the second RLC bearer is maintained.

[0483] As an embodiment, when the target cell does not support PTM transmission, the RLC entity corresponding to the second RLC bearer is maintained when performing cell switching.

[0484] As an embodiment, the benefit of the above method is that maintaining the logical channel identifier associated with the second RLC bearer, RLC-2, at least one of the state variables and timers of RLC-2 is conducive to keeping data reception uninterrupted during the switching process and maintaining the continuity of communication.

[0485] As an embodiment, when the target cell supports PTM transmission, when performing cell switching, the logical channel identifier associated with the first RLC bearer is released.

[0486] As an embodiment, when the target cell supports PTM transmission, when performing cell switching, the RLC entity corresponding to the first RLC bearer is released.

[0487] As an embodiment, when the target cell supports PTM transmission, when performing cell switching, the logical channel identifier and the corresponding RLC entity associated with the first RLC bearer are released, which is beneficial to avoid interference with the configuration of the source cell in the target cell.

[0488] As an embodiment, the characteristic of LTM switching is that the configuration of the source cell will not be released with the execution of the switching, that is, it can continue to be used in the new cell. This is to achieve fast switching and continuous switching, which is different from traditional switching and is also the scenario specifically targeted by this application. The problem to be solved by this application is unique in such a scenario.

[0489] As an embodiment, during LTM switching, it is common knowledge in the art that the target cell maintains the configuration of the LTM indicated by the source cell.

[0490] As an embodiment, the candidate configuration indicated by the second signaling is to configure a second radio bearer, and the second radio bearer is a DRB.

[0491] As a sub-embodiment of this embodiment, only the latter of the first RLC bearer and the second RLC bearer serves the second radio bearer.

[0492] As an embodiment, in the target cell, the second RLC bearer serves a second radio bearer, and the second radio bearer is a DRB.

[0493] As an embodiment, the advantage of the above method is that even when the target cell does not support MRB, the continuity of communication during handover can be guaranteed.

[0494] As an embodiment, at least one state variable of the first radio bearer determines the value of at least one state variable of the second radio bearer.

[0495] As an embodiment, the value of at least one timer of the first radio bearer determines the value of at least one timer of the second radio bearer.

[0496] As an embodiment, the state of at least one timer of the first radio bearer determines the state of at least one timer of the second radio bearer.

[0497] Example 8

[0498] Embodiment 8 illustrates a schematic diagram of releasing the logical channel identifier associated with only the first of the first RLC bearer and the second RLC bearer according to an embodiment of the present application, depending on that one of the first radio bearer and the first RLC bearer is not configured to continue, as shown in the attached Figure 8 shown.

[0499] As an embodiment, releasing the logical channel identifier associated with only the former of the first RLC bearer and the second RLC bearer relies on the first radio bearer not being configured to continue.

[0500] As an embodiment, releasing the logical channel identifier associated with only the former of the first RLC bearer and the second RLC bearer relies on the first RLC bearer not being configured to continue.

[0501] As an embodiment, not being configured to continue refers to not being configured to continue PTM.

[0502] As an embodiment, not being configured to continue refers to not being configured to continue the MRB.

[0503] As an embodiment, not being configured to continue refers to not being configured to continue the RLC for PTM reception.

[0504] As an embodiment, when the first radio bearer is not configured to continue, the logical channel identifier associated with only the former of the first RLC bearer and the second RLC bearer is released.

[0505] As an embodiment, when the first radio bearer is configured to continue, the logical channel identifier associated with the former of the first RLC bearer and the second RLC bearer is not released.

[0506] As an embodiment, when the first RLC bearer is not configured to continue, the logical channel identifier associated with only the former of the first RLC bearer and the second RLC bearer is released.

[0507] As an embodiment, when the first RLC bearer is configured to continue, the logical channel identifier associated with the former of the first RLC bearer and the second RLC bearer is not released.

[0508] As an embodiment, the network may determine whether to configure to continue according to whether the target cell of the handover uses the same key as the source cell.

[0509] As an embodiment, the network may determine whether to configure to continue based on whether the target cell for switching is associated with the same CU (Control unit) as the source cell. For example, if they belong to the same CU, then they are configured to continue; otherwise, they are not configured to continue.

[0510] As an embodiment, the network may determine whether to configure to continue based on whether the target cell of the handover is associated with the same DU (data unit) as the source cell. For example, if they belong to the same DU, then it is configured to continue; otherwise, it is not configured to continue.

[0511] As an embodiment, the advantage of the above embodiment is that flexibility is increased.

[0512] Example 9

[0513] Embodiment 9 illustrates a schematic diagram of releasing the logical channel identifier associated with only the first of the first RLC bearer and the second RLC bearer according to an embodiment of the present application, which depends on the second parameter being equal to the first parameter. Fig. 9 shown.

[0514] As an embodiment, the third signaling indicates the first parameter.

[0515] As an embodiment, the first parameter is for the source cell.

[0516] As an embodiment, the candidate configuration indicated by the second signaling includes the second parameter.

[0517] As an embodiment, the first candidate configuration indicated by the second signaling includes the second parameter.

[0518] As an embodiment, the second parameter is for the candidate cell.

[0519] As an embodiment, when the first parameter is equal to the second parameter, the logical channel identifier associated with only the former of the first RLC bearer and the second RLC bearer is released.

[0520] As an embodiment, when the first parameter is not equal to the second parameter, the logical channel identifiers respectively associated with the first RLC bearer and the second RLC bearer are released.

[0521] As an embodiment, the first parameter and the second parameter are respectively integers.

[0522] As an embodiment, the maximum values ​​of the first parameter and the second parameter are 7 respectively.

[0523] As an embodiment, the minimum values ​​of the first parameter and the second parameter are respectively 0.

[0524] As an embodiment, the maximum values ​​of the first parameter and the second parameter are 8 respectively.

[0525] As an embodiment, the minimum values ​​of the first parameter and the second parameter are respectively 1.

[0526] As an embodiment, the first parameter is: ltm-ServingCellNoResetID.

[0527] As an embodiment, the second parameter is: ltm-NoResetID.

[0528] As an embodiment, the advantage of the above method is that flexible rows are added.

[0529] As an embodiment, the performing of cell switching includes: setting the value of the second parameter to the value of the first parameter.

[0530] As an embodiment, the benefits of the above method include: better support for continuous switching.

[0531] Example 10

[0532] Embodiment 10 illustrates a structural block diagram of a processing device used in a first node according to an embodiment of the present application; Fig.10 As shown in the attached Fig.10 In the embodiment, the processing device 1000 in the first node includes a first receiver 1001, a first transmitter 1002 and a first processor 1003.

[0533] In embodiment 10, a first receiver 1001 receives a first signaling, where the first signaling configures a first radio bearer, a first RLC bearer, and a second RLC bearer, wherein the first radio bearer is a multicast broadcast service radio bearer, the first RLC bearer and the second RLC bearer both serve the first radio bearer, an RLC entity corresponding to the first RLC bearer is configured as a PTM, and an RLC entity corresponding to the second RLC bearer is not configured as a PTM;

[0534] The first processor 1003 receives a second signaling indicating a cell switch; and performs the cell switch, which includes: releasing a logical channel identifier associated with only the first RLC bearer and the second RLC bearer.

[0535] As an embodiment, the cell switching indicated by the second signaling is an LTM cell switching.

[0536] As an embodiment, the first RLC bearer and the second RLC bearer are both configured by the RLC-BearerConfig information block of the first signaling.

[0537] As an embodiment, the releasing of the logical channel identifier associated with only the former of the first RLC bearer and the second RLC bearer depends on the first radio bearer or one of the first RLC bearers not being configured to continue.

[0538] As an embodiment, the first receiver 1001 receives a third signaling, where the third signaling includes a first parameter and at least one candidate configuration, where the at least one candidate configuration includes a first candidate configuration, and where the first candidate configuration includes a second parameter;

[0539] The second signaling indicates the first candidate configuration; the releasing of the logical channel identifier associated with only the first RLC bearer and the second RLC bearer depends on the second parameter being equal to the first parameter; and the performing of the cell switching includes: setting the value of the second parameter to the value of the first parameter.

[0540] As an embodiment, the performing of cell switching includes: releasing at least one of the RLC entity, state variable, cache and timer associated with only the former of the first RLC bearer and the second RLC bearer.

[0541] As an embodiment, the first processor 1003 reconstructs the RLC entity associated with the first RLC bearer.

[0542] As an embodiment, the first transmitter 1002 sends a first status report, wherein the first status report indicates a PDCP SDU that was not correctly received.

[0543] As an embodiment, the target cell configured by the candidate configuration indicated by the second signaling does not support sending the multicast broadcast service carried by the first radio bearer through PTM.

[0544] As an embodiment, the candidate configuration indicated by the second signaling is to configure a second radio bearer, the second radio bearer is a DRB, and only the latter of the first RLC bearer and the second RLC bearer serves the second radio bearer.

[0545] As an embodiment, the first node is a user equipment (UE).

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

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

[0548] As an embodiment, the first node is an aircraft.

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

[0550] As an embodiment, the first node is a relay.

[0551] As an embodiment, the first node is a vessel.

[0552] As an embodiment, the first node is an Internet of Things terminal.

[0553] As an embodiment, the first node is an industrial Internet of Things terminal.

[0554] As an embodiment, the first node is a device supporting low-latency and high-reliability transmission.

[0555] As an embodiment, the first node is a node supporting multicast.

[0556] As an embodiment, the first receiver 1001 includes at least one of the antenna 452, receiver 454, receiving processor 456, multi-antenna receiving processor 458, controller / processor 459, memory 460, or data source 467 in Example 4.

[0557] As an embodiment, the first transmitter 1002 includes at least one of the antenna 452, transmitter 454, transmit processor 468, multi-antenna transmit processor 457, controller / processor 459, memory 460, or data source 467 in Embodiment 4.

[0558] A person of ordinary skill in the art can understand that all or part of the steps in the above method can be completed by instructing the relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a hard disk or an optical disk. Optionally, all or part of the steps in the above embodiment can also be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiment can be implemented in the form of hardware or in the form of a software function module, and the present application is not limited to any specific form of software and hardware combination. The user equipment, terminal and UE in the present application include but are not limited to drones, communication modules on drones, remote-controlled aircraft, aircraft, small aircraft, mobile phones, tablet computers, notebooks, vehicle-mounted communication equipment, wireless sensors, Internet cards, Internet of Things terminals, RFID terminals, NB-IoT terminals, MTC (Machine Type Communication, machine type communication) terminals, eMTC (enhancedMTC, enhanced MTC) terminals, data cards, Internet cards, vehicle-mounted communication equipment, low-cost mobile phones, low-cost tablet computers, satellite communication equipment, ship communication equipment, NTN user equipment and other wireless communication equipment. The base stations or system equipment in this application include but are not limited to macrocell base stations, microcell base stations, home base stations, relay base stations, gNB (NR Node B) NR Node B, TRP (Transmitter Receiver Point, sending and receiving node), NTN base stations, satellite equipment, flight platform equipment and other wireless communication equipment.

[0559] The present invention may be implemented in other specified forms without departing from its core or essential features. Therefore, the embodiments disclosed herein should be considered as illustrative rather than restrictive in any way. The scope of the invention is determined by the appended claims rather than the preceding description, and all modifications within their equivalent meanings and regions are considered to be included therein.

Claims

1. A first node used for cell switching in wireless communication, wherein: include: A first receiver receives a first signaling, wherein the first signaling configures a first radio bearer, a first RLC bearer, and a second RLC bearer, wherein the first radio bearer is a multicast broadcast service radio bearer, the first RLC bearer and the second RLC bearer both serve the first radio bearer, an RLC entity corresponding to the first RLC bearer is configured as a PTM, and an RLC entity corresponding to the second RLC bearer is not configured as a PTM; The first processor receives a second signaling indicating a cell switch; and performs the cell switch, which includes: releasing a logical channel identifier associated with only the first RLC bearer and the second RLC bearer.

2. The first node according to claim 1, characterized in that: The cell handover indicated by the second signaling is an LTM cell handover.

3. The first node according to claim 1 or 2, characterized in that: The first RLC bearer and the second RLC bearer are both configured by the RLC-BearerConfig information block of the first signaling.

4. The first node according to any one of claims 1 to 3, characterized in that: The releasing of the logical channel identifier associated with only the former of the first RLC bearer and the second RLC bearer relies on the first radio bearer or one of the first RLC bearers not being configured to continue.

5. The first node according to any one of claims 1 to 4, characterized in that: include: The first receiver receives a third signaling, where the third signaling includes a first parameter and at least one candidate configuration, where the at least one candidate configuration includes a first candidate configuration, and where the first candidate configuration includes a second parameter; The second signaling indicates the first candidate configuration; the releasing of the logical channel identifier associated with only the first RLC bearer and the second RLC bearer depends on the second parameter being equal to the first parameter; and the performing of the cell switching includes: setting the value of the second parameter to the value of the first parameter.

6. The first node according to any one of claims 1 to 5, characterized in that: The performing of the cell switching includes: releasing at least one of an RLC entity, a state variable, a cache and a timer associated with only the former of the first RLC bearer and the second RLC bearer.

7. The first node according to any one of claims 1 to 6, characterized in that: include: The first processor reestablishes the RLC entity associated with the first RLC bearer.

8. The first node according to any one of claims 1 to 7, characterized in that: include: A first transmitter sends a first status report indicating a PDCP SDU that was not correctly received.

9. The first node according to any one of claims 1 to 8, characterized in that: The target cell configured by the candidate configuration indicated by the second signaling does not support sending the multicast broadcast service carried by the first radio bearer through PTM.

10. The first node according to any one of claims 1 to 9, characterized in that: The candidate configuration indicated by the second signaling is to configure a second radio bearer, the second radio bearer is a DRB, and only the latter of the first RLC bearer and the second RLC bearer serves the second radio bearer.

11. A method in a first node for cell switching in wireless communication, wherein: include: receiving a first signaling, wherein the first signaling configures a first radio bearer, a first RLC bearer, and a second RLC bearer, wherein the first radio bearer is a multicast broadcast service radio bearer, the first RLC bearer and the second RLC bearer both serve the first radio bearer, an RLC entity corresponding to the first RLC bearer is configured as a PTM, and an RLC entity corresponding to the second RLC bearer is not configured as a PTM; Receiving a second signaling indicating a cell switch; performing the cell switch, which includes: releasing a logical channel identifier associated with only the first RLC bearer and the second RLC bearer.

Images