CN116095632A - Method and apparatus for wireless communication - Google Patents

Method and apparatus for wireless communication Download PDF

Info

Publication number
CN116095632A
CN116095632A CN202111314627.0A CN202111314627A CN116095632A CN 116095632 A CN116095632 A CN 116095632A CN 202111314627 A CN202111314627 A CN 202111314627A CN 116095632 A CN116095632 A CN 116095632A
Authority
CN
China
Prior art keywords
signaling
timer
node
operations
domain
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202111314627.0A
Other languages
Chinese (zh)
Inventor
陈宇
张晓博
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shanghai Langbo Communication Technology Co Ltd
Original Assignee
Shanghai Langbo Communication Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shanghai Langbo Communication Technology Co Ltd filed Critical Shanghai Langbo Communication Technology Co Ltd
Publication of CN116095632A publication Critical patent/CN116095632A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30Services specially adapted for particular environments, situations or purposes
    • H04W4/40Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/0001Arrangements for dividing the transmission path
    • H04L5/0003Two-dimensional division
    • H04L5/0005Time-frequency
    • H04L5/0007Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053Allocation of signaling, i.e. of overhead other than pilot signals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/02Arrangements for optimising operational condition
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/08Reselecting an access point
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • H04W72/044Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453Resources in frequency domain, e.g. a carrier in FDMA
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/14Direct-mode setup
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/20Manipulation of established connections
    • H04W76/27Transitions between radio resource control [RRC] states
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/30Connection release

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

A method and apparatus for wireless communication includes starting a first timer, the first timer being used for access barring; receiving first signaling, the first signaling being used to configure an MCG, the first signaling comprising a first domain; in response to receiving the first signaling, performing a first set of operations; wherein the first domain is a reconfigurationWithSync, and the first operation set includes sending a second signaling for confirming that configuration of at least the first signaling is successfully completed; the first signaling is used to indicate whether the first set of operations includes stopping the first timer. By receiving the first signaling, the method and the device can avoid network congestion.

Description

Method and apparatus for wireless communication
Technical Field
The present invention relates to a transmission method and apparatus in a wireless communication system, and in particular, to a method and apparatus for reducing service interruption and improving service continuity in sidelink relay communication.
Background
Future wireless communication systems have more and more diversified application scenes, and different application scenes have different performance requirements on the system. To meet the different performance requirements of various application scenarios, a New air interface technology (NR) is decided to be researched in the 3GPP (3 rd Generation Partner Project, third Generation partnership project) RAN (Radio Access Network ) #72 times of the whole meeting, and standardized Work is started on NR by the 3GPP RAN #75 times of the whole meeting through the WI (Work Item) of NR.
In communication, both LTE (Long Term Evolution ) and 5GNR can be related to reliable accurate reception of information, optimized energy efficiency ratio, determination of information validity, flexible resource allocation, scalable system structure, efficient non-access layer information processing, lower service interruption and disconnection rate, low power consumption support, which is significant for normal communication of base stations and user equipment, reasonable scheduling of resources, balancing of system load, so-called high throughput, meeting communication requirements of various services, improving spectrum utilization, improving quality of service, whether eMBB (ehanced Mobile BroadBand, enhanced mobile broadband), URLLC (Ultra Reliable Low Latency Communication, ultra-high reliability low latency communication) or eMTC (enhanced Machine Type Communication ) are indispensable. Meanwhile, in the internet of things in the field of IIoT (Industrial Internet of Things), in V2X (vehicle to X) communication (Device to Device) in the field of industry, in communication of unlicensed spectrum, in monitoring of user communication quality, in network planning optimization, in NTN (Non Territerial Network, non-terrestrial network communication), in TN (Territerial Network, terrestrial network communication), in dual connectivity (Dual connectivity) system, in radio resource management and codebook selection of multiple antennas, in signaling design, neighbor management, service management, and beamforming, there is a wide demand, and the transmission modes of information are broadcast and unicast, both transmission modes are indispensable for 5G system, because they are very helpful to meet the above demands.
With the increasing of the scene and complexity of the system, the system has higher requirements on reducing the interruption rate, reducing the time delay, enhancing the reliability, enhancing the stability of the system, and the flexibility of the service, and saving the power, and meanwhile, the compatibility among different versions of different systems needs to be considered in the system design.
The 3GPP standardization organization performs related standardization work for 5G, and forms a series of standards including 38.304,38.211,38.213, etc., and reference may be made to the standard content:
https://www.3gpp.org/ftp/Specs/archive/38_series/38.304/38304-g40.zip
https://www.3gpp.org/ftp/Specs/archive/38_series/38.211/38211-g50.zip
https://www.3gpp.org/ftp/Specs/archive/38_series/38.213/38213-g50.zip
https://www.3gpp.org/ftp/Specs/archive/38_series/38.331/38331-g50.zip
disclosure of Invention
In various communication scenarios, the use of relays may be involved, for example, when one UE is not within the coverage area of a cell, the network may be accessed through a relay, which may be another UE. The relay mainly comprises a layer 3 relay and a layer 2 relay (U2 Nrelay UE), which are used for providing network access service for a remote node (U2N remote UE) through a relay node, wherein the layer 3 relay is transparent to an access network, namely the remote UE only establishes connection with a core network, and the access network cannot identify whether data come from the remote node or the relay node; in layer 2 relay, a remote node (U2N remote UE) and an access network (RAN) have RRC connections, the access network may manage the remote node, and a radio bearer may be established between the access network and the remote node. In a system using layer 2 relay, a UE may communicate with a network through relay, i.e., using an indirect path (direct path), or may communicate with the network directly without relay, i.e., using a direct path (direct path). In some cases, such as signal degradation of the network, the remote node may switch from a direct path to an indirect path; when the network signal becomes good, it can also switch from the indirect path to the direct path. In such a case, the 5G NR network may instruct the remote node to complete the path conversion using signaling including reconfigurationWithSync. Such path switching is typically performed within a cell, and the switching within a cell involves the problem of whether or not the access barring (access barring) related timer is stopped, and in general, if the cell is not changed, the access barring timer may not be stopped. On the other hand, signalling including reconfigurationWithSync may also (often) be used to indicate handover between cells, for which a handover from one cell to another is required, the access blocking timer is stopped, since a new cell is changed, which may not be congested without performing access blocking, but which would not be changed by a path change if the cell was not changed, so it is preferable not to stop the access blocking timer in this case. One problem to be solved is therefore how to determine whether the access blocking timer should be stopped based on very similar signalling (i.e. both include reconfiguration wishsync).
In view of the above problems, the present application provides a solution.
It should be noted that, in the case of no conflict, the embodiments in any node of the present application and the features in the embodiments may be applied to any other node. The embodiments of the present application and features in the embodiments may be combined with each other arbitrarily without conflict.
The application discloses a method in a first node used for wireless communication, comprising:
starting a first timer, the first timer being used for access barring;
receiving first signaling, the first signaling being used to configure an MCG, the first signaling comprising a first domain; in response to receiving the first signaling, performing a first set of operations;
wherein the first domain is a reconfigurationWithSync, and the first operation set includes sending a second signaling for confirming that configuration of at least the first signaling is successfully completed; the first signaling is used to indicate whether the first set of operations includes stopping the first timer.
As one embodiment, the problems to be solved by the present application include: how to determine whether the access blocking timer should be stopped according to different situations.
As one example, the benefits of the above method include: whether to stop the access blocking timer can be reasonably determined according to specific conditions; comprising the following steps: the access blocking timer is not stopped when the conversion from the indirect path to the direct path is performed; the access blocking timer is stopped when a cell handover is performed.
Specifically, according to one aspect of the present application, the format of the first signaling is used to determine whether the first set of operations includes stopping the first timer; the format of the first signaling is one candidate format in a candidate format set, the candidate format set comprising at least two candidate formats, a first format and a second format; any two candidate formats in the candidate format set are two RRC IEs with different names; the first set of operations includes stopping the first timer when the format of the first signaling is the first format, and the first set of operations does not include stopping the first timer when the format of the first signaling is the second format.
In particular, according to one aspect of the application, the first signaling includes a second field, the second field of the first signaling being used to determine whether the first set of operations includes stopping the first timer.
In particular, according to one aspect of the present application, the first field of the first signaling is used to determine whether the first set of operations includes stopping the first timer.
Specifically, according to one aspect of the present application, a first conditional reconfiguration is received, the first conditional reconfiguration including a first condition and the first signaling associated with the first condition; in response to a first condition being met, performing the first signaling; in response to performing the first signaling, the first set of operations is performed.
Specifically, according to one aspect of the present application, after the act of receiving the first signaling, receiving second signaling, the second signaling being used to indicate a transition from a direct path to an indirect path;
executing the second signaling; stopping the first timer in response to performing the second signaling;
wherein the indirect path is that data transmission between the first node and a network is forwarded through a relay; the direct path is that data transmission between the first node and the network does not pass through a relay.
In particular, according to one aspect of the present application, when the first signaling used to indicate the first set of operations includes stopping the first timer, the primary cell of the first node remains unchanged before and after the first signaling is performed; when the first set of operations of the first signaling is used to indicate that the first set of operations does not include stopping the first timer, a primary cell of the first node changes before and after the first signaling is performed.
Specifically, according to one aspect of the present application, a second timer is started in response to performing the first signaling;
initiating a first random access procedure for the cell indicated by the first signaling, a successful completion of the first random access procedure being used to stop the second timer;
wherein expiration of the second timer is used to trigger RRC reestablishment.
Specifically, according to one aspect of the present application, the first node is a user equipment.
Specifically, according to one aspect of the present application, the first node is an internet of things terminal.
Specifically, according to one aspect of the present application, the first node is a relay.
Specifically, according to one aspect of the present application, the first node is a U2NremoteUE.
Specifically, according to one aspect of the present application, the first node is a vehicle-mounted terminal.
In particular, according to one aspect of the present application, the first node is an aircraft.
A method in a second node for wireless communication, comprising:
transmitting first signaling, the first signaling being used to configure an MCG, the first signaling comprising a first domain;
wherein the receiving of the first signaling is used to trigger execution of a first set of operations; the first domain is a reconfigurationWithSync, and the first operation set includes sending second signaling for confirming that configuration of at least the first signaling is successfully completed; the first signaling is used to indicate whether the first set of operations includes stopping a first timer, the first timer being used for access barring.
Specifically, according to one aspect of the present application, the format of the first signaling is used to determine whether the first set of operations includes stopping the first timer; the format of the first signaling is one candidate format in a candidate format set, the candidate format set comprising at least two candidate formats, a first format and a second format; any two candidate formats in the candidate format set are two RRC IEs with different names; the first set of operations includes stopping the first timer when the format of the first signaling is the first format, and the first set of operations does not include stopping the first timer when the format of the first signaling is the second format.
In particular, according to one aspect of the application, the first signaling includes a second field, the second field of the first signaling being used to determine whether the first set of operations includes stopping the first timer.
In particular, according to one aspect of the present application, the first field of the first signaling is used to determine whether the first set of operations includes stopping the first timer.
Specifically, according to one aspect of the present application, a first conditional reconfiguration is sent, the first conditional reconfiguration including a first condition and the first signaling associated with the first condition; a first condition is satisfied that is used to trigger a receiver of the first signaling to perform the first signaling; the first signaling is performed to trigger a recipient of the first signaling to perform the first set of operations.
Specifically, according to one aspect of the present application, after the act of transmitting the first signaling, transmitting second signaling, the second signaling being used to indicate a transition from a direct path to an indirect path;
the second signaling is performed by a receiver of the second signaling and is used to trigger the stopping of the first timer;
wherein the indirect path is that data transmission between the first node and a network is forwarded through a relay; the direct path is that data transmission between the first node and the network does not pass through a relay.
Specifically, according to one aspect of the present application, when the first signaling used to indicate the first set of operations includes stopping the first timer, the primary cell of the receiver of the first signaling remains unchanged before the receiver of the first signaling performs the first signaling and after the receiver of the first signaling performs the first signaling; when the first set of operations of the first signaling used to indicate that the first set of operations does not include stopping the first timer, a primary cell of a receiver of the first signaling changes before and after the receiver of the first signaling performs the first signaling.
Specifically, according to one aspect of the present application, the second node is a base station.
Specifically, according to one aspect of the present application, the second node is a relay.
In particular, according to one aspect of the present application, the second node is an aircraft.
In particular, according to one aspect of the present application, the second node is a satellite.
Specifically, according to one aspect of the present application, the second node is an access point device.
The application discloses a first node for wireless communication, comprising:
a first processor to start a first timer, the first timer being used for access barring;
the first processor receives first signaling, the first signaling being used to configure an MCG, the first signaling comprising a first domain; in response to receiving the first signaling, performing a first set of operations;
wherein the first domain is a reconfigurationWithSync, and the first operation set includes sending a second signaling for confirming that configuration of at least the first signaling is successfully completed; the first signaling is used to indicate whether the first set of operations includes stopping the first timer.
The application discloses a second node for wireless communication, comprising:
a second transmitter that transmits first signaling, the first signaling being used to configure the MCG, the first signaling including a first domain;
wherein the receiving of the first signaling is used to trigger execution of a first set of operations; the first domain is a reconfigurationWithSync, and the first operation set includes sending second signaling for confirming that configuration of at least the first signaling is successfully completed; the first signaling is used to indicate whether the first set of operations includes stopping a first timer, the first timer being used for access barring.
As an example, compared to the conventional solution, the present application has the following advantages:
it may be determined for different situations whether the access blocking timer should be stopped, in order to avoid network congestion, or to avoid delays or interruptions in traffic.
The same RRC message can be used for supporting path conversion and cell switching, and the complexity of signaling is reduced.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the detailed description of non-limiting embodiments, made with reference to the following drawings in which:
FIG. 1 illustrates a flow chart of starting a first timer, receiving first signaling, and performing a first set of operations according to one embodiment of the present application;
FIG. 2 shows a schematic diagram of a network architecture according to one embodiment of the present application;
fig. 3 shows a schematic diagram of an embodiment of a radio protocol architecture of a user plane and a control plane according to one embodiment of the present application;
FIG. 4 shows a schematic diagram of a first communication device and a second communication device according to one embodiment of the present application;
fig. 5 shows a flow chart of wireless signal transmission according to one embodiment of the present application;
figure 6 shows a schematic diagram of an RRC message according to one embodiment of the present application;
FIG. 7 illustrates a schematic diagram of a protocol stack for relaying communications according to one embodiment of the present application;
FIG. 8 illustrates a schematic diagram of a second domain of first signaling being used to determine whether a first set of operations includes stopping a first timer, according to one embodiment of the present application;
FIG. 9 shows a schematic diagram of a first domain of first signaling being used to determine whether a first set of operations includes stopping a first timer, according to one embodiment of the present application;
FIG. 10 illustrates a schematic diagram of a processing device for use in a first node according to one embodiment of the present application;
Fig. 11 illustrates a schematic diagram of a processing device for use in a second node according to one embodiment of the present application.
Description of the embodiments
The technical solution of the present application will be further described in detail with reference to the accompanying drawings, and it should be noted that, without conflict, the embodiments and features of the embodiments in the present application may be arbitrarily combined with each other.
Example 1
Embodiment 1 illustrates a flowchart for starting a first timer, receiving a first signaling, and performing a first set of operations according to one embodiment of the present application, as shown in fig. 1. In fig. 1, each block represents a step, and it is emphasized that the order of the blocks in the drawing does not represent temporal relationships between the represented steps.
In embodiment 1, a first node in the present application starts a first timer in step 101; receiving first signaling in step 102; performing a first set of operations in step 103;
wherein the first timer is used for access barring (access barring); the first signaling is used to configure the MCG, the first signaling including a first domain; in response to receiving the first signaling, performing a first set of operations; the first domain is a reconfigurationWithSync, and the first operation set includes sending second signaling for confirming that configuration of at least the first signaling is successfully completed; the first signaling is used to indicate whether the first set of operations includes stopping the first timer.
As an embodiment, the first node is a UE (User Equipment).
As an embodiment, the first node is not operating in an SNPN AM (Access Mode).
As an embodiment, a direct path (direct path) refers to a UE-to-network transmission path by which transmission means that data is sent between a remote UE of the UE-to-network (U2N) and the network without being relayed.
As a sub-embodiment of this embodiment, the data includes higher layer data and signaling.
As a sub-embodiment of this embodiment, the data comprises RRC signaling.
As a sub-embodiment of this embodiment, the data comprises a string or block of bits.
As a sub-embodiment of this embodiment, the data includes only signaling or data carried by RBs (radio bearers).
As one embodiment, an indirect path refers to a transmission path of a UE to a Network, through which data is transmitted, meaning that the data is forwarded between a remote UE of the UE to the Network (U2N, UE-to-Network) and the Network via a relay UE of the UE to the Network (U2N, UE-to-Network).
As a sub-embodiment of this embodiment, the data includes higher layer data and signaling.
As a sub-embodiment of this embodiment, the data comprises RRC signaling.
As a sub-embodiment of this embodiment, the data comprises a string or block of bits.
As a sub-embodiment of this embodiment, the data includes only signaling or data carried by RBs (radio bearers).
As one embodiment, a U2N relay UE refers to a UE that provides functionality to support the connection of a U2N remote UE to a network.
As one embodiment, a U2N remote UE refers to a UE that needs to communicate with a network via a U2N relay UE.
As one embodiment, a U2N remote UE refers to a UE that needs to communicate with a network via a U2N relay UE.
As one embodiment, a U2N remote UE refers to a UE that communicates with a network supporting relay services.
As one embodiment, the U2N relay is a U2N relay UE.
As an embodiment, when unicast service is sent and received with the network, both the U2N relay and the U2N remote node are in RRC connected state.
As an embodiment, when the U2N remote UE is in an RRC idle state or an RRC inactive state, the U2N relay UE may be in any RRC state, including an RRC connected state, an RRC idle state, and an RRC inactive state.
As an embodiment, not transmitting over a direct path is equal to transmitting over an indirect path.
As one embodiment, not transmitting over a direct path includes transmitting over a relay.
As one embodiment, transmitting over a direct path is or includes transmitting without relaying.
As one embodiment, transmitting over the direct path is or includes forwarding without relaying.
As one embodiment, the U2N relay UE is a UE that provides functionality (functionality) support for a U2N remote UE to connect to a network.
As a sub-embodiment of this embodiment, the U2N relay UE is a UE.
As a sub-embodiment of this embodiment, the U2N relay UE provides relay services to the network for the U2N remote UE.
As one embodiment, the U2N remote UE is a UE that communicates with the network through a U2N relay UE.
As one embodiment, a direct mode is a mode using the direct path.
As one embodiment, the direct mode is a mode in which the U2N remote UE communicates with the network using the direct path.
As an embodiment, the direct mode is a mode in which the U2N remote UE uses the direct path to transmit RRC signaling or establish an RRC connection with the network.
As one embodiment, the indirect (indirect) mode is a mode using the indirect path.
As an embodiment, the indirect mode is a mode using the indirect path.
As one embodiment, the direct mode is a mode in which the U2N remote UE communicates with the network using the indirect path.
As an embodiment, the direct mode is a mode in which the U2N remote UE uses the indirect path to transmit RRC signaling or establish an RRC connection with the network.
As an embodiment, the serving cell is or includes a cell in which the UE resides. Performing a cell search includes the UE searching for a suitable (subscriber) cell of the selected PLMN (Public land mobile Network ) or SNPN (Stand-alone Non-Public Network), selecting the suitable cell to provide available service, monitoring a control channel of the suitable cell, which is defined as camping on the cell; that is, a camped cell, with respect to the UE, is the serving cell for the UE. Camping on one cell in RRC idle state or RRC inactive state has the following benefits: such that the UE may 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 may perform initial access on the control channel of the camping cell; the network may page to the UE; so that the UE can receive ETWS (Earthquake and Tsunami Warning System, earthquake tsunami warning system) and CMAS (Commercial Mobile Alert System ) notifications.
As an embodiment, for a U2N remote node, the serving cell is or includes the cell in which the U2N relay resides or is connected.
As an embodiment, for a UE in RRC connected state without CA/DC (carrier aggregation/dual connectivity ) configuration, only one serving cell includes the primary cell. For UEs in RRC connected state that are CA/DC (carrier aggregation/dual connectivity ) configured, the serving Cell is used to indicate the set of cells including the Special Cell (SpCell) and all the secondary cells. The Primary Cell (Primary Cell) is a MCG (Master Cell Group) Cell, operating on the Primary frequency, on which the UE performs an initial connection establishment procedure or initiates connection re-establishment. For the dual connectivity operation, the special Cell refers to a PCell (Primary Cell) of MCG or a PSCell (Primary SCG Cell) of SCG (Secondary Cell Group); if not dual connectivity operation, the special cell is referred to as a PCell.
As an example, the frequency at which the SCell (Secondary Cell, slave Cell) operates is the slave frequency.
For one embodiment, the individual content of the information element is referred to as a field.
As an example, MR-DC (Multi-Radio Dual Connectivity ) refers to dual connectivity of E-UTRA and NR nodes, or dual connectivity between two NR nodes.
As an embodiment, in MR-DC, the radio access node providing the control plane connection to the core network is a master node, which may be a master eNB, a master ng-eNB, or a master gNB.
As an embodiment, MCG refers to a set of serving cells associated with a primary node, including SpCell, and optionally, one or more scells, in MR-DC.
As an example, PCell is SpCell of MCG.
As one example, PSCell is the SpCell of SCG.
As an embodiment, in MR-DC, the radio access node that does not provide control plane connection to the core network, providing additional resources to the UE, is a slave node. The slave node may be an en-gNB, a slave ng-eNB or a slave gNB.
As an embodiment, in MR-DC, the set of serving cells associated with the slave node is SCG (secondary cell group, slave cell group), including SpCell and, optionally, one or more scells.
As one embodiment, the access layer function that enables V2X (Vehicle-to-evaluation) communications defined in 3GPP standard TS 23.285 is V2X sidelink communications (V2X sidelink communication), which occur between nearby UEs and which use E-UTRA technology but do not traverse network nodes.
As one embodiment, at least the access layer function enabling V2X (Vehicle-to-evaluation) communications defined in 3GPP standard TS23.287 is NR sidelink communications (NR sidelink communication), where the NR sidelink communications occur between two or more UEs in close proximity and use NR technology but do not traverse a network node.
As one embodiment, the sidelink is a direct communication link between UE-to-UEs using sidelink resource allocation patterns, physical layer signals or channels, and physical layer procedures.
As an example, not or not within or outside of the coverage is equal to the coverage.
As one embodiment, the in-coverage is equal to the in-coverage.
As an embodiment, the out-of-coverage is equal to the out-of-coverage.
As an embodiment, the first node is a U2N remote node.
As an embodiment, PDCP entities corresponding to radio bearers terminated between the UE and the network are located within the UE and the network, respectively.
As an embodiment, the direct path is a direct path or a communication link or channel or bearer used when transmitting over the direct path.
As an embodiment, the direct path transmission refers to that data carried by at least SRB (Signaling radio bearer ) between the UE and the network is not relayed or forwarded by other nodes.
As an embodiment, the direct path transmission refers to that RLC bearers associated with at least SRBs (Signaling radio bearer, signaling radio bearers) between the UE and the network are terminated by the UE and the network, respectively.
As an embodiment, the direct path transmission refers to that RLC entities associated with at least SRBs (Signaling radio bearer, signaling radio bearers) between the UE and the network are terminated by the UE and the network, respectively.
As an embodiment, the direct path transmission refers to that there is a direct communication link between the UE and the network.
As an embodiment, the direct path transmission refers to that a Uu interface exists between the UE and the network.
As an embodiment, the direct path transmission refers to a MAC layer where a Uu interface exists between the UE and the network, and the MAC layer of the Uu interface carries RRC signaling.
As an embodiment, the direct path transmission refers to a physical layer where a Uu interface exists between the UE and the network.
As an embodiment, the direct path transmission refers to the presence of a logical channel and/or a transport channel between the UE and the network.
As an embodiment, the indirect path is an indirect path or a communication link or channel or bearer used when transmitting over the indirect path.
As an embodiment, the indirect path transmission refers to the relay or forwarding of data carried by at least SRB (Signaling radio bearer ) between the UE and the network via other nodes.
As an embodiment, the indirect path transmission refers to that RLC bearers associated with at least SRB (Signaling radio bearer ) between the UE and the network are terminated by the UE and other nodes, other nodes and the network, respectively.
As an embodiment, the indirect path transmission refers to that RLC entities associated with at least SRBs (Signaling radio bearer, signaling radio bearers) between the UE and the network are terminated by the UE and other nodes, respectively, the other nodes and the network.
As an embodiment, the indirect path transmission refers to that there is no direct communication link between the UE and the network.
As an embodiment, the indirect path transmission refers to a MAC layer where a Uu interface does not exist between the UE and the network.
As an embodiment, the indirect path transmission refers to a physical layer where no Uu interface exists between the UE and the network.
As an embodiment, the indirect path transmission refers to that there is no logical channel or no transmission channel between the UE and the network.
As an embodiment, the network comprises a Radio Access Network (RAN) and/or a serving cell and/or a base station.
As an embodiment, the meaning of the phrase at least SRB includes at least one of { SRB0, SRB1, SRB2, SRB3 }.
As an embodiment, the phrase at least the meaning of SRB includes SRB and DRB (data radio bearer ).
As an embodiment, the phrase UE and the UE in the network comprise the first node.
As an embodiment, the other nodes comprise relay nodes or other UEs.
As one embodiment, the UE may send physical layer signaling to the network when using direct path transmission; when using indirect path transmission, the UE cannot send or directly send physical layer signaling to the network;
as one embodiment, the UE may send a MAC CE to the network when using direct path transmission; when indirect path transmission is used, the UE cannot send or directly send MAC CEs to the network;
as an embodiment, when direct path transmission is used, no other protocol layer exists between the PDCP layer and RLC layer of the first node; when indirect path transmission is used, there are other protocol layers between the PDCP layer and the RLC layer of the first node.
As a sub-embodiment of this embodiment, the other protocol layer is or comprises an adaptation layer.
As an embodiment, when using direct path transmission, the network directly schedules uplink transmission of the first node through DCI; when indirect path transmission is used, the network does not directly schedule uplink transmission of the first node through DCI.
As an embodiment, when using direct path transmission, the SRB of the first node is associated with an RLC entity and/or RLC layer and/or RLC bearer; when using indirect path transmission, the SRB of the first node is associated with the RLC entity of the PC5 interface.
As an embodiment, when using direct path transmission, there is a mapping relationship between the SRB of the first node and the RLC entity of the Uu interface; when indirect path transmission is used, the SRB of the first node has a mapping relation with the RLC entity of the PC5 interface.
As an embodiment, there is only a direct path or only an indirect path between the first node and the network.
As an embodiment, the meaning of converting from a direct path to an indirect path is: the indirect path starts to be used while the direct path stops to be used.
As an embodiment, the meaning of converting from a direct path to an indirect path is: the indirect path transmission is started while the direct path transmission is stopped.
As an embodiment, the meaning of converting from a direct path to an indirect path is: from direct path transmission to indirect path transmission.
As an embodiment, the meaning of converting from a direct path to an indirect path is: the first node associates an SRB with an RLC entity of a PC5 interface while releasing the RLC entity of the Uu interface associated with the SRB.
As an embodiment, the meaning of converting from a direct path to an indirect path is: the first node associates SRBs and DRBs with RLC entities of the PC5 interface while releasing RLC entities of the Uu interface associated with the SRBs and DRBs.
As an embodiment, the relay in the present application refers to a U2N relay UE.
As an embodiment, the meaning of converting from an indirect path to a direct path is: the use of the indirect path is stopped and the use of the direct path is started.
As an embodiment, the meaning of converting from an indirect path to a direct path is: the indirect path transmission is stopped while the direct path transmission is started.
As an embodiment, the meaning of converting from an indirect path to a direct path is: from indirect path transmission to direct path transmission.
As an embodiment, the meaning of converting from an indirect path to a direct path is: the SRB of the first node is no longer associated with the RLC entity of the PC5 interface, while the SRB is associated to the RLC entity of the Uu interface.
As a sub-embodiment of this embodiment, the SRB is one of SRB1, SRB2, SRB 3.
As a sub-embodiment of this embodiment, the SRB of the first node no longer being associated with the RLC entity of the PC5 interface comprises: the RLC entity of the PC5 interface associated with the SRB of the first node is released.
As an embodiment, the meaning of converting from an indirect path to a direct path is: the SRB and DRB of the first node are no longer associated with the RLC entity of the PC5 interface, and the SRB and the DRB of the first node are associated with the RLC entity of the Uu interface.
As a sub-embodiment of this embodiment, the SRB is one of SRB1, SRB2, SRB 3.
As a sub-embodiment of this embodiment, the SRB of the first node no longer being associated with the RLC entity of the PC5 interface comprises: the RLC entity of the PC5 interface associated with the SRB of the first node is released; the DRB of the first node no longer being associated with the RLC entity of the PC5 interface comprises: the RLC entity of the PC5 interface associated with the DRB of the first node is released.
As one embodiment, the act of starting the first timer includes starting and restarting the first timer.
As one example, the first timer is T390.
As a sub-embodiment of this embodiment, the first timer is for any access category (access category).
As a sub-embodiment of this embodiment, the first timer is for any access class (access class).
As a sub-embodiment of this embodiment, the first timer is for a partial access class.
As a sub-embodiment of this embodiment, the first timer is only for a part of the access categories.
As a sub-embodiment of this embodiment, the first timer is for an access class other than access class 0.
As a sub-embodiment of this embodiment, the first timer is for an access class other than access class 2.
As a sub-embodiment of this embodiment, the first timer is for access categories other than access categories 0 and 2.
As a sub-embodiment of this embodiment, the first timer is for access class 0.
As a sub-embodiment of this embodiment, the first timer is for access class 2.
As a sub-embodiment of this embodiment, the first timer is for access class 0 or access class 2.
As a sub-embodiment of this embodiment, the first timer is for all access categories.
As a sub-embodiment of this embodiment, the first timer is for an access class.
As one embodiment, the first timer is T302.
As one embodiment, the first timer is either T302 or T390.
As one embodiment, when the first timer is in an operational state, access or service requests initiated by the first node are blocked.
As one embodiment, the first node relinquishes initiating access when the first timer is in an operational state.
As a sub-embodiment of this embodiment, the first node gives up initiating access for the access class for which the first timer is intended.
As one embodiment, the first node discards initiating a service request when the first timer is in an operational state.
As a sub-embodiment of this embodiment, the first node gives up initiating traffic requests for the access class for which the first timer is intended.
As an embodiment, the first node gives up initiating a connection establishment when the first timer is in an operational state.
As a sub-embodiment of this embodiment, the first node gives up initiating connection establishment for the access class for which the first timer is intended.
As an embodiment, the first timer is used for UAC (unified access barring ) check.
As an embodiment, the first node first performs a UAC check when initiating a new service, and the first node starts the first timer as a part of or as a result of performing the UAC check.
As an embodiment, the serving cell or base station of the first node configures the first timer.
As an embodiment, the first signaling is used to configure MCG, which means that the first signaling includes masterCellGroup to configure MCG of the first node.
As an embodiment, the first signaling is used to configure MCG, which means that the ServCellIndex in SpCellConfig included in the first signaling is equal to 0.
As an embodiment, the first signaling is used to configure MCG, which means that ServCellIndex in the first format included in the first signaling is equal to 0.
As an embodiment, the first signaling is used to configure MCG, which means that ServCellIndex in the second format included in the first signaling is equal to 0.
As an embodiment, there is and only one MCG when the first node is in RRC connected state.
As an embodiment, the first signaling is used to configure the MCG, and includes at least one of configuration { identity of the MCG, RLC bearer of the MCG, MAC layer of the MCG, physical layer of the MCG, random access resource of the MCG, identity of the first node in the MCG, radio link failure related timer of the MCG }.
As an embodiment, receiving the first signaling is equal to performing the first signaling.
As an embodiment, the first signaling is rrcrecon configuration.
As an embodiment, the first signaling is mobile from nrcommunication.
As one embodiment, the first node starts a first timer, the first timer being used for access barring; the first node receives a first signaling, wherein the first signaling is a mobile from NRCommand; in response to receiving the first signaling, performing a first set of operations; wherein the first set of operations includes sending second signaling for confirming that configuration of at least the first signaling was successfully completed; the first signaling is used to indicate whether the first set of operations includes stopping the first timer.
As an embodiment, the first set of operations includes performing a configuration indicated by the first signaling.
As an embodiment, the first set of operations includes storing at least a portion of the fields comprised by the first signaling in a state variable.
As an embodiment, the first set of operations includes initiating a random access procedure for the SpCell indicated by the first signaling.
As an embodiment, the first signaling is used to indicate a transition from the indirect path to the direct path.
As a sub-embodiment of this embodiment, all SRBs and all DRBs of the first node, except at least SRB0, are transmitted using an indirect path before the first signaling is received.
As a sub-embodiment of this embodiment, at least all SRBs and all DRBs of the first node other than SRB0 are associated with an RLC bearer or RLC entity of the PC5 interface before the first signaling is received.
As a sub-embodiment of this embodiment, at least all SRBs and all DRBs of the first node other than SRB0 are not associated with RLC bearers or RLC entities of the Uu interface before the first signaling is received.
As a sub-embodiment of this embodiment, after completing the transition from non-direct to the direct path, all SRBs and all DRBs of the first node, except at least SRB0, are associated with RLC bearers or RLC entities of the Uu interface, and all SRBs and all DRBs of the first node, except at least SRB0, are no longer associated with RLC bearers or RLC entities of the PC5 interface.
As a sub-embodiment of this embodiment, the first signaling instructs the first node to release all PC5 interface RLC entities or RLC bearers associated with SRBs and DRBs.
As a sub-embodiment of this embodiment, the first signaling indicates that at least SRBs other than SRB0 and all DRBs of the first node are associated to a Uu interface RLC entity or RLC bearer.
As a sub-embodiment of this embodiment, the first signaling indicates that at least SRBs other than SRB0 and all DRBs of the first node are no longer associated with any PC5 interface RLC entity or RLC bearer.
As an embodiment, when using direct path transmission, the first node does not use the adaptation layer, i.e. the RLC PDU does not include an adaptation layer PDU; when using indirect path transmission, the first node uses the adaptation layer, i.e. the adaptation layer PDU is included in at least part of the RLC PDUs.
As a sub-embodiment of this embodiment, the adaptation layer is PC5-ADAPT.
As one embodiment, the first set of operations includes sending a first message using SRB0, the logical channel identity used by the first message being either 0 or 52.
As a sub-embodiment of this embodiment, when using the indirect path, the logical channel identities corresponding to SRB0 are values other than 0 and 52.
As an embodiment, the first signaling is used to indicate a transition from the direct path to the indirect path.
As a sub-embodiment of this embodiment, all SRBs and all DRBs of the first node are transmitted using a direct path before the first signaling is received.
As a sub-embodiment of this embodiment, at least all SRBs and all DRBs of the first node other than SRB0 are transmitted using a direct path before the first signaling is received.
As a sub-embodiment of this embodiment, at least all SRBs and all DRBs of the first node other than SRB0 are associated with an RLC bearer or RLC entity of the Uu interface before the first signaling is received.
As a sub-embodiment of this embodiment, at least all SRBs and all DRBs of the first node other than SRB0 are not associated with an RLC bearer or RLC entity of the PC5 interface before the first signaling is received.
As a sub-embodiment of this embodiment, after completing the transition from direct to the indirect path, all SRBs and all DRBs of the first node, except at least SRB0, are associated with RLC bearers or RLC entities of the PC5 interface, and all SRBs and all DRBs of the first node, except at least SRB0, are no longer associated with RLC bearers or RLC entities of the Uu interface.
As a sub-embodiment of this embodiment, after completing the transition from direct to the indirect path, all SRBs and all DRBs of the first node are associated with RLC bearers or RLC entities of the PC5 interface, and all SRBs and all DRBs of the first node are no longer associated with RLC bearers or RLC entities of the Uu interface.
As a sub-embodiment of this embodiment, the first signaling instructs the first node to release all Uu interface RLC entities or RLC bearers associated with SRBs and DRBs.
As a sub-embodiment of this embodiment, the first signaling indicates that at least SRBs other than SRB0 and all DRBs of the first node are associated to a PC5 interface RLC entity or RLC bearer.
As a sub-embodiment of this embodiment, the first signaling indicates that at least SRBs other than SRB0 and all DRBs of the first node are no longer associated with any Uu interface RLC entity or RLC bearer.
As an embodiment, the SRB in the present application is a radio bearer of the Uu interface, the DRB in the present application is a radio bearer of the Uu interface, i.e. the SRB in the present application is not a sidelink SRB; the DRB is not a sidelink DRB.
As an embodiment, the second signaling is or includes rrcrecon configuration complete.
As an embodiment, the second signaling indicates that the configuration of the first signaling was completed successfully.
As an embodiment, the second signaling is used to confirm completion of the conversion from the indirect path to the direct path.
As an embodiment, the first set of operations includes evaluating whether a condition required for the first signaling to be performed is satisfied.
As one embodiment, the first set of operations includes executing Reconfiguration with sync.
As one embodiment, the first set of operations includes stopping T310 the timer.
As one embodiment, the first set of operations includes stopping T312 the timer.
As one embodiment, the first set of operations includes starting a T304 timer.
As one embodiment, the first set of operations includes starting a timer associated with transitioning from a direct path to an indirect path.
As one embodiment, the first set of operations includes starting a T304a timer.
As one embodiment, the first set of operations includes starting a T304b timer.
For one embodiment, the first set of operations includes starting a T314 timer.
For one embodiment, the first set of operations includes starting a T324 timer.
As one embodiment, the first set of operations includes starting a T305 timer.
As one embodiment, the first set of operations includes starting a T306 timer.
The first set of operations includes, as one embodiment, starting a T334 timer.
As an embodiment, at least part of the operations of the first set of operations are performed with execution of signaling indicated by the first domain of the first signaling.
As an embodiment, at least part of the operations in the first set of operations are triggered to be performed by the execution of signaling indicated by the first domain of the first signaling.
As an embodiment, the first set of operations includes synchronizing with a SpCell indicated by the first signaling.
As an embodiment, the first set of operations includes applying a BCCH configuration of the SpCell indicated by the first signaling.
As an embodiment, the first signaling explicitly indicates that the first set of operations includes the first timer.
As an embodiment, the first signaling implicitly indicates that the first set of operations includes the first timer.
As an embodiment, the first field is used to indicate whether the first set of operations includes stopping the first timer.
As an embodiment, the first set of operations does not comprise stopping the first timer means that the first timer is not stopped when the first signaling is performed.
As an embodiment, the meaning of the sentence of the first signaling used to indicate whether the first set of operations includes stopping the first timer is: there is at least one case, the first set of operations includes stopping the first timer and there is at least one other case, the first set of operations does not include stopping the first timer.
As an embodiment, the meaning of the sentence of the first signaling used to indicate whether the first set of operations includes stopping the first timer is: there is at least one case, the first signaling is used to indicate that the first set of operations includes stopping the first timer and there is at least one other case, the first signaling is used to indicate that the first set of operations does not include stopping the first timer.
As an embodiment, the first signaling occupies sidelink resources.
As a sub-embodiment of this embodiment, the first node receives a first MAC PDU on the sidelink, the first MAC PDU carrying the first signaling.
As an embodiment, the first signaling uses SRB.
As an embodiment, the first signaling uses DCCH.
As an embodiment, the first signaling does not use a sidelink SRB.
As an embodiment, the physical channel occupied by the first signaling comprises one of a PSCCH or a PSSCH.
As one embodiment, the format of the first signaling is used to determine whether the first set of operations includes stopping the first timer; the format of the first signaling is one candidate format in a candidate format set, the candidate format set comprising at least two candidate formats, a first format and a second format; any two candidate formats in the candidate format set are two RRC IEs with different names, or any two candidate formats in the candidate format set are two domains with different names; the first set of operations includes stopping the first timer when the format of the first signaling is the first format, and the first set of operations does not include stopping the first timer when the format of the first signaling is the second format.
As a sub-embodiment of the above embodiment, excluding stopping the first timer means that the first timer is not stopped when the first signaling is performed.
As an embodiment, the meaning of a sentence when the format of the first signaling is the first format is that the first signaling includes an RRC IE (Information Element) corresponding to the first format.
As a sub-embodiment of this embodiment, the first signaling does not include a format other than the first format in the set of candidate formats.
As a sub-embodiment of this embodiment, the first signaling does not include the second format of the set of candidate formats.
As an embodiment, the first format is SpCellConfig, and the second format is a candidate format other than SpCellConfig.
As an embodiment, the first format is spcellconfigdodedited and the second format is a candidate format other than spcellconfigdodedited.
As an embodiment, the first format is ServCellIndex, and the second format is a candidate format other than ServCellIndex.
As an embodiment, the first format is spCellConfigCommon and the second format is a candidate format other than spCellConfigCommon.
As an embodiment, the first format is newUE-Identity and the second format is a candidate format other than newUE-Identity.
As an embodiment, the first format is a physiocellid and the second format is a candidate format other than the physiocellid.
As one example, the first format is a physical cellgroupconfig, and the second format is a candidate format other than a physical cellgroupconfig.
As one embodiment, the first format is mac-CellGroupConfig and the second format is a candidate format other than mac-CellGroupConfig.
As an embodiment, the first format is a dedication sib1-Delivery, and the second format is a candidate format other than the dedication sib 1-Delivery.
As one embodiment, the first format is a masterKeyUpdate and the second format is a candidate format other than masterKeyUpdate.
As an embodiment, the first format is a dedication systemiformationdelivery, and the second format is a candidate format other than the dedication systemiformationdelivery.
As an embodiment, the first format is MAC Cell Group configuration and the second format is a candidate format other than MAC Cell Group configuration.
As an embodiment, the first signaling comprises only one candidate format of the set of candidate formats.
As an embodiment, when the first signaling includes the first format, the first signaling does not include the second format; when the first signaling includes a second format, the first signaling does not include the first signaling.
As an embodiment, the meaning that the format of the first signaling is the first format is that the first signaling includes an RRC IE named the first format.
As an embodiment, the meaning that the format of the first signaling is the second format is that the first signaling includes an RRC IE named the second format.
As an embodiment, when the first set of operations of the first signaling is used to indicate that the first set of operations includes stopping the first timer, the primary cell of the first node remains unchanged before the first signaling is performed and after the first signaling is performed; when the first set of operations of the first signaling is used to indicate that the first set of operations does not include stopping the first timer, a primary cell of the first node changes before and after the first signaling is performed.
As an embodiment, when the SpCell indicated by the first signaling is unchanged or is not indicated to be changed, the first set of operations does not include stopping the first timer; when the SpCell indicated by the first signaling changes, the first set of operations includes stopping the first timer.
As a sub-embodiment of this embodiment, the first signaling includes a servCellIndex in SpCellConfig equal to 0.
As a sub-embodiment of this embodiment, the meaning of the phrase that the SpCell indicated by the first signaling has not been changed is: before and after performing the first signaling, the SpCell of the first node is unchanged.
As a sub-embodiment of this embodiment, the phrase that the first signaling does not indicate that the SpCell is changed means that: after performing the first signaling, the SpCell of the first node is unchanged from before the first signaling was performed.
As a sub-embodiment of this embodiment, the meaning of the change in SpCell indicated by the phrase first signaling is or includes: after performing the first signaling, the SpCell of the first node changes compared to before performing the first signaling.
As a sub-embodiment of this embodiment, the meaning of the change in SpCell indicated by the phrase first signaling is or includes: the SpCell indicated by the first signaling is different from the SpCell of the first node prior to performing the first signaling.
As a sub-embodiment of this embodiment, the physiocellid in ServingCellConfigCommon in reconfiguration wisync included in the first signaling is used to determine whether the SpCell indicated by the first signaling has changed.
As a sub-embodiment of this embodiment, the change of the physiocellid in the ServingCellConfigCommon in the reconfiguration wisync included in the first signaling means that the SpCell indicated by the first signaling changes.
As a sub-embodiment of this embodiment, the second signaling includes a specific signaling, and the specific signaling includes a specific signaling.
As a sub-embodiment of this embodiment, the cellaccessrelateinfo included in the first signaling does not change, which means that the SpCell indicated by the first signaling does not change; the change of the cellaccessrelateinfo included in the first signaling means that the SpCell indicated by the first signaling is changed.
As a sub-embodiment of this embodiment, the PLMN-identity info list included in the first signaling does not change, which means that the SpCell indicated by the first signaling does not change; a change in PLMN-identity info list included in the first signaling means that the SpCell indicated by the first signaling is changed.
As a sub-embodiment of this embodiment, the cellIdentity included in the first signaling does not change, which means that the SpCell indicated by the first signaling does not change; the change of the cellIdentity included in the first signaling means that the SpCell indicated by the first signaling is changed.
As a sub-embodiment of this embodiment, the cellIdentity in the PLMN-identity infoist in the cellaccessrelationship info included in the first signaling does not change, which means that the SpCell indicated by the first signaling does not change; the change of cellIdentity in PLMN-identity info list in cellaccessrelationship info included in the first signaling means that the SpCell indicated by the first signaling is changed.
As a sub-embodiment of this embodiment, the uac-barrennifo included in the first signaling does not change, which means that the SpCell indicated by the first signaling does not change; a change in uac-barrennifo included in the first signaling means that the SpCell indicated by the first signaling is changed.
As an embodiment, when the first signaling includes a dedication sib1-Delivery, the first set of operations includes stopping the first timer.
As an embodiment, when the first signaling does not include a dedication sib 1-delay, the first set of operations does not include stopping the first timer.
As an embodiment, when the first signaling includes a dedication sib1-Delivery, the first set of operations includes stopping the first timer.
As an embodiment, when the first signaling does not include uac-barrennifo, the first set of operations does not include stopping the first timer.
As an embodiment, when the first signaling comprises uac-barrennifo, the first set of operations comprises stopping the first timer.
Example 2
Embodiment 2 illustrates a schematic diagram of a network architecture according to one embodiment of the present application, as shown in fig. 2. Fig. 2 illustrates V2X communication architecture under 5G NR (new radio, new air interface), LTE (Long-Term Evolution) and LTE-a (Long-Term Evolution Advanced, enhanced Long-Term Evolution) system architecture. The 5G NR or LTE network architecture may be referred to as 5GS (5 GSystem)/EPS (Evolved Packet System ) some other suitable terminology.
The V2X communication architecture of embodiment 2 includes UE (User Equipment) 201, UE241, ng-RAN (next generation radio access network) 202,5GC (5G Core Network)/EPC (Evolved Packet Core, evolved packet core) 210, hss (Home Subscriber Server )/UDM (Unified Data Management, unified data management) 220, proSe function 250, and ProSe application server 230. The V2X communication architecture may be interconnected with other access networks, but these entities/interfaces are not shown for simplicity. As shown, the V2X communication architecture provides packet-switched services, however, those skilled in the art will readily appreciate that the various concepts presented throughout this application may be extended to networks providing circuit-switched services or other cellular networks. The NG-RAN includes NR node bs (gnbs) 203 and other gnbs 204. The gNB203 provides user and control plane protocol termination towards the UE 201. The gNB203 may be connected to other gnbs 204 via an Xn interface (e.g., backhaul). The gNB203 may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a Basic Service Set (BSS), an Extended Service Set (ESS), a TRP (transmit receive node), or some other suitable terminology. The gNB203 provides the UE201 with an access point to the 5GC/EPC210. Examples of UE201 include a cellular telephone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a Personal Digital Assistant (PDA), a satellite radio, a non-terrestrial base station communication, a satellite mobile communication, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, an drone, an aircraft, a narrowband internet of things device, a machine-type communication device, a land-based vehicle, an automobile, a wearable device, or any other similar functional device. Those of skill in the art may also refer to the UE201 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. gNB203 is connected to 5GC/EPC210 through an S1/NG interface. The 5GC/EPC210 includes MME (Mobility Management Entity )/AMF (Authentication Management Field, authentication management domain)/SMF (Session Management Function ) 211, other MME/AMF/SMF214, S-GW (Service Gateway)/UPF (userplaneflection) 212, and P-GW (Packet Date Network Gateway, packet data network Gateway)/UPF 213. The MME/AMF/SMF211 is a control node that handles signaling between the UE201 and the 5GC/EPC210. In general, the MME/AMF/SMF211 provides bearer and connection management. All user IP (Internet Protocal, internet protocol) packets are transported through the S-GW/UPF212, which S-GW/UPF212 itself is connected to the P-GW/UPF213. The P-GW provides UEIP address allocation as well as other functions. The P-GW/UPF213 is connected to the internet service 230. Internet services 230 include operator-corresponding internet protocol services, which may include, in particular, the internet, intranets, IMS (IP Multimedia Subsystem ) and packet-switched streaming services. The ProSe function 250 is a logic function for network related behavior required for a ProSe (Proximity-based Service); including DPF (Direct Provisioning Function, direct provision function), direct discovery name management function (Direct Discovery Name Management Function), EPC level discovery ProSe function (EPC-level Discovery ProSe Function), and the like. The ProSe application server 230 has the functions of storing EPC ProSe user identities, mapping between application layer user identities and EPC ProSe user identities, allocating ProSe-restricted code suffix pools, etc.
As an embodiment, the UE201 and the UE241 are connected through a PC5 Reference Point (Reference Point).
As an embodiment, the ProSe function 250 is connected to the UE201 and the UE241 through PC3 reference points, respectively.
As an embodiment, the ProSe function 250 is connected to the ProSe application server 230 via a PC2 reference point.
As an embodiment, the ProSe application server 230 is connected to the ProSe application of the UE201 and the ProSe application of the UE241 via PC1 reference points, respectively.
As an embodiment, the first node in the present application is UE201.
As one embodiment, the second node in this application is the gNB203.
As an embodiment, the third node in the present application is UE241.
As an embodiment, the radio link between the UE201 and the UE241 corresponds to a Sidelink (SL) in the present application.
As an embodiment, the radio link from the UE201 to the NR node B is an uplink.
As an embodiment, the radio link from the NR node B to the UE201 is a downlink.
As an embodiment, the radio link from the UE241 to the NR node B is an uplink.
As one embodiment, the radio link from NR node B to UE241 is a downlink.
As an embodiment, the UE201 supports relay transmission.
As an embodiment, the UE241 supports relay transmission.
As an embodiment, the UE201 includes a mobile phone.
As an embodiment, the UE241 includes a mobile phone.
As one example, the UE201 is a vehicle including an automobile.
As one example, the UE241 is a vehicle including an automobile.
As an embodiment, the gNB203 is a macro cell (marcocelluar) base station.
As one example, the gNB203 is a Micro Cell (Micro Cell) base station.
As an embodiment, the gNB203 is a PicoCell (PicoCell) base station.
As an embodiment, the gNB203 is a flying platform device.
As one embodiment, the gNB203 is a satellite device.
Example 3
Embodiment 3 shows a schematic diagram of an embodiment of a radio protocol architecture according to one user plane and control plane of the present application, as shown in fig. 3. Fig. 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300, fig. 3 shows the radio protocol architecture for the control plane 300 for a first node (UE, satellite or aerial in gNB or NTN) and a second node (gNB, satellite or aerial in UE or NTN), or between two UEs, in three layers: layer 1, layer 2 and layer 3. Layer 1 (L1 layer) is the lowest layer and implements various PHY (physical layer) signal processing functions. The L1 layer will be referred to herein as PHY301. Layer 2 (L2 layer) 305 is above PHY301 and is responsible for the links 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, radio link layer control protocol) sublayer 303, and a PDCP (Packet Data Convergence Protocol ) sublayer 304, which terminate at the second node. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by ciphering the data packets and handover support for the first node between second nodes. 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 the various radio resources (e.g., resource blocks) in one cell among the first nodes. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control ) sublayer 306 in layer 3 (L3 layer) in the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring the lower layers using RRC signaling between the second node and the first node. The PC5-S (PC 5 Signaling Protocol ) sublayer 307 is responsible for the processing of 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 for the physical layer 351, PDCP sublayer 354 in the L2 layer 355, RLC sublayer 353 in the L2 layer 355 and MAC sublayer 352 in the L2 layer 355 as the corresponding layers and sublayers in the control plane 300, but the PDCP sublayer 354 also provides header compression for upper layer packets to reduce radio transmission overhead. Also included in the L2 layer 355 in the user plane 350 is an SDAP (Service Data Adaptation Protocol ) sublayer 356, the SDAP sublayer 356 being responsible for mapping between QoS flows and data radio bearers (DRBs, data Radio Bearer) to support diversity of traffic. Although not shown, the first node may have several upper layers above the L2 layer 355. Further included are a network layer (e.g., IP layer) terminating at the P-GW on the network side and an application layer terminating at the other end of the connection (e.g., remote UE, server, etc.). For UEs involving relay services, the control plane may also include an adaptation sublayer AP308, and the user plane may also include an adaptation sublayer AP358, where the introduction of the adaptation layer may facilitate multiplexing and/or distinguishing data from multiple source UEs by lower layers, such as the MAC layer, e.g., the RLC layer, and may or may not include an adaptation sublayer for UE-to-UE communications involving relay services. In addition, the adaptation sublayers AP308 and AP358 may also be sublayers within PDCP304 and PDCP354, respectively. The RRC306 may be used to handle RRC signaling for Uu interface and signaling for PC5 interface.
As an embodiment, the radio protocol architecture in fig. 3 is applicable to the first node in the present application.
As an embodiment, the radio protocol architecture in fig. 3 is applicable to the second node in the present application.
As an embodiment, the radio protocol architecture in fig. 3 is applicable to the third node in the present application.
As an embodiment, the first signaling in the present application is generated in RRC306.
As an embodiment, the second signaling in the present application is generated in RRC306.
As an embodiment, the third signaling in the present application is generated in RRC306 or MAC302.
As an embodiment, the first conditional reconfiguration in the present application is generated in RRC306.
Example 4
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 fig. 4. Fig. 4 is a block diagram of a first communication device 450 and a second communication device 410 communicating with each other in an access network.
The first communication device 450 includes a controller/processor 459, a memory 460, a data source 467, a transmit processor 468, a receive processor 456, a multi-antenna transmit processor 457, a multi-antenna receive processor 458, a transmitter/receiver 454, and an antenna 452.
The second communication device 410 includes a controller/processor 475, a memory 476, a receive processor 470, a transmit processor 416, a multi-antenna receive processor 472, a multi-antenna transmit processor 471, a transmitter/receiver 418, and an antenna 420.
In the transmission from the second communication device 410 to the first communication device 450, upper layer data packets from the core network are provided to a controller/processor 475 at the second communication device 410. 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, a 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 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., physical layer). Transmit processor 416 performs coding and interleaving to facilitate Forward Error Correction (FEC) at the second communication device 410, as well as mapping of signal clusters 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 digitally space-precodes the coded and modulated symbols, including codebook-based precoding and non-codebook-based precoding, and beamforming processing, to generate one or more spatial streams. A transmit processor 416 then maps each spatial stream to a subcarrier, multiplexes with reference signals (e.g., pilots) in the time and/or frequency domain, and then uses an Inverse Fast Fourier Transform (IFFT) to generate a physical channel carrying the time domain multicarrier symbol stream. The multi-antenna transmit processor 471 then performs transmit analog precoding/beamforming operations on the time domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multicarrier symbol stream provided by the multiple antenna transmit processor 471 to a radio frequency stream and then provides it to a different antenna 420.
In a transmission from the second communication device 410 to the first communication device 450, each receiver 454 receives a signal at the first communication device 450 through its respective antenna 452. Each receiver 454 recovers information modulated onto a radio frequency carrier and converts the radio frequency stream into a baseband multicarrier symbol stream that is provided to a receive processor 456. The receive processor 456 and the multi-antenna receive processor 458 implement various signal processing functions for the L1 layer. A multi-antenna receive processor 458 performs receive analog precoding/beamforming operations on the baseband multi-carrier symbol stream from the receiver 454. The receive processor 456 converts the baseband multicarrier symbol stream after receiving the analog precoding/beamforming operation from the time domain to the frequency domain using a Fast Fourier Transform (FFT). In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receive processor 456, wherein the reference signal is to be used for channel estimation, and the data signal is subjected to multi-antenna detection in the multi-antenna receive processor 458 to recover any spatial stream destined for the first communication device 450. The symbols on each spatial stream are demodulated and recovered in a receive processor 456 and soft decisions are generated. The receive processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals that were 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. 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 demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover upper layer data packets from the core network. The upper layer packets are then provided to all protocol layers above the L2 layer. Various control signals may also be provided to L3 for L3 processing.
In the transmission from the first communication device 450 to the second communication device 410, a data source 467 is used at the first communication device 450 to provide upper layer data packets to a controller/processor 459. Data source 467 represents all protocol layers above the L2 layer. Similar to the transmit functions 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 allocations, implementing L2 layer functions for the user and control planes. The controller/processor 459 is also responsible for retransmission of lost packets and signaling to the second communication device 410. The transmit processor 468 performs modulation mapping, channel coding, and digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming, with the multi-antenna transmit processor 457 performing digital multi-antenna spatial precoding, after which the transmit processor 468 modulates the resulting spatial stream into a multi-carrier/single-carrier symbol stream, which is analog precoded/beamformed in the multi-antenna transmit processor 457 before being provided to the different antennas 452 via the transmitter 454. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a radio frequency symbol stream and provides it to an antenna 452.
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 receiving 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 radio frequency signals through its corresponding antenna 420, converts the received radio frequency signals to baseband signals, and provides the baseband signals to a multi-antenna receive processor 472 and a receive processor 470. The receive processor 470 and the multi-antenna receive processor 472 collectively implement the functions of the L1 layer. The controller/processor 475 implements L2 layer functions. The controller/processor 475 may be associated with a memory 476 that stores program codes and data. Memory 476 may be referred to as a computer-readable medium. In the transmission from the first communication device 450 to the second communication device 410, a controller/processor 475 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover upper layer data packets from the UE 450. Upper layer packets from the controller/processor 475 may be provided to the core network.
As an embodiment, the first communication device 450 apparatus includes: at least one processor and at least one memory including computer program code; the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus of the first communication device 450 to at least: starting a first timer, the first timer being used for access barring;
receiving first signaling, the first signaling being used to configure an MCG, the first signaling comprising a first domain; in response to receiving the first signaling, performing a first set of operations; wherein the first domain is a reconfigurationWithSync, and the first operation set includes sending a second signaling for confirming that configuration of at least the first signaling is successfully completed; the first signaling is used to indicate whether the first set of operations includes stopping the first timer.
As an embodiment, the first communication device 450 includes: a memory storing a program of computer-readable instructions that, when executed by at least one processor, produce acts comprising: starting a first timer, the first timer being used for access barring; receiving first signaling, the first signaling being used to configure an MCG, the first signaling comprising a first domain; in response to receiving the first signaling, performing a first set of operations; wherein the first domain is a reconfigurationWithSync, and the first operation set includes sending a second signaling for confirming that configuration of at least the first signaling is successfully completed; the first signaling is used to indicate whether the first set of operations includes stopping the first timer.
As an embodiment, the second communication device 410 apparatus includes: at least one processor and at least one memory including computer program code; the at least one memory and the computer program code are configured for use with the at least one processor. The second communication device 410 means at least: transmitting first signaling, the first signaling being used to configure an MCG, the first signaling comprising a first domain; wherein the receiving of the first signaling is used to trigger execution of a first set of operations; the first domain is a reconfigurationWithSync, and the first operation set includes sending second signaling for confirming that configuration of at least the first signaling is successfully completed; the first signaling is used to indicate whether the first set of operations includes stopping a first timer, the first timer being used for access barring.
As an embodiment, the second communication device 410 apparatus includes: a memory storing a program of computer-readable instructions that, when executed by at least one processor, produce acts comprising: transmitting first signaling, the first signaling being used to configure an MCG, the first signaling comprising a first domain; wherein the receiving of the first signaling is used to trigger execution of a first set of operations; the first domain is a reconfigurationWithSync, and the first operation set includes sending second signaling for confirming that configuration of at least the first signaling is successfully completed; the first signaling is used to indicate whether the first set of operations includes stopping a first timer, the first timer being used for access barring.
As an embodiment, the first communication device 450 corresponds to a first node in the present application.
As an embodiment, the second communication device 410 corresponds to a second node in the present application.
As an embodiment, the first communication device 450 corresponds to a third node in the present application.
As an embodiment, the first communication device 450 is a UE.
As an embodiment, the first communication device 450 is an in-vehicle terminal.
As an embodiment, the first communication device 450 is a mobile phone.
As an embodiment, the first communication device 450 is a relay.
As an embodiment, the second communication device 410 is a base station.
As an example, a receiver 456 (including an antenna 460), a receive processor 452 and a controller/processor 490 are used for receiving the first signaling in the present application.
As an example, a receiver 456 (including an antenna 460), a receive processor 452 and a controller/processor 490 are used for receiving the third signaling in the present application.
As an example, the receiver 456 (including the antenna 460), the receiving processor 452 and the controller/processor 490 are used in the present application to receive said first conditional reconfiguration.
As an example, a transmitter 456 (including an antenna 460), a transmit processor 455 and a controller/processor 490 are used in the present application to transmit the random access signal in the first random access procedure.
As an example, a transmitter 456 (including an antenna 460), a transmit processor 455 and a controller/processor 490 are used to send the second signaling in this application.
As one example, transmitter 416 (including antenna 420), transmit processor 412 and controller/processor 440 are used to send the first signaling in this application.
As one example, transmitter 416 (including antenna 420), transmit processor 412 and controller/processor 440 are used to send the second signaling in this application.
As one example, transmitter 416 (including antenna 420), transmit processor 412 and controller/processor 440 are used to send the third signaling in this application.
As one example, transmitter 416 (including antenna 420), transmit processor 412 and controller/processor 440 are used to send the first conditional reconfiguration in this application.
As one example, transmitter 416 (including antenna 420), transmit processor 412 and controller/processor 440 are used in this application
As an embodiment, the receiver 416 (including the antenna 420), the receiving processor 412 and the controller/processor 440 are used for receiving the random access signal in the first random access procedure in the present application.
As an embodiment, the receiver 416 (including the antenna 420), the receiving processor 412 and the controller/processor 440 are used for receiving said second signaling in the present application.
Example 5
Embodiment 5 illustrates a wireless signal transmission flow diagram according to one embodiment of the present application, as shown in fig. 5. In fig. 5, U01 corresponds to a first node of the present application, U02 corresponds to a second node of the present application, and U03 is a relay node, which specifically illustrates that the order in this example is not limited to the signal transmission order and the order of implementation in the present application, where the steps in F51 are optional, and step S5102 is also optional.
For the followingFirst node U01Receiving a first signaling in step S5101; initiating a first random access procedure in step S5102; transmitting a second signaling in step S5103; the third signaling is received in step S5104.
For the followingSecond node U02Transmitting a first signaling in step S5201; receiving a second signaling in step S5202; the third signaling is sent in step S5203.
For the followingThird node U03The first signaling is forwarded in step S5301.
In embodiment 5, the first node U01 starts a first timer, which is used for access barring; the first signaling is used to configure the MCG, the first signaling including a first domain; the first node U01, in response to receiving the first signaling, performs a first set of operations;
wherein the first domain is a reconfigurationWithSync, and the first operation set includes sending a second signaling for confirming that configuration of at least the first signaling is successfully completed; the first signaling is used to indicate whether the first set of operations includes stopping the first timer.
As an embodiment, the first node U01 is a U2N relay UE.
As an embodiment, the first node U01 is a U2N remote UE.
As an embodiment, the first node U01 is an nrproseu2N remote UE.
As an embodiment, the third node U03 is a UE.
As an embodiment, the third node U03 is a U2N relay of the first node U01.
As an embodiment, the third node U03 is a layer 2 relay of the first node U01.
As an embodiment, the third node U03 is an nrproseu2N relay.
As an embodiment, the third node U03 is a U2N relay UE.
As an embodiment, the third node U03 provides an L2U2N relay service to the first node U01.
As an embodiment, the second node U02 is a serving cell of the first node U01.
As an embodiment, the second node U02 is a primary cell of the first node U01.
As an embodiment, the second node U02 is a master cell group of the first node U01.
As an embodiment, the second node U02 is a base station corresponding to or belonging to the primary cell of the first node U01.
As an embodiment, the second node U02 is a base station corresponding to or belonging to the primary cell of the third node U03.
As an embodiment, the second node U02 is a serving cell of the third node U03.
As an embodiment, the second node U02 is a primary cell of the third node U03.
As an embodiment, the second node U02 is a master cell group of the third node U03.
As an embodiment, the second node U02 is a base station corresponding to or belonging to the primary cell of the third node U03.
As an embodiment, the first node U01 and the third node U03 have the same primary cell (PCell).
As an embodiment, an RRC connection exists between the first node U01 and the third node U03.
As an embodiment, a PC5 connection exists between the first node U01 and the third node U03.
As an embodiment, an RRC connection exists between the third node U03 and the second node U02.
As an embodiment, an RRC connection exists between the first node U01 and the second node U02.
As an embodiment, the third node U03 applies the system message of the second node U02.
As an embodiment, the first node U01 applies the system message forwarded by the third node U03.
As an embodiment, the first node U01 applies the system message of the second node U02 forwarded by the third node U03.
As an embodiment, the first node U01 communicates with the second node U02 via an indirect path before receiving the first signaling.
As an embodiment, the first node U01 communicates with the third node U03 through a sidelink.
As an embodiment, the first node U01 establishes a direct link with the third node U03.
As an embodiment, the first signaling is sent to the first node U01 by forwarding by the third node U03.
As a sub-embodiment of this embodiment, the forwarding is L2 forwarding.
As a sub-embodiment of this embodiment, the third node U03 does not change PDCP PDUs carrying the first signaling while forwarding the first signaling.
As an embodiment, the communication interface between the second node U02 and the third node U03 is a Uu interface.
As an embodiment, the communication interface between the first node U01 and the third node U03 is a PC5 interface.
As an embodiment, the transmission of the first signaling comprises at least a sidelink.
As an embodiment, the first signaling is performed immediately after being received.
As an embodiment, the first signaling is performed after being received for a delay period of time.
As an embodiment, the first signaling is performed when a certain condition is met after being received.
As an embodiment, the first node U01 starts a second timer in response to performing the first signaling; initiating a first random access procedure for the cell indicated by the first signaling, a successful completion of the first random access procedure being used to stop the second timer;
Wherein expiration of the second timer is used to trigger RRC reestablishment.
As a sub-embodiment of this embodiment, the second timer is or includes T304.
As a sub-embodiment of this embodiment, the second timer is or includes T305.
As a sub-embodiment of this embodiment, the second timer is or includes T306.
As a sub-embodiment of this embodiment, the second timer is or includes T314.
As a sub-embodiment of this embodiment, the second timer is or includes T334.
As a sub-embodiment of this embodiment, the second timer is or includes T304a.
As a sub-embodiment of this embodiment, the second timer is or includes T304b.
As a sub-embodiment of this embodiment, the first random access procedure comprises CFRA (contention free random access ).
As a sub-embodiment of this embodiment, the first random access procedure comprises CBRA (contention based random access, contention free random access).
As a sub-embodiment of this embodiment, the cell indicated by the first signaling is a cell indicated by a spCellConfig included in the first signaling.
As a sub-embodiment of this embodiment, the cell indicated by the first signaling is a cell indicated by a reconfigurationwisync included in the first signaling.
As a sub-embodiment of this embodiment, the cell indicated by the first signaling is a cell indicated by a servingcellconfiguration common in a reconfiguration wisync included in the first signaling.
As a sub-embodiment of this embodiment, the first random access procedure is indicated by the rach-ConfigDedicated in the reconfigurationWithSync of the first signaling.
As a sub-embodiment of this embodiment, the sentence meaning of initiating the first random access procedure for the cell indicated by the first signaling comprises: and transmitting the random access signal in the first random access process on the random access resource of the cell indicated by the first signaling.
As a sub-embodiment of this embodiment, the sentence meaning of initiating the first random access procedure for the cell indicated by the first signaling comprises: and selecting random access resources used by the first random access process according to the random access resources of the cell indicated by the first signaling.
As a sub-embodiment of this embodiment, the sentence meaning of initiating the first random access procedure for the cell indicated by the first signaling comprises: and synchronizing with the cell indicated by the first signaling.
As a sub-embodiment of this embodiment, the sentence meaning of initiating the first random access procedure for the cell indicated by the first signaling comprises: and initiating a random access procedure on the frequency or part of the frequency of the cell indicated by the first signaling.
As a sub-embodiment of this embodiment, the cell indicated by the first signaling is a PCell.
As a sub-embodiment of this embodiment, the cell indicated by the first signaling is a SpCell.
As a sub-embodiment of this embodiment, the first node stops the second timer when the first random access procedure is successfully completed.
As a sub-embodiment of this embodiment, when the second timer expires, the first node initiates an RRC reestablishment comprising sending an RRCReestablishmentRequest message.
As an embodiment, the first conditional reconfiguration comprises said first signaling.
As a sub-embodiment of this embodiment, the first conditional reconfiguration is a conditional reconfiguration in an rrcrecon configuration message.
As a sub-embodiment of this embodiment, the first signaling is condrrcrecon included in one condreconfigtoadmodlist in the condreconfigtoadmodlist included in the first conditional reconfiguration.
As a sub-embodiment of this embodiment, the first condition is condexecu-nd included in one condreconfigtoadmodlist included in the first condition reconfiguration.
As a sub-embodiment of this embodiment, the first set of operations includes stopping the first timer.
As a sub-embodiment of this embodiment, the first signaling is used to configure a conditional handover (CHO, conditional handover).
As an embodiment, the second signaling uses SRB1.
As an embodiment, the second signaling is sent over the direct path.
As an embodiment, the second signaling does not pass through the relay of the third node U03.
As an embodiment, the second signaling is transmitted without using a sidelink.
As an embodiment, the first node U01, after step S5103, receives third signaling, which is used to instruct to switch from a direct path to an indirect path;
The first node U01 performs the third signaling; stopping the first timer in response to performing the third signaling;
wherein the indirect path is that data transmission between the first node and a network is forwarded through a relay; the direct path is that data transmission between the first node and the network does not pass through a relay.
As an embodiment, the third signaling includes reconfigurationWithSync.
As an embodiment, the third signaling does not include reconfigurationWithSync.
As an embodiment, the third signaling is rrcrecon configuration.
As an embodiment, the third signaling is sent and received using a direct path.
As an embodiment, the third signaling uses SRB.
As an embodiment, the third signaling reception is performed, and the sentence as a response to performing the third signaling is equal to as a response to receiving the third signaling.
For one embodiment, the phrase converting from a direct path to an indirect path includes: SRBs other than SRB0 are associated with RLC entities or RLC bearers of the PC5 interface while ceasing to be associated with RLC entities or RLC bearers of the Uu interface.
For one embodiment, the phrase converting from a direct path to an indirect path includes: all DRBs are associated with the RLC entity or RLC bearer of the PC5 interface while ceasing to be associated with the RLC entity or RLC bearer of the Uu interface.
For one embodiment, the phrase converting from a direct path to an indirect path includes: the added new DRB is associated with the RLC entity or RLC bearer of the PC5 interface and not with the RLC entity or RLC bearer of the Uu interface.
As an embodiment, the indirect path indicated by the third signaling is a transmission path through the third node U03.
As an embodiment, the indirect path indicated by the third signaling is a transmission path relayed through L2U2N, and the PCell relayed by L2U2N is the second node U02 or a cell of the second node U02.
As an embodiment, the indirect path indicated by the third signaling is a transmission path relayed through L2U2N, and the PCell relayed by L2U2N is not the second node U02.
As an embodiment, the indirect path indicated by the third signaling is a transmission path relayed through L2U2N, and the PCell of the L2U2N relay is the same as the PCell of the first node U01.
As an embodiment, the indirect path indicated by the third signaling is a transmission path relayed through L2U2N, and the PCell of the L2U2N relay is different from the PCell of the first node U01.
Example 6
Embodiment 6 illustrates a schematic diagram of an RRC message according to an embodiment of the present application, as shown in fig. 6.
Field1, field2, field11, field12, field21 in FIG. 6 are all domains.
The format of the RRC message is based on the relevant specifications of the iso sn.1.
Information element1, information element2, information element11, and information element12 in fig. 6 are all RRC IEs.
For one embodiment, an RRC message includes one or more RRC IEs (information elements), such as RRCMessage-IEs in FIG. 6.
As an example, the RRCMessage-IEs in fig. 6 is an RRC IE.
As an example, the RRCMessage-IEs in fig. 6 are any IEs of an RRC message.
As an example, an RRC IE includes one or more fields, such as field1 and field2 included in the RRCMessage-IEs of fig. 6, such as Information.
As an example, the domain in fig. 6 is applicable to the first domain of the present application.
As an example, the domain in fig. 6 is applicable to the second domain of the present application.
As an example, the value of a field in the RRC message may be an RRC IE, for example, field1 in fig. 6 is information element1.
As an example, one field in the RRC message carries or carries one RRC IE, for example, field1 carries or carries information element1 in fig. 6.
As an example, one field in the RRC message corresponds to one RRC IE, for example, field1 corresponds to information element1 in fig. 6.
As an embodiment, in the RRC message, different fields may correspond to, carry, or take the same value of the RRC IE, e.g. field11 and field21 are both set to information element11.
As an embodiment, the IE in the RRC message may include one or more levels.
For one embodiment, the IE in the RRC message may include one or more sub-IEs.
For one embodiment, the IE in the RRC message may include one or more grandchild IEs, and/or a deeper level IE.
As an example, the IE in the RRC message may include one or more sub-fields and/or Sun Yu, e.g., field1 is a sub-item of the RRCMessage-IEs, field11 is Sun Xiang of the RRCMessage-IEs; the sub-fields of the IEs in one RRC message may also include its own sub-field or Sun Yu, and so on.
As an embodiment, the meaning that the phrase the first domain is reconfigurationWithSync includes that the name of the first domain is "reconfigurationWithSync".
As an embodiment, the RRCIE carried or carried by the first domain is ReconfigurationWithSync.
As an embodiment, the first field is a child of the first signaling.
As an embodiment, the first domain is Sun Xiang of the first signaling.
As an embodiment, the first field is a child of Sun Xiang of the first signaling.
As an embodiment, the sub-item of one RRC IE is a first level item included in the one RRC IE.
As an embodiment, the Sun Xiang of one RRC IE is a second level item included in the one RRC IE.
As an embodiment, the sub-item of Sun Xiang of one RRC IE is a third level item included in the one RRC IE.
As one example, the fields in fig. 6 are applicable to the candidate format set of the present application, any format in the candidate format set being a field.
As an example, the domain in fig. 6 is applicable to the first format of the present application, which is a domain.
As an example, the domain in fig. 6 is applicable to the second format of the present application, and the first format is a domain.
As an example, the RRC IE in fig. 6 applies to the candidate format set of the present application, any format in the candidate format set being an RRC IE.
As an example, the RRC IE in fig. 6 is applicable to the first format of the present application, which is an RRC IE.
As an example, the RRC IE in fig. 6 is applicable to the second format of the present application, which is an RRC IE.
Example 7
Embodiment 7 illustrates a schematic diagram of a protocol stack for relaying communications according to one embodiment of the present application, as shown in fig. 7.
The protocol stack shown in fig. 7 is applicable to L2U2N relay communication, and embodiment 7 is based on embodiment 3.
Fig. 7 (a) corresponds to a user plane protocol stack in L2U2N relay communication; fig. 7 (b) corresponds to a control plane protocol stack in L2U2N relay communication.
In embodiment 7, the PC5 interface is an interface between the first node and the first relay, and the PC5 interface-related protocol entity { PC5-ADAPT, PC5-RLC, PC5-MAC, PC5-PHY } terminates at the first node and the first relay; the Uu interface is an interface between the UE and the gNB, and protocol entities of the Uu interface are respectively terminated by the UE and the gNB.
As an embodiment, the first relay is a U2N relay UE, and the first relay provides an L2U2N relay service to the first node before performing the first signaling.
As an embodiment, after performing the first signaling, the first relay no longer provides L2U2N relay services to the first node.
As an embodiment, the first node and the first relay are both UEs.
As an embodiment, the first relay in fig. 7 corresponds to the third node U03 in embodiment 5.
As an embodiment, the gNB in fig. 7 corresponds to the second node of the present application.
As an embodiment, the protocol entity { Uu-ADAPT, uu-RLC, uu-MAC, uu-PHY } of the Uu interface terminates with the first relay and the gNB.
As an embodiment, in (a), the protocol entity { Uu-SDAP, uu-PDCP } of the Uu interface ends with the first node and the gNB, and the SDAP PDU and PDCP PDU of the first node are forwarded by the first relay, but the first relay does not modify the SDAP PDU and PDCP PDU of the first node, that is, the SDAP PDU and PDCP PDU sent by the first node to the gNB are transparent to the first relay.
As an embodiment, in (b), the protocol entity { Uu-RRC, uu-PDCP } of the Uu interface terminates with the first node and the gNB, and the RRC PDU and PDCP PDU of the first node are forwarded by the first relay, but the first relay does not modify the RRC PDU and PDCP PDU sent by the first node, that is, the RRC PDU and PDCP PDU sent by the first node to the gNB are transparent to the first relay.
As an example, in (a), PC5-ADAPT corresponds to AP358 in fig. 3, PC5-RLC corresponds to RLC353 in fig. 3, PC5-MAC corresponds to MAC352 in fig. 3, and PC5-PHY corresponds to PHY351 in fig. 3.
As an example, in (a), uu-SDAP corresponds to SDAP356 in fig. 3, uu-PDCP corresponds to PDCP354 in fig. 3.
As an example, in (b), PC5-ADAPT corresponds to AP308 in fig. 3, PC5-RLC corresponds to RLC303 in fig. 3, PC5-MAC corresponds to MAC302 in fig. 3, and PC5-PHY corresponds to PHY301 in fig. 3.
As an example, in (b), uu-RRC corresponds to RRC306 in fig. 3 and Uu-PDCP corresponds to PDCP304 in fig. 3.
As an example, one cell of the gNB shown in fig. 7 is a serving cell of the first relay, and the first relay is in a non-RRC connected state.
As an example, one cell of the gNB in fig. 7 is the PCell of the first relay, and the first relay is in an RRC connected state.
As an example, one cell of the gNB in fig. 7 is the camping cell of the first relay.
As an example, one cell of the gNB in fig. 7 is a suitable cell of the first relay.
As an example, one cell of the gNB shown in fig. 7 is the cell selected by the first relay.
As an example, one cell of the gNB in fig. 7 is the camping cell of the first node.
As an example, one cell of the gNB in fig. 7 is a suitable cell of the first node.
As an example, one cell of the gNB shown in fig. 7 is the cell selected by the first node.
As one example, PC5-ADAPT is used only for specific RBs or messages or data.
As a sub-embodiment of this embodiment, the PC 5-accept layer is not used when the first relay forwards system information.
As an example, in fig. 7, the communication between the first node and the gNB uses an indirect path.
As an embodiment, the first signaling is generated by Uu-RRC of the gNB in fig. 7 (b), which is received by Uu-RRC of the first node.
As an embodiment, the first signaling is transparent to the first medium and then to the second medium.
As an embodiment, the Uu-PDCP of the first node is associated with PC5-RLC, or with PC5-RLC by PC5-ADAPT when using an indirect path.
As an embodiment, when using the direct path, the first node will establish Uu-RLC, with which Uu-PDCP of the first node is associated.
As a sub-embodiment of this embodiment, the first node releases PC5-RLC after switching to the direct path.
As a sub-embodiment of this embodiment, the first node releases PC 5-accept after switching to the direct path.
As a sub-embodiment of this embodiment, the first node releases the PC5-MAC and PC5-PHY after switching to the direct path.
As a sub-embodiment of this embodiment, the first node no longer uses PC 5-accept after switching to the direct path.
As a sub-embodiment of this embodiment, there is no other protocol layer between Uu-PDCP and Uu-RLC of the first node after switching to the direct path.
Example 8
Embodiment 8 illustrates a schematic diagram in which a second field of first signaling is used to determine whether a first set of operations includes stopping a first timer, as shown in fig. 8, according to one embodiment of the present application.
As an embodiment, the second domain comprises the first domain.
As an embodiment, the first domain comprises the second domain.
As an embodiment, the second domain has no relation to and is contained by the first domain.
As an embodiment, the second domain explicitly indicates whether the first set of operations includes stopping the first timer.
As an embodiment, the second domain is radio beareconfig.
As a sub-embodiment of the above embodiment, when the SecurityConfig indicated by the second domain changes compared to the SecurityConfig being used, the first operation set includes stopping the first timer; the first set of operations does not include stopping the first timer when the SecurityConfig indicated by the second field is unchanged from the SecurityConfig being used.
As an embodiment, the second domain is fullConfig, and when the first signaling includes the second domain, the first set of operations includes stopping the first timer; when the first signaling does not include the second domain, the first set of operations does not include stopping the first timer.
As one embodiment, the second domain is a masterKeyUpdate, and when the first signaling includes the second domain, the first set of operations includes stopping the first timer; when the first signaling does not include the second domain, the first set of operations does not include stopping the first timer.
As an embodiment, the second domain is a dedication sib1-Delivery, and when the first signaling includes the second domain, the first set of operations includes stopping the first timer; when the first signaling does not include the second domain, the first set of operations does not include stopping the first timer.
As an embodiment, the second domain is a dedication system information delivery, and when the first signaling includes the second domain, the first operation set includes stopping the first timer; when the first signaling does not include the second domain, the first set of operations does not include stopping the first timer.
As an embodiment, the second domain is configured to configure a timer, and when the first signaling includes the second domain, the first set of operations includes stopping the first timer; when the first signaling does not include the second domain, the first set of operations does not include stopping the first timer.
As an embodiment, the second domain is a masterCellGroup, and the first set of operations does not include stopping the first timer when the RLC bearer of the PC5 interface indicated by the second domain is no longer serving SRBs and/or DRBs; when the second domain does not indicate that the RLC bearer of the PC5 interface is no longer serving SRBs and/or DRBs, the first set of operations includes stopping the first timer.
As a sub-embodiment of this embodiment, when the RLC bearer of the PC5 interface indicated by the second domain no longer serves SRB and/or DRB, the second domain indicates simultaneously that the RLC bearer serves SRB and/or DRB.
As a sub-embodiment of this embodiment, the sentence that the RLC bearer of the PC5 interface indicated by the second domain no longer serves the SRB and/or the DRB comprises: and releasing the RLC bearer of the PC5 interface serving the SRB and/or the DRB.
As a sub-embodiment of this embodiment, the RLC bearer of the PC5 interface is a relay RLC bearer of the PC5 interface.
As an embodiment, the second domain is a masterCellGroup, and the first set of operations does not include stopping the first timer when the RLC bearer with the PC5 interface indicated by the second domain is no longer serving any SRB and/or DRB; when the second domain does not indicate that the RLC bearer of the PC5 interface is no longer serving any SRB and/or DRB, the first set of operations includes stopping the first timer.
As a sub-embodiment of this embodiment, when the RLC bearer of the PC5 interface indicated by the second domain no longer serves any SRB and/or DRB, the second domain simultaneously indicates that any SRB and/or DRB is served by the RLC bearer.
As a sub-embodiment of this embodiment, the RLC bearer of the PC5 interface is a relay RLC bearer of the PC5 interface.
As a sub-embodiment of this embodiment, the sentence that the RLC bearer of the PC5 interface indicated by the second domain no longer serves any SRB and/or DRB comprises: and releasing the RLC bearer of the PC5 interface serving the SRB and/or the DRB.
As an embodiment, the second field is a masterCellGroup, and the first set of operations does not include stopping the first timer when the second field indicates that a sidelink RLC bearer is no longer serving SRBs and/or DRBs; when the second domain does not indicate that a sidelink RLC bearer is no longer serving SRBs and/or DRBs, the first set of operations includes stopping the first timer.
As a sub-embodiment of this embodiment, when the second domain indicates that the secondary link RLC bearer no longer serves SRB and/or DRB, the second domain simultaneously indicates RLC bearer service SRB and/or DRB.
As a sub-embodiment of this embodiment, the sentence that the second domain indicates that the sidelink RLC bearer is no longer serving SRBs and/or DRBs comprises: the sidelink RLC bearer of the serving SRB and/or DRB is released.
As an embodiment, the second field is a masterCellGroup, and the first set of operations does not include stopping the first timer when the second field indicates that a sidelink RLC bearer is no longer serving any SRB and/or DRB; the first set of operations includes stopping the first timer when the second domain does not indicate that a sidelink RLC bearer is no longer serving any SRB and/or DRB.
As a sub-embodiment of this embodiment, when the second domain indicates that the sidelink RLC bearer is no longer serving any SRB and/or DRB, the second domain simultaneously indicates that the SRB and/or DRB is served by the RLC bearer.
As a sub-embodiment of this embodiment, the sentence that the second domain indicates that the sidelink RLC bearer is no longer serving any SRB and/or DRB comprises: the sidelink RLC bearer of the serving SRB and/or DRB is released.
As an embodiment, the second domain is a masterCellGroup, and the first set of operations does not include stopping the first timer when the second domain indicates that the first radio bearer is no longer served by the first RLC bearer but is served by the second RLC bearer; the first set of operations includes stopping the first timer when the second domain does not indicate that the first radio bearer is no longer served by the first RLC bearer but is served by the second RLC bearer.
As a sub-embodiment of this embodiment, the first radio bearer is one of an SRB and/or a DRB of the first node.
As a sub-embodiment of this embodiment, the first radio bearer is any radio bearer of the first node.
As a sub-embodiment of this embodiment, the first radio bearer is either an SRB or a DRB of the first node.
As a sub-embodiment of this embodiment, the first RLC bearer is a sidelink RLC bearer.
As a sub-embodiment of this embodiment, the first RLC bearer is an RLC bearer of the PC5 interface.
As a sub-embodiment of this embodiment, the first RLC bearer is a PC5 relay RLC bearer.
As a sub-embodiment of this embodiment, the first RLC bearer is a PC 5L 2U 2N relay RLC bearer.
As a sub-embodiment of this embodiment, the first RLC bearer is an L2U 2N RLC bearer.
As a sub-embodiment of this embodiment, the first RLC bearer is a relay-related RLC bearer.
As a sub-embodiment of this embodiment, the first RLC bearer is an RLC bearer related to an L2U 2N relay.
As a sub-embodiment of this embodiment, the first RLC bearer is a secondary link relay RLC bearer.
As a sub-embodiment of this embodiment, the first RLC bearer is a relay RLC bearer with the sidelink L2.
As a sub-embodiment of this embodiment, the first RLC bearer is a relay RLC bearer with the sidelink U2N.
As a sub-embodiment of this embodiment, the second RLC bearer is a UuRLC bearer.
As a sub-embodiment of this embodiment, the second RLC bearer is an RLC bearer.
As a sub-embodiment of this embodiment, the second RLC bearer is configured by RLC-beaderconfig.
As a sub-embodiment of this embodiment, the first RLC bearer corresponds to a different interface than the second RLC bearer, the different interface including { PC5, uu }.
As a sub-embodiment of this embodiment, the first RLC bearer corresponds to a different link than the second RLC bearer, the different link including { primary link, secondary link }.
As a sub-embodiment of this embodiment, the main link is a wireless link with respect to the sidelink.
As a sub-embodiment of this embodiment, the main link is a wireless link between the UE and the gNB.
As a sub-embodiment of this embodiment, the primary link is a radio link between the UE and the cell.
As a sub-embodiment of this embodiment, the second radio bearer is one of an SRB and/or a DRB of the second node.
As a sub-embodiment of this embodiment, the second radio bearer is any radio bearer of the second node.
As a sub-embodiment of this embodiment, the second radio bearer is either an SRB or a DRB of the second node.
As a sub-embodiment of this embodiment, the second RLC bearer is a sidelink RLC bearer.
As a sub-embodiment of this embodiment, the second RLC bearer is an RLC bearer of the PC5 interface.
As a sub-embodiment of this embodiment, the second RLC bearer is a PC5 relay RLC bearer.
As a sub-embodiment of this embodiment, the second RLC bearer is a PC 5L 2U 2N relay RLC bearer.
As a sub-embodiment of this embodiment, the second RLC bearer is an L2U 2N RLC bearer.
As a sub-embodiment of this embodiment, the second RLC bearer is a relay-related RLC bearer.
As a sub-embodiment of this embodiment, the second RLC bearer is an RLC bearer related to an L2U 2N relay.
As a sub-embodiment of this embodiment, the second RLC bearer is a secondary link relay RLC bearer.
As a sub-embodiment of this embodiment, the second RLC bearer is a relay RLC bearer with the sidelink L2.
As a sub-embodiment of this embodiment, the second RLC bearer is a relay RLC bearer with the sidelink U2N.
As a sub-embodiment of this embodiment, the second RLC bearer is a Uu RLC bearer.
As a sub-embodiment of this embodiment, the second RLC bearer is an RLC bearer.
As a sub-embodiment of this embodiment, the second RLC bearer is configured by RLC-beaderconfig.
As a sub-embodiment of this embodiment, the meaning of the sentence that the second domain indicates that the first radio bearer is no longer served by the first RLC bearer but is served by the second RLC bearer includes that the second domain indicates that the first RLC bearer is released.
As one embodiment, the second domain is a masterCellGroup, and the first set of operations does not include stopping the first timer when the second domain indicates that a first radio bearer is no longer served by a first type of RLC bearer but is served by a second type of RLC bearer; the first set of operations includes stopping the first timer when the second domain does not indicate that the first radio bearer is no longer served by the first type RLC bearer but is served by the second type RLC bearer.
As a sub-embodiment of this embodiment, the first type of RLC bearer is an RLC bearer of the Uu interface; the second type RLC bearer is an RLC bearer of a PC5 interface.
As a sub-embodiment of this embodiment, the first type of RLC bearer is an RLC bearer; the second type of RLC bearer is a sidelink RLC bearer.
As a sub-embodiment of this embodiment, the second type of RLC bearer is an RLC bearer of the Uu interface; the first type of RLC bearer is an RLC bearer of a PC5 interface.
As a sub-embodiment of this embodiment, the second type of RLC bearer is an RLC bearer; the first type of RLC bearer is a sidelink RLC bearer.
As a sub-embodiment of this embodiment, the first type of RLC bearer and the second type of RLC bearer are different types of RLC bearers, which refer to RLC bearers of the Uu interface or RLC bearers of the PC5 interface.
As a sub-embodiment of this embodiment, the first type of RLC bearer and the second type of RLC bearer are different types of RLC bearers, which refer to RLC bearers or sidelink RLC bearers.
As a sub-embodiment of this embodiment, the phrase that the second domain does not indicate that the first radio bearer is no longer served by the first type RLC bearer but is served by the second type RLC bearer includes: the bearers of the RLC layer serving the first radio bearer indicated by the second domain are RLC bearers of the same type both before and after performing the first signaling; the RLC bearers of the same type refer to RLC bearers which are both Uu interfaces or RLC bearers which are both PC5 interfaces.
As a sub-embodiment of this embodiment, the phrase that the second domain does not indicate that the first radio bearer is no longer served by the first type RLC bearer but is served by the second type RLC bearer includes: the bearers of the RLC layer serving the first radio bearer indicated by the second domain are RLC bearers of the same type both before and after performing the first signaling; the same type of RLC bearer refers to both RLC bearers or both sidelink RLC bearers.
As a sub-embodiment of this embodiment, the phrase that the second domain does not indicate that the first radio bearer is no longer served by the first type RLC bearer but is served by the second type RLC bearer includes: the second domain does not indicate that a bearer of an RLC layer serving the first radio bearer has changed.
As a sub-embodiment of this embodiment, the phrase that the second domain does not indicate that the first radio bearer is no longer served by the first type RLC bearer but is served by the second type RLC bearer includes: the second domain indicates that the RLC layer serving the first radio bearer is increased in bearer, and the increased RLC layer serving the first radio bearer and the original RLC layer serving the first radio bearer are the same type of RLC bearer, where the same type of RLC bearer refers to both RLC bearers or both sidelink RLC bearers.
As a sub-embodiment of this embodiment, the phrase that the second domain does not indicate that the first radio bearer is no longer served by the first type RLC bearer but is served by the second type RLC bearer includes: the second domain indicates that a bearer of an RLC layer serving the first radio bearer is added, the added bearer of the RLC layer serving the first radio bearer and a bearer of an original RLC layer serving the first radio bearer are the same type of RLC bearer, and the same type of RLC bearer refers to a bearer of both Uu interfaces or an RLC bearer of both PC5 interfaces.
As an embodiment, either SRB or DRB of the first node is served only by a sidelink RLC bearer or only by an RLC bearer.
As one embodiment, the second domain is fullConfig and masterKeyUpdate, and when the first signaling includes the second domain, the first set of operations includes stopping the first timer; when the first signaling does not include the second domain, the first set of operations does not include stopping the first timer.
As one embodiment, the second domain is a newUE-Identity included in the first domain of the first signaling, the newUE-Identity indicating a C-RNTI of the first node, and the first set of operations includes stopping the first timer when the C-RNTI indicated by the second domain is not the C-RNTI currently used by the first node; the first set of operations does not include stopping the first timer when the C-RNTI indicated by the second domain is the C-RNTI currently used by the first node.
As an embodiment, the second domain is a physiocellid, and the first set of operations includes stopping the first timer when a change occurs in a physical cell identity indicated by the second domain; the first set of operations does not include stopping the first timer when the physical cell identity indicated by the second domain has not changed.
As an embodiment, the second domain is a physiocellid, and the first set of operations includes stopping the first timer when the physical cell identity indicated by the second domain changes from the current physical cell identity of the first node; the first set of operations does not include stopping the first timer when the physical cell identity indicated by the second domain has not changed from the current physical cell identity of the first node.
As an embodiment, the second domain is PLMN-identity infolist, and the first operation set includes stopping the first timer when a change occurs in cellIdentity included in the second domain; when the cellIdentity included in the second domain is unchanged, the first operation set includes not stopping the first timer.
As an embodiment, the second domain is a PLMN-identity info list, and the first set of operations includes stopping the first timer when a cell identity included in the second domain changes with respect to a current primary cell of the first node; when the cellIdentity included in the second domain is unchanged relative to the current primary cell of the first node, the first set of operations includes not stopping the first timer.
As an embodiment, the second domain is cellIdentity, and the first set of operations includes stopping the first timer when the cell identity indicated by the second domain changes; the first set of operations includes not stopping the first timer when the cell identity indicated by the second domain has not changed.
As an embodiment, the second domain is cellIdentity, and when the cell identity indicated by the second domain is different from the identity of the primary cell of the first node, the first set of operations includes stopping the first timer; the first set of operations includes not stopping the first timer when the cell identity indicated by the second domain is the same as an identity of a primary cell of the first node.
As an embodiment, the second domain is a physiocellid, and the first set of operations includes stopping the first timer when the physical cell identity indicated by the second domain is different from the physical cell identity of the primary cell of the first node; the first set of operations includes not stopping the first timer when the physical cell identity indicated by the second domain is the same as the physical cell identity of the primary cell of the first node.
As an embodiment, the second domain is a physiocellid, and the first set of operations includes stopping the first timer when a change occurs in a physical cell identity indicated by the second domain; the first set of operations includes not stopping the first timer when the physical cell identity indicated by the second domain has not changed.
As one embodiment, the second field indicates that the first set of operations does not include stopping the first timer when performing the indirect path to direct path conversion; the first set of operations does not include stopping the first timer when the second field does not indicate that the indirect path to direct path conversion is performed.
As a sub-embodiment of this embodiment, the sentence that the second field does not indicate that the indirect path to direct path conversion is performed comprises: the second field indicates a configuration other than performing the indirect path to direct path conversion.
As a sub-embodiment of this embodiment, the sentence that the second field does not indicate that the indirect path to direct path conversion is performed comprises: the second field indicates that a handover is performed.
As a sub-embodiment of this embodiment, the sentence that the second field does not indicate that the indirect path to direct path conversion is performed comprises: the second domain indicates to change the primary cell.
As a sub-embodiment of this embodiment, the sentence that the second field does not indicate that the indirect path to direct path conversion is performed comprises: the second field indicates a change to the primary cell group.
As a sub-embodiment of this embodiment, the sentence that the second field does not indicate that the indirect path to direct path conversion is performed comprises: the second field indicates that CHO or CPC is performed.
As an embodiment, the second domain indicates an access barring parameter, and the first set of operations includes stopping the first timer when the access barring related parameter indicated by the second domain changes; the first set of operations does not include stopping the first timer when the parameter related to the access barring indicated by the second domain has not changed.
As an embodiment, the second domain is PathSwitchConfig.
As a sub-embodiment of this embodiment, the first set of operations does not include stopping the first timer when the second field indicates a transition from an indirect path to a direct path.
As a sub-embodiment of this embodiment, the first set of operations includes stopping the first timer when the second domain indicates a transition from a direct path to an indirect path.
As a sub-embodiment of this embodiment, the first set of operations does not include stopping the first timer when the second domain indicates a transition from a direct path to an indirect path.
As a sub-embodiment of this embodiment, the first set of operations does not include stopping the first timer when the second domain is present.
As a sub-embodiment of this embodiment, the first set of operations includes stopping the first timer when the second domain is not present.
As an embodiment, the second domain is cellIdentity, and the first set of operations includes stopping the first timer when the cell Identity indicated by the second domain is different from pCell-Identity maintained by the first node; the first set of operations does not include stopping the first timer when the cell Identity indicated by the second domain is the same as pCell-Identity maintained by the first node.
As an embodiment, the second domain is a physiocellid, and the first set of operations includes stopping the first timer when the cell Identity indicated by the second domain is different from pCell-Identity maintained by the first node; the first set of operations does not include stopping the first timer when the cell Identity indicated by the second domain is the same as pCell-Identity maintained by the first node.
As one embodiment, the first node receives a first message, where the first message includes a cellIdentity, and when a cell Identity indicated by the cellIdentity included in the first message is different from a pCell-Identity maintained by the first node, the first operation set includes stopping the first timer; the first set of operations includes stopping the first timer when the cell Identity indicated by the cellIdentity included in the first message is concurrent with the pCell-Identity maintained by the first node.
As a sub-embodiment of this embodiment, the first message is SIB1.
As a sub-embodiment of this embodiment, the first message is a system information block.
As a sub-embodiment of this embodiment, the first message is the first signaling.
As a sub-embodiment of this embodiment, the first message is sent by way of broadcasting.
Example 9
Embodiment 9 illustrates a schematic diagram in which a first field of first signaling is used to determine whether a first set of operations includes stopping a first timer, as shown in fig. 9, according to one embodiment of the present application.
As one embodiment, when the first domain does not include newUE-Identity, the first set of operations does not include stopping the first timer; when the first domain includes newUE-Identity, the first set of operations includes stopping the first timer.
As one embodiment, when the spCellConfigCommon included in the first domain does not include a physiocellid, the first set of operations does not include stopping the first timer; when the spCellConfigCommon included in the first domain includes a physiocellid, the first set of operations includes stopping the first timer.
As an embodiment, when the first field does not include cellIdentity, the first set of operations does not include stopping the first timer; when the first field includes cellIdentity, the first set of operations includes stopping the first timer.
As one embodiment, when the first field indicates CHO or CPC, the first set of operations includes stopping the first timer; when the first field does not indicate CHO nor CPC, the first set of operations does not include stopping the first timer.
As one embodiment, when the first domain indicates a relay path transition, the first set of operations does not include stopping the first timer; the first set of operations includes stopping the first timer when the first domain does not indicate a relay path transition.
As one embodiment, when the first domain indicates a DAPS handoff, the first set of operations includes stopping the first timer; when the first domain does not indicate a DAPS handoff, the first set of operations does not include stopping the first timer.
As an embodiment, the first field explicitly indicates whether the first set of operations includes stopping the first timer.
As one embodiment, when the first signaling indicates a path switch, the first set of operations does not include stopping the first timer; the first set of operations includes stopping the first timer when the first signaling does not indicate a path switch.
As a sub-embodiment of this embodiment, the path switch comprises a switch from an indirect path to a direct path.
As a sub-embodiment of this embodiment, the path switch comprises a switch from a direct path to an indirect path.
As a sub-embodiment of this embodiment, the first field indicates the path switch.
As one embodiment, when the first domain includes newUE-identity remote, the first set of operations does not include stopping the first timer; when the first domain includes newUE-Identity, the first set of operations includes stopping the first timer.
Example 10
Embodiment 10 illustrates a block diagram of a processing apparatus for use in a first node according to one embodiment of the present application; as shown in fig. 10. In fig. 10, a processing device 1000 in a first node includes a first handler 1001. In the case of the embodiment of the present invention in which the number of the substrates in the sample is 10,
the first processor 1001 starts a first timer, which is used for access barring;
the first handler 1001 receives first signaling, the first signaling being used to configure the MCG, the first signaling comprising a first domain; in response to receiving the first signaling, performing a first set of operations;
Wherein the first domain is a reconfigurationWithSync, and the first operation set includes sending a second signaling for confirming that configuration of at least the first signaling is successfully completed; the first signaling is used to indicate whether the first set of operations includes stopping the first timer.
As one embodiment, the format of the first signaling is used to determine whether the first set of operations includes stopping the first timer; the format of the first signaling is one candidate format in a candidate format set, the candidate format set comprising at least two candidate formats, a first format and a second format; any two candidate formats in the candidate format set are two RRC IEs with different names, or any two candidate formats in the candidate format set are two domains with different names; the first set of operations includes stopping the first timer when the format of the first signaling is the first format, and the first set of operations does not include stopping the first timer when the format of the first signaling is the second format.
As an embodiment, the first signaling comprises a second domain, the second domain of the first signaling being used to determine whether the first set of operations comprises stopping the first timer.
As one embodiment, the first field of the first signaling is used to determine whether the first set of operations includes stopping the first timer.
As an embodiment, the first processor 1001 receives a first condition reconfiguration, the first condition reconfiguration including a first condition and the first signaling associated with the first condition;
the first handler 1001 performs the first signaling in response to the first condition being satisfied; in response to performing the first signaling, the first set of operations is performed.
As an embodiment, the first processor 1001, after the act receives the first signaling, receives third signaling, the third signaling being used to indicate a transition from a direct path to an indirect path;
the first handler 1001 performs the third signaling; stopping the first timer in response to performing the third signaling;
wherein the indirect path is that data transmission between the first node and a network is forwarded through a relay; the direct path is that data transmission between the first node and the network does not pass through a relay.
As an embodiment, when the first set of operations of the first signaling is used to indicate that the first set of operations includes stopping the first timer, the primary cell of the first node remains unchanged before the first signaling is performed and after the first signaling is performed; when the first set of operations of the first signaling is used to indicate that the first set of operations does not include stopping the first timer, a primary cell of the first node changes before and after the first signaling is performed.
As an embodiment, the first processor 1001 starts a second timer in response to performing the first signaling;
the first handler 1001 initiates a first random access procedure for the cell indicated by the first signaling, a successful completion of the first random access procedure being used to stop the second timer; wherein expiration of the second timer is used to trigger RRC reestablishment.
As an embodiment, the first node is a User Equipment (UE).
As an embodiment, the first node is a terminal supporting a large delay difference.
As an embodiment, the first node is a terminal supporting NTN.
As an embodiment, the first node is an aircraft.
As an embodiment, the first node is a U2N remote UE.
As an embodiment, the first node is a mobile phone.
As an embodiment, the first node is an in-vehicle terminal.
As an embodiment, the first node is a relay.
As an embodiment, the first node is a ship.
As an embodiment, the first node is an internet of things terminal.
As an embodiment, the first node is a terminal of an industrial internet of things.
As an embodiment, the first node is a device supporting low latency and high reliability transmissions.
As an embodiment, the first node is a sidelink communication node.
As an example, the first processor 1001 includes at least one of the antenna 452, the receiver 454, the receive processor 456, the multi-antenna receive processor 458, the controller/processor 459, the memory 460, or the data source 467 of example 4.
As an example, the first processor 1001 includes at least one of the antenna 452, the transmitter 454, the transmit processor 468, the multi-antenna transmit processor 457, the controller/processor 459, the memory 460, or the data source 467 of example 4.
Example 11
Embodiment 11 illustrates a block diagram of a processing apparatus for use in a second node according to one embodiment of the present application; as shown in fig. 11. In fig. 11, the processing means 1100 in the second node comprises a second transmitter 1101 and a second receiver 1102. In the case of the embodiment of the present invention in which the sample is a solid,
a second transmitter 1101 that transmits first signaling, the first signaling being used to configure the MCG, the first signaling including a first domain;
Wherein the receiving of the first signaling is used to trigger a receiver of the first signaling to perform a first set of operations; the first domain is a reconfigurationWithSync, and the first operation set includes sending second signaling for confirming that configuration of at least the first signaling is successfully completed; the first signaling is used to indicate whether the first set of operations includes stopping a first timer, the first timer being used for access barring.
As one embodiment, the format of the first signaling is used to determine whether the first set of operations includes stopping the first timer; the format of the first signaling is one candidate format in a candidate format set, the candidate format set comprising at least two candidate formats, a first format and a second format; any two candidate formats in the candidate format set are two RRC IEs with different names; the first set of operations includes stopping the first timer when the format of the first signaling is the first format, and the first set of operations does not include stopping the first timer when the format of the first signaling is the second format.
As an embodiment, the first signaling comprises a second domain, the second domain of the first signaling being used to determine whether the first set of operations comprises stopping the first timer.
As one embodiment, the first field of the first signaling is used to determine whether the first set of operations includes stopping the first timer.
As an embodiment, the first transmitter 1101 sends a first condition reconfiguration comprising a first condition and the first signaling associated with the first condition; a first condition is satisfied that is used to trigger a receiver of the first signaling to perform the first signaling; the first signaling is performed to trigger a recipient of the first signaling to perform the first set of operations.
As an embodiment, the first transmitter 1101 sends second signaling after the act of sending the first signaling, the second signaling being used to indicate a transition from a direct path to an indirect path;
the second signaling is performed by a receiver of the second signaling and is used to trigger the stopping of the first timer;
wherein the indirect path is that data transmission between the first node and a network is forwarded through a relay; the direct path is that data transmission between the first node and the network does not pass through a relay.
As an embodiment, when the first set of operations of the first signaling used to indicate the first set of operations includes stopping the first timer, the primary cell of the receiver of the first signaling remains unchanged before the receiver of the first signaling performs the first signaling and after the receiver of the first signaling performs the first signaling; when the first set of operations of the first signaling used to indicate that the first set of operations does not include stopping the first timer, a primary cell of a receiver of the first signaling changes before and after the receiver of the first signaling performs the first signaling.
As an embodiment, the second node is a satellite.
As one embodiment, the second node is an IoT node.
As an embodiment, the second node is a relay.
As an embodiment, the second node is a U2N relay UE.
As an embodiment, the second node is an access point.
As an embodiment, the second node is a base station.
As an example, the second transmitter 1101 includes at least one of the antenna 420, the transmitter 418, the transmission processor 416, the multi-antenna transmission processor 471, the controller/processor 475, and the memory 476 in example 4.
As an example, the second receiver 1102 may include at least one of the antenna 420, the receiver 418, the receive processor 470, the multi-antenna receive processor 472, the controller/processor 475, and the memory 476 of example 4.
Those of ordinary skill in the art will appreciate that all or a portion of the steps of the above-described methods may be implemented by a program that instructs associated hardware, and the program may be stored on a computer readable storage medium, such as a read-only memory, a hard disk or an optical disk. Alternatively, all or part of the steps of the above embodiments may be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiment may be implemented in a hardware form or may be implemented in a software functional module form, and the application is not limited to any specific combination of software and hardware. User equipment, terminals, and UEs in the present application include, but are not limited to, unmanned aerial vehicles, communication modules on unmanned aerial vehicles, remote control airplanes, aircraft, mini-planes, cell phones, tablet computers, notebooks, vehicle-mounted communication devices, wireless sensors, network cards, internet of things terminals, RFID terminals, NB-IoT terminals, MTC (Machine Type Communication ) terminals, eMTC (enhanced MTC) terminals, data cards, network cards, vehicle-mounted communication devices, low cost cell phones, low cost tablet computers, satellite communication devices, ship communication devices, NTN user devices, and other wireless communication devices. The base station or system device in the present application includes, but is not limited to, a macro cell base station, a micro cell base station, a home base station, a relay base station, a gNB (NR node B) NR node B, a TRP (Transmitter Receiver Point, transmitting/receiving node), an NTN base station, a satellite device, a flight platform device, and other wireless communication devices.
The present invention may be embodied in other specific forms without departing from its spirit or essential characteristics. Accordingly, the presently disclosed embodiments are considered in all respects to be illustrative and not restrictive. The scope of the invention is indicated by the appended claims rather than by the foregoing description, and all changes that come within the meaning and range of equivalents are intended to be embraced therein.

Claims (11)

1. A first node for wireless communication, comprising:
a first processor to start a first timer, the first timer being used for access barring;
the first processor receives first signaling, the first signaling being used to configure an MCG, the first signaling comprising a first domain; in response to receiving the first signaling, performing a first set of operations;
wherein the first domain is a reconfigurationWithSync, and the first operation set includes sending a second signaling for confirming that configuration of at least the first signaling is successfully completed; the first signaling is used to indicate whether the first set of operations includes stopping the first timer.
2. The first node of claim 1, wherein the format of the first signaling is used to determine whether the first set of operations includes stopping the first timer; the format of the first signaling is one candidate format in a candidate format set, the candidate format set comprising at least two candidate formats, a first format and a second format; any two candidate formats in the candidate format set are two RRC IEs with different names; the first set of operations includes stopping the first timer when the format of the first signaling is the first format, and the first set of operations does not include stopping the first timer when the format of the first signaling is the second format.
3. The first node of claim 1, wherein the first signaling comprises a second domain, the second domain of the first signaling being used to determine whether the first set of operations comprises stopping the first timer.
4. The first node of claim 1, wherein the first field of the first signaling is used to determine whether the first set of operations includes stopping the first timer.
5. The first node according to any of claims 1 to 4, comprising:
the first processor receives a first condition reconfiguration, the first condition reconfiguration including a first condition and the first signaling associated with the first condition;
the first handler performing the first signaling in response to a first condition being met; in response to performing the first signaling, the first set of operations is performed.
6. The first node according to any of claims 1 to 5, comprising:
the first processor, after the act of receiving the first signaling, receiving third signaling, the third signaling being used to indicate a transition from a direct path to an indirect path;
The first processor executing the third signaling; stopping the first timer in response to performing the third signaling;
wherein the indirect path is that data transmission between the first node and a network is forwarded through a relay; the direct path is that data transmission between the first node and the network does not pass through a relay.
7. The first node according to any of the claims 1 to 6, characterized in that,
when the first set of operations of the first signaling is used to indicate that the first set of operations includes stopping the first timer, the primary cell of the first node remains unchanged until and after the first signaling is performed; when the first set of operations of the first signaling is used to indicate that the first set of operations does not include stopping the first timer, a primary cell of the first node changes before and after the first signaling is performed.
8. The first node according to any of the claims 1 to 7, characterized in that,
the first processor, in response to performing the first signaling, starting a second timer;
The first processor initiating a first random access procedure for the cell indicated by the first signaling, a successful completion of the first random access procedure being used to stop the second timer;
wherein expiration of the second timer is used to trigger RRC reestablishment.
9. A second node for wireless communication, comprising:
a second transmitter that transmits first signaling, the first signaling being used to configure the MCG, the first signaling including a first domain;
wherein the receiving of the first signaling is used to trigger execution of a first set of operations; the first domain is a reconfigurationWithSync, and the first operation set includes sending second signaling for confirming that configuration of at least the first signaling is successfully completed; the first signaling is used to indicate whether the first set of operations includes stopping a first timer, the first timer being used for access barring.
10. A method in a first node for wireless communication, comprising:
starting a first timer, the first timer being used for access barring;
receiving first signaling, the first signaling being used to configure an MCG, the first signaling comprising a first domain; in response to receiving the first signaling, performing a first set of operations;
Wherein the first domain is a reconfigurationWithSync, and the first operation set includes sending a second signaling for confirming that configuration of at least the first signaling is successfully completed; the first signaling is used to indicate whether the first set of operations includes stopping the first timer.
11. A method in a second node for wireless communication, comprising:
transmitting first signaling, the first signaling being used to configure an MCG, the first signaling comprising a first domain;
wherein the receiving of the first signaling is used to trigger execution of a first set of operations; the first domain is a reconfigurationWithSync, and the first operation set includes sending second signaling for confirming that configuration of at least the first signaling is successfully completed; the first signaling is used to indicate whether the first set of operations includes stopping a first timer, the first timer being used for access barring.
CN202111314627.0A 2021-11-01 2021-11-08 Method and apparatus for wireless communication Pending CN116095632A (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111281427X 2021-11-01
CN202111281427 2021-11-01

Publications (1)

Publication Number Publication Date
CN116095632A true CN116095632A (en) 2023-05-09

Family

ID=86210785

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111314627.0A Pending CN116095632A (en) 2021-11-01 2021-11-08 Method and apparatus for wireless communication

Country Status (1)

Country Link
CN (1) CN116095632A (en)

Similar Documents

Publication Publication Date Title
CN114007196A (en) Method and equipment used for wireless communication
CN116266918A (en) Method and apparatus for wireless communication
CN115118400B (en) Method and apparatus for wireless communication
CN113938841B (en) Method and device used in node of wireless communication
CN113747610B (en) Method and apparatus in a communication node for wireless communication
CN116133002A (en) Method and apparatus for wireless communication
CN114916095A (en) Method and equipment used for wireless communication
CN115484691A (en) Method and equipment used for wireless communication
CN115379530A (en) Method and equipment used for wireless communication
CN116095632A (en) Method and apparatus for wireless communication
US20240179611A1 (en) Method and device for wireless communication
CN116033552B (en) Method and apparatus for wireless communication
US20230156844A1 (en) Method and device for wireless communication
US20230379881A1 (en) Method and device used for wireless communication
US11943745B2 (en) Method and device for sidelink wireless communication
US20230232485A1 (en) Method and device for wireless communication
US20240107296A1 (en) Method and device for wireless communication
WO2024078431A1 (en) Method and device used for wireless communication
CN116567756A (en) Method and apparatus for wireless communication
CN116800390A (en) Method and apparatus for wireless communication
CN116744475A (en) Method and apparatus for wireless communication
CN115884222A (en) Method and equipment used for wireless communication
CN116156585A (en) Method and apparatus for wireless communication
CN116137705A (en) Method and apparatus for wireless communication
CN116828545A (en) Method and apparatus for wireless communication

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination