CN115379530A - A method and device used for wireless communication - Google Patents

Abstract

The application discloses a method and apparatus used for wireless communication, comprising: receiving a first parameter set, and executing access blocking check according to the first parameter set; in response to performing the access barring check, starting a first timer; sending a second message, the second message being used to request an RRC connection, the second message including at least a request cause, the second message being used to trigger the first message; receiving the first message; operating the first timer after receiving the first message, the operation being a stop or a continuation of operation, the operation relating to a trigger cause of the second message; the method and the device ensure fairness and robustness of access blocking through the first message and the second message.

Description

A method and device used for wireless communication

technical field

The present application relates to a transmission method and device in a wireless communication system, in particular to a method and device for reducing service interruption, improving service continuity, enhancing reliability, and security in wireless communication.

Background technique

The application scenarios of future wireless communication systems are becoming more and more diversified, and different application scenarios put forward different performance requirements for the system. In order to meet the different performance requirements of various application scenarios, the new air interface technology (NR, New Radio) (or Fifth Generation, 5G) to conduct research, passed the WI (Work Item, work item) of NR at the 3GPP RAN#75 plenary meeting, and started to standardize NR.

In communication, whether it is LTE (Long Term Evolution, long-term evolution) or 5G NR, it will involve accurate reception of reliable information, optimized energy efficiency ratio, determination of information validity, flexible resource allocation, and scalable system structure. Efficient non-access layer information processing, low service interruption and drop rate, support for low power consumption, which is important for normal communication between base stations and user equipment, reasonable scheduling of resources, and balance of system load Significance, it can be said that it is the cornerstone of high throughput, meeting the communication needs of various services, improving spectrum utilization, and improving service quality, whether it is eMBB (ehanced Mobile BroadBand, enhanced mobile broadband), URLLC (Ultra Reliable Low Latency Communication, Ultra Reliable Low Latency Communication, ultra High reliability and low latency communication) or eMTC (enhanced Machine Type Communication, enhanced machine type communication) are indispensable. At the same time, in the IIoT (Industrial Internet of Things, the Internet of Things in the industrial field, in the V2X (Vehicular to X, vehicle communication), in the communication between devices (Device to Device), in the communication of unlicensed spectrum, in the user Communication quality monitoring, 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 In multi-antenna codebook selection, there are extensive requirements in signaling design, neighbor cell management, service management, and beamforming. Information transmission methods are divided into broadcast and unicast, both of which are 5G system Indispensable as they are very helpful in fulfilling the above requirements.

As the scenarios and complexity of the system continue to increase, higher requirements are put forward for reducing interruption rate, reducing delay, enhancing reliability, enhancing system stability, business flexibility, and power saving. Compatibility between different versions of different systems also needs to be considered during system design.

Contents of the invention

In various communication scenarios, the use of a relay is involved. For example, when a UE is not within the coverage area of a cell, it can access the network through a relay, and the relay node can be another UE. When accessing the network through a relay, the selected relay node may have established an RRC connection with the network, or may not have established an RRC connection. If the RRC connection has not been established, the relay node needs to establish an RRC connection to communicate with the remote The data of the node (remote UE) is forwarded or relayed. Both the remote node and the relay node need to establish an RRC connection with the network. The connection request may be to newly establish an RRC connection, or to resume a suspended RRC connection. Regardless of whether it is a remote node or a relay node, if it wants to request RRC or connection, it needs to perform access control, and the access control performed on the UE side can be realized through a unified access control (Unified Access Control, UAC) mechanism. When performing access control, the UE needs to perform an access barring check (Access Barring Check). When the result of the check is no barring, the UE can access the network; otherwise, the UE is prohibited from initiating an access request. The data of the remote node involves the remote node and the relay node at the same time. In theory, one or both of the remote node and the relay node can perform access blocking checks, or the two can be separated independently. The access control check of the node's connection request is performed at the remote node, and the relay node only performs the access control check for the access request triggered by its own data. In this case, the two nodes are relatively independent, and the relay node will not affect the access of the remote node, even if it has passed the access control check and is in the blocked state, the blocked state of the relay only affects the relay node without affecting remote nodes. The blocking state will last for a period of time, and the duration is configured by the system. During this period of time, the UE is not allowed to initiate an access request for a specific access category in the blocking state. If the UE directly communicates with the network, once the UE accesses the network, the blocking state is meaningless, and the UE will immediately leave the blocking state, but the situation is different when using a relay node to communicate, regardless of whether the relay node is in the blocking state, it is possible Because the access to the network is to forward the data of the remote node, if in this case the connection state is caused to leave the blocking state, it means that the relay node can bypass the access control, which will have a negative impact on the network.

With regard to the above-mentioned problems, the present application provides a solution.

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

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

receiving a first set of parameters, performing an access blocking check according to said first set of parameters; in response to performing said access blocking check, starting a first timer;

sending a second message, the second message is used to request an RRC connection, the second message includes at least a request reason, the second message is used to trigger the first message;

receiving the first message; operating the first timer after receiving the first message, the operation is to stop or continue to run, and the operation is related to the triggering cause of the second message;

Wherein, the operation in the phrase related to the triggering cause of the second message includes:

When said triggering cause of said second message is for an information bit generated at said first node, said operation is stopping in response to receiving said first message;

When the triggering cause of the second message is to forward information bits generated at the second node, the operation is to continue running.

As an embodiment, the problems to be solved in this application include: when the relay node and the remote node perform access control checks independently, the access of the remote node is not affected by whether the relay node is in a blocking state, and the remote node The access of end nodes should also not affect the current blocking state of relay nodes. Therefore, how to avoid the self-blocking state caused by the access of the relay node for the access of the remote node is a problem to be solved in this application.

As an embodiment, the advantages of the above method include: the method proposed in this application can solve the above problems. At the same time, the method proposed in this application can make the access control of the relay node and the remote node relatively independent, which is conducive to the access control for different access requirements, and at the same time avoids the remote node and the relay node performing two Repeated access control checks. In the method of the present application, the access of the relay node to itself may not be affected by the access of the remote node, so that the unified access control arranged by the network is more robust and reliable.

Specifically, according to one aspect of the present application, a third message is received through the PC5 interface, where the third message is used to request the RRC connection of the second node;

Sending a fourth message through the Uu interface, the fourth message is generated by the third message, and the fourth message is used to request the RRC connection of the second node; the third message and the fourth message are Included requests have the same reason.

Specifically, according to one aspect of the present application, a second parameter set is sent, and the first parameter set is used to generate the second parameter set; the second parameter set is used for sending the third message Perform access blocking checks.

Specifically, according to one aspect of the present application, the second message includes a first field, the third message includes a second field, and the fourth message includes a third field; the second field and the third The values of the domains are the same; the third message is used to determine the value of the first domain;

The first field, the second field and the third field are respectively used to indicate the request reason for requesting the RRC connection.

Specifically, according to one aspect of the present application, a fifth message and a sixth message are received, and the fifth message and the sixth message are respectively used to release the RRC connection; the fifth message includes a first time length; The fifth message includes that the first length of time is used to trigger the start of a second timer; the expiration value of the second timer is equal to the first length of time; the start of the second timer is separated by the The receiving moment of the sixth message is less than the expiration value of the second timer; the start of the second timer is earlier than the sending of the second message; the receiving of the sixth message is later than the sending of the second message sending; the sixth message includes a second length of time; the sixth message includes that the second length of time is used to trigger a restart of the second timer; the restart of the second timer after The expiration value is equal to the second length of time; the running state of the second timer is used for access blocking checks.

Specifically, according to one aspect of the present application, the sixth message is received, and the sixth message is used to release the RRC connection; the first timer is operated after receiving the sixth message, and the operation is to stop or continue Running, the operation is related to the triggering cause of the second message; when the sixth message is received, the first timer is in the running state;

Wherein, the operation in the phrase related to the triggering cause of the second message includes:

Said operation is stopping in response to receiving said sixth message when said triggering cause of said second message is for an information bit generated at said first node;

When the triggering cause of the second message is to forward information bits generated at the second node, the operation is to continue running.

Specifically, according to one aspect of the present application, a seventh message is sent, where the seventh message is used to indicate the first timer.

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 an 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 vehicle-mounted terminal.

Specifically, according to one aspect of the present application, the first node is an aircraft.

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

The first node, receiving a first set of parameters, performing an access blocking check according to the first set of parameters; in response to performing the access blocking check, starting a first timer;

The first node sends a second message, the second message is used to request an RRC connection, the second message includes at least a request reason, and the second message is used to trigger the first message;

The first node receives the first message; operates the first timer after receiving the first message, the operation is to stop or continue to run, and the operation is related to the trigger cause of the second message;

Wherein, the operation in the phrase related to the triggering cause of the second message includes:

When said triggering cause of said second message is for an information bit generated at said first node, said operation is stopping in response to receiving said first message;

When the triggering cause of the second message is to forward information bits generated at the second node, the operation is to continue running.

Specifically, according to one aspect of the present application, a third message is sent through the PC5 interface, where the third message is used to request the RRC connection of the second node;

The first node sends a fourth message through the Uu interface, the fourth message is generated by the third message, and the fourth message is used to request the RRC connection of the second node; the third message and The request reasons included in the fourth message are the same.

Specifically, according to one aspect of the present application, a second parameter set is received, and the first parameter set is used to generate the second parameter set; the second parameter set is used for sending the third message performing an access blocking check; and starting a third timer in response to performing said access blocking check.

Specifically, according to one aspect of the present application, the second message includes a first field, the third message includes a second field, and the fourth message includes a third field; the second field and the third The values of the domains are the same; the third message is used to determine the value of the first domain;

The first field, the second field and the third field are respectively used to indicate the request reason for requesting the RRC connection.

Specifically, according to one aspect of the present application, an eighth message is received, and the eighth message is used to agree to the RRC connection request of the second node in the third message, or the eighth message is used to releasing the RRC connection of the second node upon the request of the third message; in response to receiving the eighth message, stopping the third timer.

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 an 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 vehicle-mounted terminal.

Specifically, according to one aspect of the present application, the first node is an aircraft.

The present application discloses a method used in a third node of wireless communication, including:

Send the first set of parameters;

receive the second message;

send the first message;

the sender of the second message performs an access blocking check according to the first set of parameters; in response to performing the access blocking check, starts a first timer; the second message is used to request an RRC connection, The second message includes at least a reason for the request, the second message is used to trigger the first message; the sender of the second message operates the first timer after receiving the first message, the The operation is to stop or continue to run, and the operation is related to the trigger cause of the second message;

Wherein, the operation in the phrase related to the triggering cause of the second message includes:

When said triggering cause of said second message is for an information bit generated at said first node, said operation is stopping in response to receiving said first message;

When the triggering cause of the second message is to forward information bits generated at the second node, the operation is to continue running.

Specifically, according to one aspect of the present application, a fourth message is received through a Uu interface, where the fourth message is used to request an RRC connection of the second node.

Specifically, according to one aspect of the present application, a fifth message and a sixth message are sent, and the fifth message and the sixth message are respectively used to release the RRC connection; the fifth message includes a first time length; the The fifth message includes that the first length of time is used to trigger the start of a second timer; the expiration value of the second timer is equal to the first length of time; the start of the second timer is separated by the The receiving moment of the sixth message is less than the expiration value of the second timer; the start of the second timer is earlier than the sending of the second message; the receiving of the sixth message is later than the sending of the second message sending; the sixth message includes a second length of time; the sixth message includes that the second length of time is used to trigger a restart of the second timer; the restart of the second timer after The expiration value is equal to the second length of time; the running state of the second timer is used for access blocking checks.

Specifically, according to one aspect of the present application, a sixth message is sent, and the sixth message is used to release the RRC connection; the receiver of the sixth message operates the first timer after receiving the sixth message , the operation is to stop or continue to run, and the operation is related to the trigger cause of the second message; when the sixth message is received, the first timer is in the running state;

Wherein, the operation in the phrase related to the triggering cause of the second message includes:

Said operation is stopping in response to receiving said sixth message when said triggering cause of said second message is for an information bit generated at said first node;

When the triggering cause of the second message is to forward information bits generated at the second node, the operation is to continue running.

Specifically, according to one aspect of the present application, a seventh message is received, where the seventh message is used to indicate the first timer.

Specifically, according to one aspect of the present application, an eighth message is sent, and the eighth message is used to agree to the RRC connection request of the second node.

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

Specifically, according to one aspect of the present application, the third node is a cell or a cell group.

Specifically, according to one aspect of the present application, the third node is a gateway.

Specifically, according to an aspect of the present application, the third node is an access point.

This application discloses a first node used for wireless communication, including:

a first receiver, receiving a first set of parameters and a first message; performing an access blocking check according to said first set of parameters; in response to performing said access blocking check, starting a first timer;

The first transmitter sends a second message, the second message is used to request an RRC connection, the second message includes at least a request reason, and the second message is used to trigger the first message; upon receiving the Operate the first timer after the first message, the operation is to stop or continue to run, and the operation is related to the triggering cause of the second message;

Wherein, the operation in the phrase related to the triggering cause of the second message includes:

When said triggering cause of said second message is for an information bit generated at said first node, said operation is stopping in response to receiving said first message;

When the triggering cause of the second message is to forward information bits generated at the second node, the operation is to continue running.

The present application discloses a second node used for wireless communication, including:

a first node, receiving a first set of parameters and a first message; performing an access blocking check according to said first set of parameters; in response to performing said access blocking check, starting a first timer;

The first node sends a second message, the second message is used to request an RRC connection, the second message includes at least a request reason, and the second message is used to trigger the first message; upon receiving the Operating the first timer after the first message, the operation is to stop or continue to run, and the operation is related to the triggering cause of the second message;

Wherein, the operation in the phrase related to the triggering cause of the second message includes:

When said triggering cause of said second message is for an information bit generated at said first node, said operation is stopping in response to receiving said first message;

When the triggering cause of the second message is to forward information bits generated at the second node, the operation is to continue running.

The present application discloses a third node used for wireless communication, including:

A third transmitter, sending a first set of parameters and a first message; the sender of the second message performs an access blocking check according to said first set of parameters; in response to performing said access blocking check, starts a first timer ;

A third receiver, receiving the second message, the second message is used to request an RRC connection, the second message includes at least a request reason, and the second message is used to trigger the first message; The sender of the second message operates the first timer after receiving the first message, the operation is to stop or continue to run, and the operation is related to the triggering cause of the second message;

Wherein, the operation in the phrase related to the triggering cause of the second message includes:

When said triggering cause of said second message is for an information bit generated at said first node, said operation is stopping in response to receiving said first message;

When the triggering cause of the second message is to forward information bits generated at the second node, the operation is to continue running.

As an embodiment, compared with the traditional solution, this application has the following advantages: the method proposed by this application can make the access control checks performed by the remote UE and the relay UE relatively independent when requesting RRC connection; including whether to allow The remote UE access is determined by the remote UE, regardless of whether the relay UE is in the access blocking state. The relay UE will neither prevent the remote UE from accessing because of its own access blocking state. The access of the relay UE triggered by the access request of the remote UE and the requirement of data forwarding will not affect the access blocking state of the relay UE.

As an embodiment, compared with the traditional solution, the present application has the following advantages: unified access control is executed and guaranteed, and access blocking caused by the access triggered by the access of the relay node due to the access of the remote UE is avoided be circumvented. It is beneficial to alleviate network congestion and ensure fairness of access in a congested state.

As an embodiment, compared with the traditional solution, this application has the following advantages: the relay node notifies the network of its own access blocking situation, which is beneficial for the network to schedule it, for example, when it is still in access blocking, only the remote The data of the terminal UE is not scheduled to relay the data of the UE, which ensures fairness.

As an embodiment, compared with the traditional solution, the present application has the following advantages: the access of the remote UE only depends on the access control check of the remote UE, which helps to avoid repeated blocking and ensures the quality of service of the remote UE.

As an embodiment, compared with the traditional solution, the present application has the following advantages: the RRC connection requested by the relay node for forwarding the data of the remote UE uses a special request reason, which facilitates the identification of the access reason by the network.

Description of drawings

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

FIG. 1 shows a flow chart of receiving a first parameter set and a first message and sending a second message according to an embodiment of the present application;

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

FIG. 3 shows a schematic diagram of an embodiment of a wireless protocol architecture of a user plane and a control plane according to an embodiment of the present application;

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

Figure 5 shows a flow chart of transmission according to one embodiment of the present application;

Figure 6 shows a flow chart of transmission according to one embodiment of the present application;

FIG. 7 shows a schematic diagram in which the third message is used to determine the value of the first field according to an embodiment of the present application;

FIG. 8 shows a schematic diagram in which a seventh message is used to indicate a first timer according to an embodiment of the present application;

Fig. 9 illustrates a schematic diagram of a processing device used in a first node according to an embodiment of the present application;

FIG. 10 illustrates a schematic diagram of a processing device used in a second node according to an embodiment of the present application;

Fig. 11 illustrates a schematic diagram of a processing device used in a second node according to an embodiment of the present application;

Detailed ways

The technical solutions of the present application will be described in further detail below in conjunction with the accompanying drawings. It should be noted that, in the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined arbitrarily.

Example 1

Embodiment 1 illustrates a flowchart of receiving a first parameter set and a first message and sending a second message according to an embodiment of the present application, as shown in FIG. 1 . In the accompanying drawing 1, each block represents a step, and it should be emphasized that the order of the blocks in the figure does not represent the temporal sequence of the steps represented.

In Embodiment 1, the first node in this application receives the first parameter set in step 101; sends the second message in step 102; receives the first message in step 103;

Wherein, the first node performs an access blocking check according to the first parameter set; as a response to performing the access blocking check, a first timer is started; the second message is used to request an RRC connection, and the first The second message includes at least a request reason, the second message is used to trigger the first message; the first timer is operated after receiving the first message, the operation is to stop or continue to run, the operation It is related to the triggering reason of the second message; the phrase described operation is related to the triggering reason of the second message includes:

When said triggering cause of said second message is for an information bit generated at said first node, said operation is stopping in response to receiving said first message;

When the triggering cause of the second message is to forward information bits generated at the second node, the operation is to continue running.

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

As an embodiment, the second node is a UE.

As an embodiment, the interface through which the first node communicates with the second node is a PC5 interface.

As an embodiment, the first node is a relay node of the second node.

As an embodiment, the first node is an L2 relay node of the second node.

As an embodiment, the first node is a layer 2 relay node of the second node.

As an embodiment, the first node and the second node communicate using a secondary link.

As an embodiment, the first message is sent through a Uu interface.

As an embodiment, the first message includes an RRC message.

As an embodiment, the first message is a downlink message.

As an embodiment, the first message includes RRCSetup.

As an embodiment, the first message includes RRCResume.

As an embodiment, the first message includes RRCRelease.

As an embodiment, the first message includes RRCConnectionSetup.

As an embodiment, the first message includes RRCConnectionResume.

As an embodiment, the first message includes RRCConnectionRelease.

As an embodiment, the physical channel occupied by the first message includes a PDSCH (Physical Downlink Shared Channel, Physical Downlink Shared Channel).

As an embodiment, the logical channel occupied by the first message includes a CCCH (Common Control Channel, common control channel).

As an embodiment, the logical channel occupied by the first message includes a DCCH (Dedicated Control Channel, dedicated control channel).

As an embodiment, the bearer occupied by the first message includes SRB0.

As an embodiment, the bearer occupied by the first message includes SRB1.

As an embodiment, the receiving of the first message is used to trigger the behavior to operate the first timer.

As an embodiment, the first message is used to feed back the second message.

As a sub-embodiment of the above embodiment, the second message is RRCSetupRequest, and the first message is RRCSetup.

As a sub-embodiment of the above embodiment, the second message is RRCResumeRequest, and the first message is RRCSetup.

As a sub-embodiment of the above embodiment, the second message is RRCResumeRequest, and the first message is RRCResume.

As a sub-embodiment of the above embodiment, the second message is RRCResumeRequest, and the first message is RRCRelease.

As a sub-embodiment of the above embodiment, the second message is RRCConnectionSetupRequest, and the first message is RRCConnectionSetup.

As a sub-embodiment of the above embodiment, the second message is RRCConnectionResumeRequest, and the first message is RRCConnectionSetup.

As a sub-embodiment of the above embodiment, the second message is RRCConnectionResumeRequest, and the first message is RRCConnectionResume.

As a sub-embodiment of the above embodiment, the second message is RRCConnectionResumeRequest, and the first message is RRCConnectionRelease.

As an embodiment, the first parameter set includes blocking parameters.

As an embodiment, the first parameter set includes a unified access blocking (UAC) parameter.

As an embodiment, the first parameter set includes uac-BarringInfo.

As an embodiment, the first parameter set includes uac-BarringForCommon.

As an embodiment, the first parameter set includes uac-BarringPerPLMN-List.

As an embodiment, the first parameter set includes uac-BarringInfoSetList.

As an embodiment, the first parameter set includes uac-AccessCategory1-SelectionAssistanceInfo.

As an embodiment, the phrase access barring check is an access barring check.

As an embodiment, the first parameter set includes at least one blocking parameter of an access category (Access category).

As an embodiment, the first parameter set includes at least one blocking parameter of an access identity (Access identity).

As an embodiment, the first node is configured with at least one access identity.

As an embodiment, the SIM of the first node is preconfigured with the at least one access identity.

As an embodiment, the serving cell of the first node configures the at least one access identity for the first node.

As an embodiment, the core network of the first node configures the at least one access identity for the first node.

As an embodiment, the first node is configured with at least one access category.

As an embodiment, the SIM of the first node is pre-configured with the at least one access category.

As an embodiment, the serving cell of the first node configures the at least one access category for the first node.

As an embodiment, the core network of the first node configures the at least one access category for the first node.

As an embodiment, the first timer includes T390.

As an embodiment, the first timer includes T302.

As an embodiment, the first timer includes T303.

As an embodiment, the first timer includes T305.

As an embodiment, the first timer includes T306.

As an embodiment, the first timer includes T308.

As an embodiment, the first timer includes T309.

As an embodiment, the first timer is associated with a first access category, and the trigger cause of the second message belongs to the first access category.

As an embodiment, the first timer is associated with a first access category, and the trigger cause of the second message corresponds to the first access category.

As an embodiment, the first timer is associated with a first access identity, and the trigger cause of the second message belongs to the first access identity.

As an embodiment, the first timer is associated with a first access identity, and the trigger cause of the second message corresponds to the first access identity.

As an embodiment, the second message is used for an access request.

As an embodiment, when the first timer is running, access requests or RRC connection requests for information bits generated at the first node are blocked, wherein the information bits generated for the first node The information bits belong to the first access category.

As an embodiment, when the first timer is running, access requests or RRC connection requests for information bits generated at the first node are blocked, wherein the information bits generated for the first node The information bits belong to the first access identity.

As an embodiment, when the result of the behavior performing the access blocking check is blocking, the first timer is started.

As an embodiment, when the first timer is running, an access request or an RRC connection request belonging to the first access category is blocked.

As an embodiment, when the first timer is running, an access request or an RRC connection request corresponding to the first access category is blocked.

As an embodiment, when the first timer is running, an access request or an RRC connection request belonging to the first access identity is blocked.

As an embodiment, when the first timer is running, an access request or an RRC connection request corresponding to the first access identity is blocked.

As an embodiment, whether the first timer is running is used to determine whether the access category associated with the first timer is blocked.

As an embodiment, whether the first timer is running is used to determine whether the access identity associated with the first timer is blocked.

As an embodiment, the first parameter set is used to calculate an expiration value of the first timer.

As an embodiment, the second message is an uplink message.

As an embodiment, the second message includes an RRC message.

As an embodiment, the second message is an RRC message.

As an embodiment, the second message includes RRCSetupRequest.

As an embodiment, the second message includes RRCResumeRequest.

As an embodiment, the second message includes RRCResumeRequest1.

As an embodiment, the second message includes RRCConnectionSetupRequest.

As an embodiment, the second message includes RRCConnectionSetupResume.

As an embodiment, the logical channel occupied by the second message includes CCCH.

As an embodiment, the logical channel occupied by the second message includes CCCH1.

As an embodiment, the logical channel occupied by the second message includes DCCH.

As an embodiment, the physical channel occupied by the second message includes a PUSCH (Physical uplink shared channel, physical uplink shared channel).

As an embodiment, the second message requests to establish an RRC connection.

As an embodiment, the second message requests to continue the RRC connection.

As an embodiment, the second message includes EstablishmentCause, and the EstablishmentCause indicates a reason for the request.

As an embodiment, the receiving of the first message is used to determine that the first node enters the RRC connected state.

As an embodiment, the reception of the first message is used to trigger the operation of the first timer, and the operation is to stop or continue to run.

As an embodiment, the first timer is operated after receiving the first message, the operation is to stop or continue to run, and the operation is related to the trigger cause of the second message; the behavior to continue to run The meaning is not to stop.

As an embodiment, when the triggering cause of the second message is an information bit generated at the first node, the second message is triggered by a higher layer request.

As an embodiment, when the triggering cause of the second message is an information bit generated at the first node, the second message is triggered by a request from an access stratum (Access Stratum).

As an embodiment, when the triggering cause of the second message is an information bit generated at the first node, the second message is triggered by at least one of the following: {responding to RAN paging, upon triggering RNA updates while the UE is in RRC_INACTIVE, for sidelink communication}.

As an embodiment, the sentence when the trigger reason of the second message is for the information bit generated at the first node includes the following meaning: the generator of the information bit is the first node .

As an embodiment, the sentence when the trigger reason of the second message is for the information bit generated at the first node includes the following meanings: the information bit is generated by the RRC entity of the first node or RRC layer generation.

As an embodiment, the sentence when the triggering reason of the second message is for the information bit generated at the first node includes the following meaning: the information bit is generated by the PDCP entity of the first node or PDCP layer generation.

As an embodiment, the sentence when the trigger reason of the second message is for the information bit generated at the first node includes the following meanings: the information bit is generated by the SDAP layer of the first node generate.

As an embodiment, the sentence when the trigger reason of the second message is for the information bit generated at the first node includes the following meaning: the information bit belongs to a QoS of the first node flow.

As an embodiment, the sentence when the triggering reason of the second message is for the information bit generated at the first node includes the following meaning: the information bit does not belong to other UEs using L2 relay bits.

As an embodiment, the sentence includes the following meanings when the trigger cause of the second message is for the information bits generated at the first node, the RRC connection requested by the second message is for the transmission of the The information bits generated by the first node are not for transmission of information bits from other UEs.

As an embodiment, the sentence includes the following meanings when the trigger cause of the second message is for the information bits generated at the first node, the RRC connection requested by the second message is for the transmission of the The service of the above-mentioned first node is not for transmitting the service from other UEs.

As an embodiment, the sentence includes the following meanings when the trigger reason of the second message is for information bits generated at the first node, the RRC connection requested by the second message is not for relaying .

As an embodiment, the sentence includes the following meaning when the trigger reason of the second message is for information bits generated at the first node, the RRC connection requested by the second message is not for layer 2 relay.

As an embodiment, the layer 2 relay is a first type relay.

As an embodiment, the layer 2 relay is a second type of relay.

As an embodiment, the second message includes a first field, and the first field in the second message indicates the trigger cause of the second message.

As an embodiment, the trigger reason of the second message is the request reason included in the second message.

As an embodiment, when the trigger cause of the second message is an information bit generated at the first node, the first field in the second message is generated by the first node.

As a sub-embodiment of the above-mentioned embodiment, when the triggering cause of the second message is to relay information bits generated at the second node, the first field in the second message is replaced by The second node is generated.

As a sub-embodiment of the above-mentioned embodiment, when the trigger reason of the second message is to relay information bits generated at the second node, the first field in the second message is based on An indication of the second node is generated.

As a sub-embodiment of the above-mentioned embodiment, when the trigger reason of the second message is to relay information bits generated at the second node, the first field in the second message is based on A third message sent by the second node is received and generated.

As a sub-embodiment of the above-mentioned embodiment, when the trigger reason of the second message is to relay information bits generated at the second node, the first field in the second message is reused Spare state in a Release16 message.

As a sub-embodiment of the above-mentioned embodiment, when the trigger reason of the second message is to relay information bits generated at the second node, the first field in the second message is reused The Spare state of the EstablishmentCause field in a Release16 message.

As a sub-embodiment of the above-mentioned embodiment, when the triggering cause of the second message is to relay information bits generated at the second node, the EstablishmentCause field included in the second message is set to relay or L2-relay or type II-relay or type2-relay or type1-relay or type I-relay.

As an embodiment, when the triggering reason of the second message is to forward the information bit generated at the second node, the sentence includes the following meaning: the second node is the first node A node other than the node; the purpose of the second message requesting the RRC connection is to receive and forward the information bits of the second node.

As a sub-embodiment of this embodiment, the information bits of the second node include an RLC SDU of the second node.

As a sub-embodiment of this embodiment, the information bits of the second node include an RRC message of the second node.

As a sub-embodiment of this embodiment, the information bits of the second node include a PDCP PDU of the second node.

As a sub-embodiment of this embodiment, the information bits of the second node include a PDCP SDU of the second node.

As an embodiment, the first node determines the trigger cause of the second message by receiving the third message sent by the second node.

As an embodiment, the second message and the third message use different logical channels.

As an embodiment, the second message uses SRBO.

As an embodiment, the second message and the fourth message are multiplexed in the same MAC PDU.

As an embodiment, the first message includes higher layer signaling.

As an embodiment, the first message includes RRC (Radio Resource Control, radio resource control) signaling.

As an embodiment, the first parameter set is included in SIB1.

As an embodiment, the request reason included in the second message belongs to {emergency, highPriorityAccess, mt-Access, mo-Signalling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, mps-PriorityAccess, mcs -PriorityAccess} in one.

As an embodiment, the request reason included in the second message belongs to {emergency, highPriorityAccess, mt-Access, mo-Signalling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, rna-Update, mps One of -PriorityAccess, mcs-PriorityAccess}.

As an embodiment, the request reason included in the second message belongs to one of {reconfigurationFailure, handoverFailure, otherFailure, relayreselection, relayfailure}.

As an embodiment, when the access blocking check is performed, if the first timer is not running, and the first parameter set is used to indicate the first threshold and the first blocking time, the node performing the access blocking check generating a random number, if the generated random number is smaller than the first threshold, access is allowed, and if the generated random number is not smaller than the first threshold, access is blocked and the The first timer, and the expiration value of the first timer is set as the first blocking time.

Example 2

Embodiment 2 illustrates a schematic diagram of a network architecture according to an embodiment of the present application, as shown in FIG. 2 . Figure 2 illustrates the V2X communication architecture under the 5G NR (New Radio, new air interface), LTE (Long-Term Evolution, 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 (5G System)/EPS (Evolved Packet System) or some other suitable term.

The V2X communication architecture of Embodiment 2 includes UE (User Equipment, user equipment) 201, UE 241, NG-RAN (Next Generation Radio Access Network) 202, 5GC (5G Core Network, 5G core network)/EPC (Evolved PacketCore, evolution packet core) 210 , HSS (Home Subscriber Server, Home Subscriber Server)/UDM (Unified Data Management, unified data management) 220 , ProSe function 250 and ProSe application server 230 . The V2X communication architecture can 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 can be extended to networks providing circuit-switched services or other cellular networks. NG-RAN includes NR Node B (gNB) 203 and other gNBs 204 . The gNB 203 provides user and control plane protocol termination towards the UE 201 . A gNB 203 may connect to other gNBs 204 via an Xn interface (eg, backhaul). A gNB 203 may also be called a base station, base transceiver station, radio base station, radio transceiver, transceiver function, Basic Service Set (BSS), Extended Service Set (ESS), TRP (Transmitting Receiver Node) or some other suitable terminology. The gNB203 provides an access point to the 5GC/EPC210 for the UE201. Examples of UE 201 include cellular phones, smart phones, Session Initiation Protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, non-terrestrial base station communications, satellite mobile communications, global positioning systems, multimedia devices , video devices, digital audio players (e.g., MP3 players), cameras, game consoles, drones, aircraft, NB-IoT devices, machine type communication devices, land vehicles, automobiles, wearable devices, or any Other devices with similar functions. Those skilled in the art may also refer to UE 201 as a mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, Mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client or some other suitable term. gNB203 is connected to 5GC/EPC210 through S1/NG interface. 5GC/EPC210 includes MME (Mobility Management Entity, mobility management entity)/AMF (Authentication Management Field, authentication management domain)/SMF (Session Management Function, session management function) 211. Other MME/AMF/SMF 214, S-GW (Service Gateway, service gateway)/UPF (UserPlane Function, user plane function) 212, and P-GW (Packet Date Network Gateway, packet data network gateway)/UPF 213. MME/AMF/SMF211 is a control node that handles signaling between UE201 and 5GC/EPC210. In general, the MME/AMF/SMF 211 provides bearer and connection management. All user IP (Internet Protocol, Internet Protocol) packets are transmitted through the S-GW/UPF212, and the S-GW/UPF212 itself is connected to the P-GW/UPF213. P-GW provides UE IP address allocation and other functions. P-GW/UPF 213 connects to Internet service 230 . The Internet service 230 includes Internet protocol services corresponding to operators, and specifically may include Internet, Intranet, IMS (IP Multimedia Subsystem, IP Multimedia Subsystem) and packet-switched streaming services. The ProSe function 250 is a logical function for network-related behaviors required by Proximity-basedService (ProSe, Proximity-basedService); including DPF (Direct Provisioning Function, direct provisioning function), direct discovery name management function (Direct Discovery Name Management Function), EPC-level Discovery ProSe Function (EPC-level Discovery ProSe Function), etc. The ProSe application server 230 has functions such as storing EPC ProSe user IDs, mapping between application layer user IDs and EPC ProSe user IDs, and allocating code suffix pools restricted by ProSe.

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 respectively connected to the UE 201 and the UE 241 through a PC3 reference point.

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

As an embodiment, the ProSe application server 230 is respectively connected to the ProSe application of the UE 201 and the ProSe application of the UE 241 through the PC1 reference point.

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

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

As an embodiment, the third node gNB203 in this application.

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

As an embodiment, the radio link from the UE 201 to the NR Node B is an uplink.

As one embodiment, the wireless link from NR Node B to UE 201 is downlink.

As an embodiment, the UE 201 supports relay transmission.

As an embodiment, the UE241 supports relay transmission.

As an embodiment, the UE 201 is a vehicle including a car.

As an embodiment, the UE 241 is a vehicle including a car.

As an embodiment, the gNB203 is a macrocell (MarcoCellular) base station.

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

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

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

As an embodiment, the gNB203 is a satellite device.

Example 3

Embodiment 3 shows a schematic diagram of an embodiment of a radio protocol architecture of a user plane and a control plane according to the present application, as shown in FIG. 3 . FIG. 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for the user plane 350 and the control plane 300. FIG. 3 shows three layers for the first node (UE, gNB or satellite or aircraft in NTN) and the second Radio protocol architecture of a node (gNB, UE or satellite or aircraft in NTN), or control plane 300 between two UEs: Layer 1, Layer 2 and Layer 3. Layer 1 (L1 layer) is the lowest layer and implements various PHY (Physical Layer) signal processing functions. The L1 layer will be referred to herein as PHY 301 . Layer 2 (L2 layer) 305 is above the PHY 301 and is responsible for the link between the first node and the second node and the two UEs through the PHY 301 . The L2 layer 305 includes a MAC (Medium Access Control, Media Access Control) sublayer 302, an RLC (Radio Link Control, Radio Link Layer Control Protocol) sublayer 303, and a PDCP (Packet Data Convergence Protocol, packet data convergence protocol) sublayer 304 , these sublayers terminate at the second node. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by encrypting data packets, and provides handoff support to a first node between a second node. The RLC sublayer 303 provides segmentation and reassembly of upper layer packets, retransmission of lost packets, and reordering of packets to compensate for out-of-order reception due to HARQ. The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating various radio resources (eg resource blocks) in a cell among the first nodes. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control, radio resource control) sublayer 306 in layer 3 (L3 layer) in the control plane 300 is responsible for obtaining radio resources (that is, radio bearers) and using the RRC signal between the second node and the first node command to configure the lower layer. The PC5-S (PC5 Signaling Protocol, PC5 signaling protocol) sublayer 307 is responsible for processing the signaling protocol of the PC5 interface. The radio protocol architecture of the user plane 350 includes layer 1 (L1 layer) and layer 2 (L2 layer), the radio protocol architecture for the first node and the second node in the user plane 350 is for the physical layer 351, the L2 layer 355 The PDCP sublayer 354, the RLC sublayer 353 in the L2 layer 355, and the MAC sublayer 352 in the L2 layer 355 are substantially the same as the corresponding layers and sublayers in the control plane 300, but the PDCP sublayer 354 also provides for upper Layer packet header compression to reduce radio transmission overhead. The L2 layer 355 in the user plane 350 also includes a SDAP (Service Data Adaptation Protocol, Service Data Adaptation Protocol) sublayer 356, and the SDAP sublayer 356 is responsible for the mapping between the QoS flow and the data radio bearer (DRB, Data RadioBearer), To support business diversity. Although not shown, the first node may have several upper layers above the L2 layer 355 . It also includes a network layer (eg IP layer) terminated at the P-GW on the network side and an application layer terminated at the other end of the connection (eg remote UE, server, etc.). For the UE involved in the relay service, its control plane may also include an adaptation sublayer AP308, and its user plane may also include an adaptation sublayer AP358. The introduction of the adaptation layer helps lower layers, such as the MAC layer, such as the RLC layer , to multiplex and/or differentiate data from multiple source UEs. In addition, adaptation sublayers AP308 and AP358 can also be used as sublayers in PDCP304 and PDCP354 respectively. The RRC306 can be used to process the RRC signaling of the Uu interface and the signaling of the PC5 interface.

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

As an embodiment, the wireless protocol architecture in Fig. 3 is applicable to the second node in this application.

As an embodiment, the wireless protocol architecture in Fig. 3 is applicable to the third node in this application.

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

As an embodiment, the second message in this application is generated in RRC306.

As an embodiment, the third message in this application is generated by RRC306 or PC5-S307.

As an embodiment, the fourth message in this application is generated in RRC306.

As an embodiment, the fifth message in this application is generated in RRC306.

As an embodiment, the sixth message in this application is generated in RRC306.

As an embodiment, the seventh message in this application is generated in RRC306.

As an embodiment, the eighth message in this application is generated in RRC306.

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

As an embodiment, the second parameter set in this application is generated in RRC306 or PC5-S307.

Example 4

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

The first 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 antenna 452 .

Second communications device 410 includes controller/processor 475 , memory 476 , receive processor 470 , transmit processor 416 , multi-antenna receive processor 472 , multi-antenna transmit processor 471 , transmitter/receiver 418 and antenna 420 .

In transmission from said second communication device 410 to said first communication device 450 , at said second communication device 410 upper layer data packets from the core network are provided to a controller/processor 475 . Controller/processor 475 implements the functionality of the L2 layer. In transmission from the second communications device 410 to the first communications device 450, the controller/processor 475 provides header compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels. Multiplexing, and allocation of radio resources to said 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 (ie, physical layer). The transmit processor 416 implements encoding and interleaving to facilitate forward error correction (FEC) at the second communication device 410, and based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift Mapping of signal clusters for keying (QPSK), M phase shift keying (M-PSK), M quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding on the coded and modulated symbols, including codebook-based precoding and non-codebook-based precoding, and beamforming processing to generate one or more spatial streams. The transmit processor 416 then maps each spatial stream to subcarriers, multiplexes with a reference signal (e.g., pilot) in the time and/or frequency domain, and then uses an inverse fast Fourier transform (IFFT) to generate A physical channel that carries a time-domain multi-carrier symbol stream. Then the multi-antenna transmit processor 471 performs a transmit analog precoding/beamforming operation on the time-domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multi-carrier symbol stream provided by the multi-antenna transmit processor 471 into an RF stream, which is then provided to a different antenna 420 .

In transmission from said second communication device 410 to said first communication device 450 , at said first communication device 450 each receiver 454 receives a signal via its respective antenna 452 . Each receiver 454 recovers the information modulated onto an RF carrier and converts the RF stream to a baseband multi-carrier symbol stream that is provided to a receive processor 456 . Receive processor 456 and multi-antenna receive processor 458 implement various signal processing functions of the L1 layer. The multi-antenna receive processor 458 performs receive analog precoding/beamforming operations on the baseband multi-carrier symbol stream from the receiver 454 . Receive processor 456 converts the baseband multi-carrier symbol stream after the receive analog precoding/beamforming operation from the time domain to the frequency domain using a Fast Fourier Transform (FFT). In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receiving processor 456, wherein the reference signal will be used for channel estimation, and the data signal is recovered in the multi-antenna detection in the multi-antenna receiving processor 458. Any spatial stream for which the first communication device 450 is a destination. The symbols on each spatial stream are demodulated and recovered in receive processor 456 and soft decisions are generated. The receive processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communications device 410 on the physical channel. The upper layer data and control signals are then provided to the controller/processor 459 . Controller/processor 459 implements the functions of the L2 layer. Controller/processor 459 can be associated with memory 460 that stores program codes and data. Memory 460 may be referred to as a computer-readable medium. In transmission from said second communication device 410 to said second communication device 450, 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 transmission from said first communication device 450 to said second communication device 410 , at said first communication device 450 a data source 467 is used 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 function at the second communications device 410 described in the transmission from the second communications device 410 to the first communications device 450, the controller/processor 459 implements a header based on radio resource allocation Compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels, implementing L2 layer functions for user plane and control plane. 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 and channel coding processing, and the multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing, and then transmits The processor 468 modulates the generated spatial stream into a multi-carrier/single-carrier symbol stream, which is provided to different antennas 452 via the transmitter 454 after undergoing analog precoding/beamforming operations in the multi-antenna transmit processor 457 . Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into an RF symbol stream, and then provides it to the 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 that in the transmission from the second communication device 410 to the first communication device 450 The receive function at the first communication device 450 is described in the transmission. Each receiver 418 receives radio frequency signals through its respective antenna 420 , converts the received radio frequency signals to baseband signals, and provides the baseband signals to multi-antenna receive processor 472 and receive processor 470 . The receive processor 470 and the multi-antenna receive processor 472 jointly implement the functions of the L1 layer. Controller/processor 475 implements L2 layer functions. Controller/processor 475 can be associated with memory 476 that stores program codes and data. Memory 476 may be referred to as a computer-readable medium. In transmission from said first communication device 450 to said second communication device 410, 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 UE450. Upper layer packets from controller/processor 475 may be provided to the core network.

As an embodiment, the first communication device 450 device includes: at least one processor and at least one memory, the at least one memory includes computer program code; the at least one memory and the computer program code are configured to be compatible with the The first communication device 450 device at least: receives a first parameter set, performs an access blocking check according to the first parameter set; as a response to performing the access blocking check, starts the first A timer; sending a second message, the second message is used to request RRC connection, the second message includes at least a request reason, the second message is used to trigger the first message; receiving the first message ; operate the first timer after receiving the first message, the operation is to stop or continue to run, and the operation is related to the trigger cause of the second message; wherein, the operation in the phrase is related to the The triggering cause of the second message includes: when the triggering cause of the second message is an information bit generated at the first node, as a response to receiving the first message, the operation is to stop ; When the triggering reason of the second message is to forward the information bits generated at the second node, the operation is to continue running.

As an embodiment, the first communication device 450 includes: a memory storing a computer-readable instruction program, and the computer-readable instruction program generates an action when executed by at least one processor, and the action includes: receiving a first a set of parameters, performing an access blocking check according to said first set of parameters; starting a first timer in response to performing said access blocking check; sending a second message, said second message being used to request an RRC connection , the second message includes at least a request reason, the second message is used to trigger the first message; receiving the first message; operating the first timer after receiving the first message, the operation is to stop or continue running, and the operation is related to the triggering cause of the second message; wherein, the phrase that the operation is related to the triggering reason of the second message includes: when the triggering of the second message The reason is for the information bit generated by the first node, as a response to receiving the first message, the operation is to stop; when the trigger reason for the second message is to forward the The operation is to continue running while the node generates information bits.

As an embodiment, the second communication device 410 includes: at least one processor and at least one memory, the at least one memory includes computer program code; the at least one memory and the computer program code are configured to be compatible with the at least one of the processors described above. The second communication device 410 means at least: sending a first parameter set; receiving a second message; sending the first message; the sender of the second message performs an access blocking check according to the first parameter set; A response to the access blocking check starts a first timer; the second message is used to request an RRC connection, the second message includes at least a request reason, and the second message is used to trigger the first message ; The sender of the second message operates the first timer after receiving the first message, the operation is to stop or continue to run, and the operation is related to the triggering cause of the second message; wherein, The phrase that the operation is related to the triggering cause of the second message includes: when the triggering cause of the second message is an information bit generated at the first node, as receiving the first message In response to a response, the operation is to stop; when the trigger reason of the second message is to forward the information bit generated at the second node, the operation is to continue running.

As an embodiment, the second communication device 410 includes: a memory storing a computer-readable instruction program, and the computer-readable instruction program generates an action when executed by at least one processor, and the action includes: sending A first set of parameters; receiving a second message; sending a first message; the sender of said second message performs an access blocking check according to said first set of parameters; in response to performing said access blocking check, starting a first timer; the second message is used to request RRC connection, the second message includes at least a request reason, the second message is used to trigger the first message; the sender of the second message is receiving The first timer is operated after the first message, the operation is to stop or continue to run, and the operation is related to the trigger cause of the second message; wherein, the operation in the phrase is related to the second The triggering reason of the message includes: when the triggering reason of the second message is an information bit generated at the first node, as a response to receiving the first message, the operation is to stop; when the The triggering reason of the second message is to forward the information bits generated by the second node, and the operation is to continue running.

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

As an embodiment, the second communication device 450 corresponds to the second node in this application.

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

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

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

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

As an embodiment, the first communication device 410 is an access point.

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

As one example, receiver 456 (including antenna 460), receive processor 452 and controller/processor 490 are used herein to receive the first message.

As one example, receiver 456 (including antenna 460), receive processor 452 and controller/processor 490 are used herein to receive the third message.

As one example, receiver 456 (including antenna 460), receive processor 452 and controller/processor 490 are used herein to receive the fifth message.

As one example, receiver 456 (including antenna 460), receive processor 452 and controller/processor 490 are used in this application to receive the sixth message.

As one example, receiver 456 (including antenna 460), receive processor 452 and controller/processor 490 are used herein to receive the eighth message.

As one example, receiver 456 (including antenna 460), receive processor 452 and controller/processor 490 are used in this application to receive the second set of parameters.

As an example, transmitter 456 (including antenna 460), transmit processor 455 and controller/processor 490 are used in this application to transmit the second message.

As an example, the transmitter 456 (including the antenna 460), the transmit processor 455 and the controller/processor 490 are used in this application to transmit the third message.

As an example, the transmitter 456 (including the antenna 460), the transmit processor 455 and the controller/processor 490 are used in this application to transmit the fourth message.

As an example, the transmitter 456 (including the antenna 460), the transmit processor 455 and the controller/processor 490 are used in this application to transmit the second set of parameters.

As an example, the transmitter 416 (including the antenna 420), the transmit processor 412 and the controller/processor 440 are used in this application to transmit the first message.

As an example, the transmitter 416 (including the antenna 420), the transmit processor 412 and the controller/processor 440 are used in this application to transmit the fifth message.

As an example, the transmitter 416 (including the antenna 420), the transmit processor 412 and the controller/processor 440 are used in this application to transmit the sixth message.

As an example, the transmitter 416 (including the antenna 420), the transmit processor 412 and the controller/processor 440 are used in this application to transmit the eighth message.

As an example, the transmitter 416 (including the antenna 420), the transmit processor 412 and the controller/processor 440 are used in this application to transmit the first set of parameters.

As one example, receiver 416 (including antenna 420), receive processor 412 and controller/processor 440 are used herein to receive the second message.

As one example, receiver 416 (including antenna 420), receive processor 412 and controller/processor 440 are used in this application to receive the fourth message.

Example 5

Embodiment 5 illustrates a flow chart of wireless signal transmission according to an embodiment of the present application, as shown in FIG. 5 . In Figure 5, U01 corresponds to the first node of this application, U02 corresponds to the second node of this application, and U03 corresponds to the third node of this application. It is particularly noted that the sequence in this example does not limit the signal transmission in this application Sequence and sequence of implementation, where steps within F51 and F52 are optional.

For the first node U01 , the first parameter set is received in step S5101; the second parameter set is sent in step S5102; the third message is received in step S5103; the second message is sent in step S5104; A message; send the fourth message in step S5106; send the seventh message in step S5107.

For the second node U02 , the second parameter set is received in step S5201; the third message is sent in step S5202; and the eighth message is received in step S5203.

For the third node U03 , send the first parameter set in step S5301; receive the second message in step S5302; send the first message in step S5303; receive the fourth message in step S5304; send the eighth message in step S5305 message; the seventh message is received in step S5306.

In Embodiment 5, the first node U01 performs an access blocking check according to the first parameter set; as a response to performing the access blocking check, a first timer is started; the second message is used for RRC connection is requested, the second message includes at least a request reason, the second message is used to trigger the first message; the first timer is operated after receiving the first message, the operation is to stop or continue run, the operation is related to the triggering cause of the second message;

Wherein, the operation in the phrase related to the triggering cause of the second message includes:

When said triggering cause of said second message is for an information bit generated at said first node, said operation is stopping in response to receiving said first message;

When the triggering cause of the second message is to forward information bits generated at the second node, the operation is to continue running.

As an embodiment, the first node U01 is a relay, the second node U02 is a remote UE, and the third node U03 is a base station or a cell or a cell group.

As an embodiment, the first parameter set is sent by broadcasting.

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

As an embodiment, the first parameter set is included in SIB1.

As an embodiment, the second parameter set is sent by broadcasting.

As an embodiment, the second parameter set is sent in a unicast manner.

As an embodiment, the second parameter set is sent in a multicast manner.

As an embodiment, the second parameter set is sent through the PC5 interface.

As an embodiment, the second parameter set is sent through a PC5-RRC message.

As an embodiment, the second parameter set is sent through a PC5-S message.

As an embodiment, the second parameter set is the same as the first parameter set.

As an embodiment, the second parameter set is a subset of the first parameter set.

As an embodiment, the second parameter set includes a unified access check (UAC) parameter.

As an embodiment, the second parameter set only includes parameters corresponding to the unblocked access identity of the first node U01 in the first parameter set.

As an embodiment, the second parameter set only includes parameters corresponding to the unblocked access category of the first node U01 in the first parameter set.

As an embodiment, the second parameter set belongs to a discovery message.

As an embodiment, the second parameter set belongs to the Direct Link Establishment message.

As an embodiment, the second parameter set is used to perform an access blocking check for sending the third message.

As a sub-embodiment of the above embodiment, the second node U02 needs to first perform a blocking check before sending the third message.

As a sub-embodiment of the above embodiment, the second node U02 first needs to perform a blocking check according to the second parameter set before sending the third message.

As a sub-embodiment of the above embodiment, the second node U02 needs to first perform a blocking check before sending the third message, and when the result of the access check is to allow access, the second node U02 sends The third message.

As a sub-embodiment of the above embodiment, the second node U02 needs to first perform a blocking check before sending the third message, and when the result of the access check is to block access, as the result of the access check In response, the second node U02 starts a T390 timer, and the second node U02 aborts sending the third message.

As a sub-embodiment of the above embodiment, the second node U02 needs to first perform a blocking check before sending the third message, and when the result of the access check is to block access, as the result of the access check In response, the second node U02 starts a T390 timer, and the second node U02 gives up sending the third message until the T390 timer expires and then tries again.

As an embodiment, the second node U02 sends the third message through the PC5 interface, and the third message is used to request the RRC connection of the second node U02.

As a sub-embodiment of the above embodiment, the second node U02 sends the third message through a default layer 2 configuration.

As a sub-embodiment of the above embodiment, the second node U02 sends the third message through a default layer 2 configuration, and the default layer 2 configuration includes a logical channel identity.

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

As a sub-embodiment of the above embodiment, the third message includes a reason for the request.

As a sub-embodiment of the above embodiment, the third message includes RRCSetupRequest.

As a sub-embodiment of the above embodiment, the third message includes RRCResumeRequest.

As a sub-embodiment of the above embodiment, the third message includes RRCResumeRequest1.

As a sub-embodiment of the above embodiment, the third message includes RRCConnectionSetupRequest.

As a sub-embodiment of the above embodiment, the third message includes RRCConnectionResumeRequest.

As a sub-embodiment of the above embodiment, the third message is a PC5-S message.

As a sub-embodiment of the above embodiment, the request reason included in the third message belongs to {emergency, highPriorityAccess, mt-Access, mo-Signalling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, One of mps-PriorityAccess, mcs-PriorityAccess}.

As a sub-embodiment of the above embodiment, the request reason included in the third message belongs to {emergency, highPriorityAccess, mt-Access, mo-Signalling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, One of rna-Update, mps-PriorityAccess, mcs-PriorityAccess}.

As a sub-embodiment of the above embodiment, the request reason included in the third message belongs to one of {reconfigurationFailure, handoverFailure, otherFailure, relayreselection, relayfailure}.

As a sub-embodiment of the above embodiment, the third message indicates a request to establish a new RRC connection.

As a sub-embodiment of the above embodiment, the third message indicates a request to re-establish the RRC connection.

As a sub-embodiment of the above embodiment, the third message indicates a request to continue the RRC connection.

As a sub-embodiment of the above embodiment, the third message indicates a request to establish a new RRC connection.

As a sub-embodiment of the above embodiment, the third message includes c-RNTI and shortMAC-I, and the c-RNTI and shortMAC-I are encrypted.

As a sub-embodiment of the above embodiment, the third message includes c-RNTI and shortMAC-I, and the c-RNTI and shortMAC-I are integrity protected.

As a sub-embodiment of the above embodiment, the third message includes c-RNTI and shortMAC-I, and the c-RNTI and shortMAC-I are encrypted by the PDCP layer.

As a sub-embodiment of the above embodiment, the third message includes c-RNTI and shortMAC-I, and the c-RNTI and shortMAC-I are encrypted or scrambled by a MAC layer or a physical layer.

As a sub-embodiment of the above embodiment, the third message includes a container, and the container includes RRCResumeRequest.

As a sub-embodiment of the above embodiment, the third message includes a container, and the container includes RRCReestablishmentRequest.

As a sub-embodiment of the above embodiment, the third message includes a container, and the container includes RRCReestablishmentRequest1.

As a sub-embodiment of the above embodiment, the third message is sent using SRB0.

As a sub-embodiment of the above embodiment, the third message is sent using SRB1.

As a sub-embodiment of the above embodiment, the third message is sent using SRB2.

As a sub-embodiment of the above embodiment, the third message is sent using SRB3.

As a sub-embodiment of the above embodiment, the third message is sent using SRB5.

As a sub-embodiment of the above embodiment, the third message includes resumeIdentity and resumeMAC-I, and the resumeIdentity and resumeMAC-I are encrypted.

As a sub-embodiment of the above embodiment, the third message includes resumeIdentity and resumeMAC-I, and the resumeIdentity and resumeMAC-I are integrity protected.

As a sub-embodiment of the above embodiment, the third message includes resumeIdentity and resumeMAC-I, and the resumeIdentity and resumeMAC-I are encrypted by the PDCP layer.

As a sub-embodiment of the above embodiment, the third message includes resumeIdentity and resumeMAC-I, and the resumeIdentity and resumeMAC-I are encrypted or scrambled by the MAC layer or the physical layer.

As a sub-embodiment of the above embodiment, the third message uses a radio bearer other than SRB0.

As a sub-embodiment of the above embodiment, the third message is not encrypted.

As a sub-embodiment of the above embodiment, the third message requests an RRC connection via a relay.

As a sub-embodiment of the above embodiment, the third message indicates that the requested RRC connection is through a relay.

As an embodiment, receiving the third message triggers the first node U01 to send the second message.

As an embodiment, when the third message is received, the first node U01 is in an RRC state other than the RRC connected state.

As an embodiment, the second message triggers the first message.

As an embodiment, the first message is used to agree to the RRC connection requested by the second message.

As an embodiment, the first message is used to release the RRC connection of the first node U01.

As an embodiment, the second message is msg3 in the random access process, and the first message is msg4 in the random access process.

As an embodiment, the second message is msgA in the random access process, and the first message is msgB in the random access process.

As an embodiment, the fourth message is generated by the third message, and the fourth message is used to request the RRC connection of the second node.

As a sub-embodiment of this embodiment, all bits of the fourth message are the same as all bits of the third message.

As a sub-embodiment of this embodiment, the fourth message includes c-RNTI and shortMAC-I, and the c-RNTI and shortMAC-I are from the third message.

As a sub-embodiment of this embodiment, the fourth message includes c-RNTI and shortMAC-I, and the c-RNTI and shortMAC-I are from the third message, and the c-RNTI and The shortMAC-I is not encrypted.

As a sub-embodiment of this embodiment, the fourth message includes resumeIdentity and resumeMAC-I, and the resumeIdentity and resumeMAC-I are from the third message.

As a sub-embodiment of this embodiment, the fourth message includes resumeIdentity and resumeMAC-I, and the resumeIdentity and resumeMAC-I are from the third message, and the resumeIdentity and resumeMAC-I are not is encrypted.

As a sub-embodiment of this embodiment, the EstablishmentCause included in the fourth message is the same as the EstablishmentCause included in the third message.

As a sub-embodiment of this embodiment, the ResumeCause included in the fourth message is the same as the ResumeCause included in the third message.

As a sub-embodiment of this embodiment, the REEstablishmentCause included in the fourth message is the same as the REEstablishmentCause included in the third message.

As an embodiment, the request reason included in the third message and the fourth message is the same.

As an embodiment, the fourth message includes an RRC message.

As a sub-embodiment of the above embodiment, the fourth message includes RRCSetupRequest.

As a sub-embodiment of the above embodiment, the fourth message includes RRCResumeRequest.

As a sub-embodiment of the above embodiment, the fourth message includes RRCResumeRequest1.

As a sub-embodiment of the above embodiment, the fourth message includes RRCConnectionSetupRequest.

As a sub-embodiment of the above embodiment, the fourth message includes RRCConnectionResumeRequest.

As a sub-embodiment of the above embodiment, the fourth message includes UEAssistanceInformation.

As a sub-embodiment of the above embodiment, the fourth message includes ULInformationTransfer.

As an embodiment, the fourth message is sent through the Uu interface.

As a sub-embodiment of the above embodiment, the third message is sent using SRB0.

As a sub-embodiment of the above embodiment, the third message is sent using SRB1.

As a sub-embodiment of the above embodiment, the third message is sent using SRB2.

As a sub-embodiment of the above embodiment, the third message is sent using SRB3.

As a sub-embodiment of the above embodiment, the third message is sent using SRB5.

As an embodiment, the fourth message does not use encryption.

As an embodiment, the fourth message is transmitted in a transparent manner.

As an embodiment, the fourth message is included in a container of an RRC message.

As an embodiment, the fourth message is included in the container of the RRC message from the first node U01 to the serving cell.

As an embodiment, the fourth message includes an RRC container carrying bits of the third message.

As an embodiment, the fourth message includes an RRC container carrying all bits of the third message.

As an embodiment, the eighth message is an RRC message.

As an embodiment, the eighth message is used to feed back the fourth message.

As an embodiment, the eighth message is used to feed back the third message.

As an embodiment, the eighth message is forwarded to the second node U02 through the first node U01.

As an embodiment, the SRB used by the eighth message is SRB0.

As an embodiment, the eighth message includes RRCSetup.

As an embodiment, the eighth message includes RRCResume.

As an embodiment, the eighth message includes RRCReestablishment.

As an embodiment, the eighth message includes RRCRelease.

As an embodiment, the eighth message includes RRCReject.

As an embodiment, the seventh message includes an RRC message.

As a sub-embodiment of the above embodiment, the seventh message includes UEAssistanceInformation.

As a sub-embodiment of the above embodiment, the seventh message includes ULInformationTransfer.

As a sub-embodiment of the above embodiment, the seventh message includes UEInformationResponse.

As a sub-embodiment of the above embodiment, the seventh message includes RRCReconfigurationComplete.

As a sub-embodiment of the above embodiment, the seventh message includes RRCConnectionReconfigurationComplete.

As an embodiment, the seventh message belongs to msgA.

As an embodiment, the physical channel occupied by the seventh message includes PUSCH.

As an embodiment, the physical channel occupied by the seventh message includes a PUCCH (Physical Uplink Control Channel, Physical Uplink Control Channel).

As an embodiment, the random access procedure to which the second message belongs uses a dedicated time-frequency resource to indicate that the trigger cause of the second message is generated for forwarding by a node other than the first node U01 information bits.

As an embodiment, the random access procedure to which the second message belongs uses a dedicated Preamble to indicate that the triggering cause of the second message is to forward information bits generated by a node other than the first node U01 .

Example 6

Embodiment 6 illustrates a flow chart of wireless signal transmission according to an embodiment of the present application, as shown in FIG. 6 . In Figure 6, U11 corresponds to the first node of this application, and U13 corresponds to the third node of this application. In particular, the order in this example does not limit the order of signal transmission and implementation in this application. The steps are optional; Embodiment 6 is based on Embodiment 5, and the parts that are required in Embodiment 6 but not shown can refer to Embodiment 5.

For the first node U11 , the fifth message is received in step S6101; the second message is sent in step S6102; the first message is received in step S6103; the sixth message is received in step S6104.

For the third node U13 , send the fifth message in step S6301; receive the second message in step S6302; send the first message in step S6303; send the sixth message in step S6304.

As an embodiment, the fifth message is used to release the RRC connection; the fifth message includes the first time length; the fifth message includes the first time length and is used to trigger the start of the second timer ; The expiration value of the second timer is equal to the first time length; The starting distance of the second timer is less than the expiration value of the second timer from the receiving moment of the sixth message; The timer is started earlier than the sending of the second message.

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

As a sub-embodiment of the above embodiment, the fifth message includes RRCRelease.

As a sub-embodiment of the above embodiment, the fifth message includes RRCReject.

As a sub-embodiment of the above embodiment, the fifth message includes RRCConnectionRelease.

As a sub-embodiment of the above embodiment, the fifth message includes RRCConnectionReject.

As a sub-embodiment of the above embodiment, the first time length included in the fifth message is waittime.

As a sub-embodiment of the above embodiment, the value range of the first time length included in the fifth message is X1 seconds, where X1 is a positive integer between 1 and 16; for example, X2 is equal to 1, for example X1 is equal to 16.

As a sub-embodiment of the above embodiment, the second timer includes T302.

As a sub-embodiment of the above embodiment, the second timer includes one of {T303, T304, T305, T306, T307, T308, T309}.

As an embodiment, the receiving of the fifth message occurs before receiving the third message.

As an embodiment, the fifth message indicates that the first time length triggers the first node U11 to start the second timer, and sets the expiration value of the second timer as the fifth message The first length of time indicated.

As an embodiment, the running state of the second timer is used for access blocking check.

As a sub-embodiment of the above embodiment, when the second timer is in the running state, for access categories other than Type 0 and Type 2 access categories, the access blocking check is considered as blocking.

As an embodiment, when the triggering cause of the second message is an information bit generated at the first node, receiving the first message will trigger the second timer to stop.

As an embodiment, when the triggering reason of the second message is to forward the information bit generated at the second node, the receiving of the first message will not trigger the second timer to stop.

As an embodiment, when the triggering reason of the second message is to forward information bits generated at the second node, receiving the first message does not affect the running state of the second timer.

As an embodiment, when the triggering cause of the second message is to forward information bits generated at the second node, after the first message is received, the second timer continues to run.

As an embodiment, the first message is used to agree or confirm the RRC connection request of the second message.

As an embodiment, the fifth message is used to feed back the RRC connection request of the first node U11.

As an embodiment, the fifth message is used to feed back the last RRC connection request of the first node U11.

As an embodiment, the sixth message is received later than the second message is sent; the sixth message includes a second time length; the sixth message includes the second time length and is used to trigger the second time length Restarting of the second timer: the restarted expiration value of the second timer is equal to the second time length.

As an embodiment, the sixth message is received later than the second message is sent; the sixth message includes a second time length; the sixth message includes the second time length and is used to trigger the second time length The restart of the second timer; the restarted expiration value of the second timer is equal to the second length of time; the trigger reason of the second message is generated at the second node for forwarding information bits.

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

As a sub-embodiment of the above embodiment, the sixth message includes RRCRelease.

As a sub-embodiment of the above embodiment, the sixth message includes RRCReject.

As a sub-embodiment of the above embodiment, the sixth message includes RRCConnectionRelease.

As a sub-embodiment of the above embodiment, the sixth message includes RRCConnectionReject.

As a sub-embodiment of the above embodiment, the second time length included in the sixth message is waittime.

As a sub-embodiment of the above embodiment, the value range of the second time length included in the sixth message is X2 seconds, where X2 is a positive integer between 1 and 16; for example, X2 is equal to 1, for example X2 is equal to 16.

As a sub-embodiment of the above embodiment, the sentence that the sixth message includes that the second time length is used to trigger the restart of the second timer includes that the second timer restart.

As a sub-embodiment of the above embodiment, the sentence that the sixth message includes that the second time length is used to trigger a restart of the second timer includes that the second timer starts immediately after being stopped.

As a sub-embodiment of the above embodiment, the sentence that the sixth message includes that the second time length is used to trigger a restart of the second timer includes that the second timer is stopped, and as received In response to the sixth message, the second timer starts.

As a sub-embodiment of the above embodiment, when the sixth message is received, the second timer is in a running state.

As an embodiment, the sixth message is used to release the RRC connection; the first timer is operated after receiving the sixth message, the operation is to stop or continue to run, and the operation is the same as the second The triggering cause of the message is related; when the sixth message is received, the first timer is in the running state;

Wherein, the operation in the phrase related to the triggering cause of the second message includes:

Said operation is stopping in response to receiving said sixth message when said triggering cause of said second message is for an information bit generated at said first node;

When the triggering reason of the second message is to forward the information bits generated at the second node, the operation is to continue running or restart.

As a sub-embodiment of the above embodiment, the sixth message is used to release the RRC connection requested by the second message.

As a sub-embodiment of the above embodiment, the sixth message is used to release the RRC connection agreed by the first message.

As a sub-embodiment of the above embodiment, the second timer is started before the second message is sent, when the trigger cause of the second message is for the information bit generated at the first node , the reception of the first message does not stop the second timer.

As a sub-embodiment of the above embodiment, the second timer is started before the second message is sent, when the trigger cause of the second message is for the information bit generated at the first node , operate the second timer after receiving the first message, and the behavior operation is to continue running.

As a sub-embodiment of the above embodiment, the first node U11 triggers the start of the second timer upon receiving an indication from the network.

As a sub-embodiment of the above embodiment, when the sixth message is received, the second timer is in a running state.

As a sub-embodiment of the above embodiment, when the trigger cause of the second message is an information bit generated at the first node, the reception of the sixth message triggers the second timer stop.

As a sub-embodiment of the above embodiment, when the triggering reason of the second message is to forward the information bit generated at the second node, the reception of the sixth message triggers the second timer The expiration value after the restart of and the second timer restarts is the second length of time.

As a sub-embodiment of the above embodiment, when the triggering reason of the second message is to forward the information bit generated at the second node, the reception of the sixth message triggers the second timer continue to run.

Example 7

Embodiment 7 illustrates a schematic diagram in which the third message is used to determine the value of the first field according to an embodiment of the present application, as shown in FIG. 7 .

As an embodiment, the first node receives a third message, and the third message requests an RRC connection of the second node.

As an embodiment, the first node sends a second message, the second message is used to request an RRC connection, and the second message includes at least a reason for the request.

As an embodiment, when the third message is received, the first node is in a state other than the RRC connected state.

As an embodiment, the second message includes a first field, and the third message includes a second field; the first field and the second field are respectively used to indicate a request reason for requesting an RRC connection.

As an embodiment, the second message includes a first field, the third message includes a second field, and the fourth message includes a third field; the values of the second field and the third field are the same ; The third message is used to determine the value of the first field.

As an embodiment, the first field, the second field and the third field are respectively used to indicate a request reason for requesting an RRC connection.

As an embodiment, the first field is the EstablishmentCause field of the second message.

As an embodiment, the first field is the ResumeCause field of the second message.

As an embodiment, the first field is the reestablishmentCause field of the second message.

As an embodiment, the second field is the EstablishmentCause field of the third message.

As an embodiment, the second field is the ResumeCause field of the third message.

As an embodiment, the second field is the reestablishmentCause field of the third message.

As an embodiment, the third field is the EstablishmentCause field of the fourth message.

As an embodiment, the third field is the ResumeCause field of the fourth message.

As an embodiment, the third field is the reestablishmentCause field of the fourth message.

As an embodiment, if the second field of the third message is the EstablishmentCause field, then the third field of the fourth message is the EstablishmentCause field.

As an embodiment, if the second field of the third message is a ResumeCause field, then the third field of the fourth message is a ResumeCause field.

As an embodiment, if the second field of the third message is a reestablishmentCause field, then the third field of the fourth message is a reestablishmentCause field.

As an embodiment, a value of the first field of the second message is the same as a value of the second field of the third message.

As an example, if the second field of the third message is {emergency, highPriorityAccess, mt-Access, mo-Signalling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, mps-PriorityAccess ,mcs-PriorityAccess}, the value of the first field of the second message is the same as the value of the second field of the third message.

As an example, if the second field of the third message is {emergency, highPriorityAccess, mt-Access, mo-Signalling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, mps-PriorityAccess , mcs-PriorityAccess}, the first field of the second message is the same as the second field of the third message.

As an embodiment, the second field of the third message is set to rna-Update, and the first field of the second message is set to a spare bit of release 16.

As an embodiment, the second field of the third message is set to rna-Update, and the first field of the second message is set to {emergency, highPriorityAccess, mt-Access, mo-Signalling , mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, mps-PriorityAccess, mcs-PriorityAccess}.

As an embodiment, when the trigger reason of the second message is to forward the information bits generated at the second node, the first field of the second message is set as a spare of release 16 bit.

As an embodiment, when the triggering cause of the second message is to forward information bits generated at the second node, the first field of the second message is set to relay.

As an embodiment, when the triggering cause of the second message is to forward information bits generated at the second node, the first field of the second message is set to L2-relay.

As an embodiment, when the triggering cause of the second message is to forward information bits generated at the second node, the first field of the second message is set to data-relay.

As an embodiment, when the triggering cause of the second message is to forward information bits generated at the second node, the first field of the second message is set to mo-relay.

As an embodiment, when the triggering cause of the second message is to forward information bits generated at the second node, the first field of the second message is set to mo-datarelay.

As an embodiment, when the triggering cause of the second message is to forward information bits generated at the second node, the first field of the second message is set to type1-relay.

As an embodiment, when the triggering cause of the second message is to forward information bits generated at the second node, the first field of the second message is set to type2-relay.

As an embodiment, when the triggering cause of the second message is to forward information bits generated at the second node, the first field of the second message is set to typeI-relay.

As an embodiment, when the triggering cause of the second message is to forward information bits generated at the second node, the first field of the second message is set to typeII-relay.

As an embodiment, receiving the third message is used to determine that information bits generated by the second node need to be forwarded.

As an embodiment, receiving the third message is used to determine that the second message needs to be sent to forward the information bits generated by the second node.

As an embodiment, receiving the third message triggers sending the second message.

As an embodiment, the reception of the third message triggers the sending of the second message, and the first field of the second message indicates that the request reason is related to relay.

As an embodiment, the reception of the third message triggers the sending of the second message, and the first field of the second message indicates that it is related to a relay.

As an embodiment, the first node maps the value of the second field of the third message to an access type through a pre-configured mapping table, and then maps the value of the one access type according to the pre-configured mapping table. The access type is mapped to the value of the first field of the second message.

Example 8

Embodiment 8 illustrates a schematic diagram in which the seventh message is used to indicate the first timer according to an embodiment of the present application, as shown in FIG. 8 .

As an embodiment, the seventh message includes an RRC message.

As an embodiment, the seventh message is an uplink message.

As an embodiment, the logical channel occupied by the seventh message includes CCCH.

As an embodiment, the logical channel occupied by the seventh message includes DCCH.

As an embodiment, the seventh message is an RRC message.

As a sub-embodiment of the above embodiment, the seventh message includes UEAssistanceInformation.

As a sub-embodiment of the above embodiment, the seventh message includes ULInformationTransfer.

As a sub-embodiment of the above embodiment, the seventh message includes UEInformationResponse.

As a sub-embodiment of the above embodiment, the seventh message includes RRCReconfigurationComplete.

As a sub-embodiment of the above embodiment, the seventh message includes RRCConnectionReconfigurationComplete.

As an embodiment, the seventh message indicates whether the first timer is running.

As an embodiment, the seventh message indicates an expiration time of the first timer.

As an embodiment, the seventh message indicates an expiration time of the first timer if it is not prematurely terminated.

As an embodiment, the seventh message indicates an expiration time of the first timer if no intervention is performed.

As an embodiment, the seventh message indicates the time determined by the expiration value of the first timer after the start of the first timer.

As an embodiment, the seventh message indicates an expected expiration time of the first timer.

As an embodiment, the seventh message indicates an expected expiration time of the first timer when the seventh message is sent.

As an embodiment, the seventh message indicates an expiration value of the first timer.

As an embodiment, the seventh message indicates an associated access category of the first timer.

As an embodiment, the seventh message indicates an associated access identity of the first timer.

As an embodiment, the seventh message indicates the blocked QoS flow due to the running of the first timer.

As an embodiment, the seventh message indicates the QoS flows not affected by the running of the first timer.

As an embodiment, the seventh message indicates whether the second timer is running.

As an embodiment, the seventh message indicates an expiration time of the second timer.

As an embodiment, the seventh message indicates an expiration time of the second timer if it is not terminated in advance.

As an embodiment, the seventh message indicates an expiration time of the second timer if no intervention is performed.

As an embodiment, the seventh message indicates the time determined by the expiration value of the second timer after the start of the second timer.

As an embodiment, the seventh message indicates an expected expiration time of the second timer.

As an embodiment, the seventh message indicates an expected expiration time of the second timer when the seventh message is sent.

As an embodiment, the seventh message indicates an expiration value of the second timer.

As an embodiment, the advantage of the above method is that, through the seventh message, the serving cell can know that the first timer of the first node is running, and the serving cell can avoid scheduling the data of the first node to ensure fairness .

Example 9

Embodiment 9 illustrates a structural block diagram of a processing device used in the first node according to an embodiment of the present application; as shown in FIG. 9 . In FIG. 9 , the processing device 900 in the first node includes a first receiver 901 and a first transmitter 902 . In Example 9,

The first receiver 901 receives a first set of parameters and a first message; performs an access blocking check according to the first set of parameters; as a response to performing the access blocking check, starts a first timer;

The first transmitter 902 sends a second message, the second message is used to request an RRC connection, the second message includes at least a request reason, and the second message is used to trigger the first message; upon receiving Operate the first timer after the first message, the operation is to stop or continue to run, and the operation is related to the triggering cause of the second message;

Wherein, the operation in the phrase related to the triggering cause of the second message includes:

When said triggering cause of said second message is for an information bit generated at said first node, said operation is stopping in response to receiving said first message;

When the triggering cause of the second message is to forward information bits generated at the second node, the operation is to continue running.

As an embodiment, the first receiver 901 receives a third message through the PC5 interface, where the third message is used to request the RRC connection of the second node;

The first transmitter 902 sends a fourth message through the Uu interface, the fourth message is generated by the third message, and the fourth message is used to request the RRC connection of the second node; the third The request reason included in the message and the fourth message is the same.

As an embodiment, the first transmitter 902 sends a second parameter set, and the first parameter set is used to generate the second parameter set; the second parameter set is used for the third The sending of the message performs an access blocking check.

As an embodiment, the second message includes a first field, the third message includes a second field, and the fourth message includes a third field; the values of the second field and the third field are the same ; The third message is used to determine the value of the first field;

The first field, the second field and the third field are respectively used to indicate the request reason for requesting the RRC connection.

As an embodiment, the first receiver 901 receives a fifth message and a sixth message, and the fifth message and the sixth message are respectively used to release the RRC connection; the fifth message includes the first time length; the fifth message includes that the first length of time is used to trigger the start of a second timer; the expiration value of the second timer is equal to the first length of time; the start of the second timer The distance from the receiving moment of the sixth message is less than the expiration value of the second timer; the start of the second timer is earlier than the sending of the second message; the receiving of the sixth message is later than the second timer The sending of two messages; the sixth message includes a second length of time; the sixth message includes the second length of time is used to trigger the restart of the second timer; the restart of the second timer The expiry value after start is equal to said second length of time; the running status of said second timer is used for access blocking checks.

As an embodiment, the first receiver 901 receives a sixth message, and the sixth message is used to release the RRC connection; after receiving the sixth message, the first timer is operated, and the operation is Stopping or continuing to run, the operation is related to the triggering cause of the second message; when the sixth message is received, the first timer is in the running state;

Wherein, the operation in the phrase related to the triggering cause of the second message includes:

Said operation is stopping in response to receiving said sixth message when said triggering cause of said second message is for an information bit generated at said first node;

When the triggering cause of the second message is to forward information bits generated at the second node, the operation is to continue running.

As an embodiment, the first transmitter 902 sends a seventh message, where the seventh message is used to indicate the first timer.

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

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

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

As an embodiment, the first node is an aircraft.

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

As an embodiment, the first node is a relay.

As an embodiment, the first node is a ship.

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

As an embodiment, the first node is a terminal of the Industrial Internet of Things.

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

As an embodiment, the first receiver 901 includes the antenna 452 in Embodiment 4, the receiver 454, the receiving processor 456, the multi-antenna receiving processor 458, the controller/processor 459, the memory 460, or the data source At least one of 467.

As an embodiment, the first transmitter 902 includes the antenna 452 in Embodiment 4, the transmitter 454, the transmission processor 468, the multi-antenna transmission processor 457, the controller/processor 459, the memory 460, or the data source At least one of 467.

Example 10

Embodiment 10 illustrates a structural block diagram of a processing device used in a second node according to an embodiment of the present application; as shown in FIG. 10 . In FIG. 10 , the processing device 1000 in the second node includes a second receiver 1002 and a second transmitter 1001 . In Example 10,

a first node, receiving a first set of parameters and a first message; performing an access blocking check according to said first set of parameters; in response to performing said access blocking check, starting a first timer;

The first node sends a second message, the second message is used to request an RRC connection, the second message includes at least a request reason, and the second message is used to trigger the first message; upon receiving the Operating the first timer after the first message, the operation is to stop or continue to run, and the operation is related to the triggering cause of the second message;

Wherein, the operation in the phrase related to the triggering cause of the second message includes:

When said triggering cause of said second message is for an information bit generated at said first node, said operation is stopping in response to receiving said first message;

When the triggering cause of the second message is to forward information bits generated at the second node, the operation is to continue running.

As an embodiment, the second transmitter 1001 sends a third message through the PC5 interface, where the third message is used to request the RRC connection of the second node;

The first node sends a fourth message through the Uu interface, the fourth message is generated by the third message, and the fourth message is used to request the RRC connection of the second node; the third message and The request reasons included in the fourth message are the same.

As an embodiment, the second receiver 1002 receives a second parameter set, and the first parameter set is used to generate the second parameter set; the second parameter set is used for the third message sending performing an access blocking check; in response to performing said access blocking checking, starting a third timer.

As an embodiment, the second message includes a first field, the third message includes a second field, and the fourth message includes a third field; the values of the second field and the third field are the same ; The third message is used to determine the value of the first field;

The first field, the second field and the third field are respectively used to indicate the request reason for requesting the RRC connection.

As an embodiment, the second receiver 1002 receives an eighth message, and the eighth message is used to agree to the request for the RRC connection of the second node in the third message, or the eighth message a message to release said requesting RRC connection of said second node of said third message; in response to receiving said eighth message, stopping said third timer.

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

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

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

As an embodiment, the second node is an aircraft.

As an embodiment, the second node is a vehicle terminal.

As an embodiment, the second node is a relay.

As an embodiment, the second node is a ship.

As an embodiment, the second node is an Internet of Things terminal.

As an embodiment, the second node is a terminal of the Industrial Internet of Things.

As an embodiment, the second node is a device supporting low-latency high-reliability transmission.

As an embodiment, the second transmitter 1001 includes at least one of the antenna 420 in Embodiment 4, the transmitter 418, the transmission processor 416, the multi-antenna transmission processor 471, the controller/processor 475, and the memory 476 one.

As an embodiment, the second receiver 1002 includes at least one of the antenna 420 in Embodiment 4, the receiver 418, the receiving processor 470, the multi-antenna receiving processor 472, the controller/processor 475, and the memory 476 one.

Example 11

Embodiment 11 illustrates a structural block diagram of a processing device used in a third node according to an embodiment of the present application; as shown in FIG. 11 . In FIG. 11 , the processing device 1100 in the third node includes a third receiver 1102 and a third transmitter 1101 . In Example 11,

The third transmitter 1101 sends the first parameter set and the first message; the sender of the second message performs an access blocking check according to the first parameter set; as a response to performing the access blocking check, starts a first timing device;

The third receiver 1102 receives the second message, the second message is used to request an RRC connection, the second message includes at least a request reason, and the second message is used to trigger the first message; The sender of the second message operates the first timer after receiving the first message, the operation is to stop or continue to run, and the operation is related to the triggering cause of the second message;

Wherein, the operation in the phrase related to the triggering cause of the second message includes:

When said triggering cause of said second message is for an information bit generated at said first node, said operation is stopping in response to receiving said first message;

When the triggering cause of the second message is to forward information bits generated at the second node, the operation is to continue running.

As an embodiment, the third receiver 1102 receives a fourth message through a Uu interface, where the fourth message is used to request an RRC connection of the second node.

As an embodiment, the third transmitter 1101 sends a fifth message and a sixth message, and the fifth message and the sixth message are respectively used to release the RRC connection; the fifth message includes the first time length; the fifth message includes that the first length of time is used to trigger the start of a second timer; the expiration value of the second timer is equal to the first length of time; the start of the second timer The distance from the receiving moment of the sixth message is less than the expiration value of the second timer; the start of the second timer is earlier than the sending of the second message; the receiving of the sixth message is later than the second timer The sending of two messages; the sixth message includes a second length of time; the sixth message includes the second length of time is used to trigger the restart of the second timer; the restart of the second timer The expiry value after start is equal to said second length of time; the running status of said second timer is used for access blocking checks.

As an embodiment, the third transmitter 1101 sends a sixth message, and the sixth message is used to release the RRC connection; the receiver of the sixth message operates the sixth message after receiving the sixth message A timer, the operation is to stop or continue to run, and the operation is related to the triggering cause of the second message; when the sixth message is received, the first timer is in the running state;

Wherein, the operation in the phrase related to the triggering cause of the second message includes:

Said operation is stopping in response to receiving said sixth message when said triggering cause of said second message is for an information bit generated at said first node;

When the triggering cause of the second message is to forward information bits generated at the second node, the operation is to continue running.

As an embodiment, the third receiver 1102 receives a seventh message, where the seventh message is used to indicate the first timer.

As an embodiment, the third transmitter 1101 sends an eighth message, where the eighth message is used to agree to the RRC connection request of the second node.

As an embodiment, the third node is a gateway.

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

As an embodiment, the third node is a satellite.

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

As an embodiment, the third node is an access point.

As an embodiment, the third transmitter 1101 includes at least one of the antenna 420 in Embodiment 4, the transmitter 418, the transmitting processor 416, the multi-antenna transmitting processor 471, the controller/processor 475, and the memory 476 one.

As an embodiment, the third receiver 1102 includes at least one of the antenna 420 in Embodiment 4, the receiver 418, the receiving processor 470, the multi-antenna receiving processor 472, the controller/processor 475, and the memory 476 one.

Those skilled in the art can understand that all or part of the steps in the above method can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a hard disk or an optical disk. Optionally, all or part of the steps in the foregoing embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module unit in the above-mentioned embodiments may be implemented in the form of hardware, or may be implemented in the form of software function modules, and the present application is not limited to any specific combination of software and hardware. The user equipment, terminal and UE in this application include but are not limited to drones, communication modules on drones, remote-controlled aircraft, aircraft, small aircraft, mobile phones, tablet computers, notebooks, vehicle-mounted communication equipment, wireless sensors, network cards, Internet of things terminal, RFID terminal, NB-IoT terminal, MTC (Machine Type Communication, machine type communication) terminal, eMTC (enhanced MTC, enhanced MTC) terminal, data card, network card, vehicle communication equipment, low-cost mobile phone, low-cost Cost Tablet PC, satellite communication equipment, ship communication equipment, NTN user equipment and other wireless communication equipment. The base station or system equipment in this application includes but not limited to macrocell base station, microcell base station, home base station, relay base station, gNB (NR Node B) NR Node B, TRP (Transmitter ReceiverPoint, sending and receiving node), NTN base station, Satellite equipment, flight platform equipment and other wireless communication equipment.

The above descriptions are only preferred embodiments of the present application, and are not intended to limit the protection scope of the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of this application shall be included within the protection scope of this application.

Claims (12)

1. A first node used for wireless communication, comprising: a first receiver, receiving a first set of parameters and a first message; performing an access blocking check according to said first set of parameters; in response to performing said access blocking check, starting a first timer; The first transmitter sends a second message, the second message is used to request an RRC connection, the second message includes at least a request reason, and the second message is used to trigger the first message; upon receiving the Operate the first timer after the first message, the operation is to stop or continue to run, and the operation is related to the triggering cause of the second message; Wherein, the operation in the phrase related to the triggering cause of the second message includes: When said triggering cause of said second message is for an information bit generated at said first node, said operation is stopping in response to receiving said first message; When the triggering cause of the second message is to forward information bits generated at the second node, the operation is to continue running. 2. The first node according to claim 1, comprising: The first receiver receives a third message through the PC5 interface, and the third message is used to request the RRC connection of the second node; The first transmitter sends a fourth message through the Uu interface, the fourth message is generated by the third message, and the fourth message is used to request the RRC connection of the second node; the third message It is the same as the request reason included in the fourth message. 3. The first node according to claim 2, comprising: The first transmitter transmits a second set of parameters, the first set of parameters is used to generate the second set of parameters; the second set of parameters is used to perform access for the transmission of the third message Block check. 4. The first node according to claim 2 or 3, characterized in that, The second message includes a first field, the third message includes a second field, and the fourth message includes a third field; the values of the second field and the third field are the same; the third The message is used to determine the value of the first field; The first field, the second field and the third field are respectively used to indicate the request reason for requesting the RRC connection. 5. The first node according to any one of claims 1 to 4, comprising: The first receiver receives a fifth message and a sixth message, and the fifth message and the sixth message are respectively used to release the RRC connection; the fifth message includes a first time length; the fifth The message includes that the first length of time is used to trigger the start of a second timer; the expiration value of the second timer is equal to the first length of time; the start of the second timer is a distance from the sixth message The receiving moment of the second timer is less than the expiration value of the second timer; the start of the second timer is earlier than the sending of the second message; the receiving of the sixth message is later than the sending of the second message; The sixth message includes a second length of time; the sixth message includes that the second length of time is used to trigger a restart of a second timer; the restarted expiration value of the second timer is equal to The second length of time; the running state of the second timer is used for access blocking checks. 6. The first node according to any one of claims 1 to 5, comprising: The first receiver receives a sixth message, the sixth message is used to release the RRC connection; operates the first timer after receiving the sixth message, the operation is to stop or continue to run, the The above operation is related to the triggering cause of the second message; when the sixth message is received, the first timer is in the running state; Wherein, the operation in the phrase related to the triggering cause of the second message includes: Said operation is stopping in response to receiving said sixth message when said triggering cause of said second message is for an information bit generated at said first node; When the triggering cause of the second message is to forward information bits generated at the second node, the operation is to continue running. 7. The first node according to any one of claims 1 to 6, comprising: The first transmitter, sending a seventh message, the seventh message being used to indicate the first timer. 8. A second node used for wireless communication, comprising: a first node, receiving a first set of parameters and a first message; performing an access blocking check according to said first set of parameters; in response to performing said access blocking check, starting a first timer; The first node sends a second message, the second message is used to request an RRC connection, the second message includes at least a request reason, and the second message is used to trigger the first message; upon receiving the Operating the first timer after the first message, the operation is to stop or continue to run, and the operation is related to the triggering cause of the second message; Wherein, the operation in the phrase related to the triggering cause of the second message includes: When said triggering cause of said second message is for an information bit generated at said first node, said operation is stopping in response to receiving said first message; When the triggering cause of the second message is to forward information bits generated at the second node, the operation is to continue running. 9. A third node used for wireless communication, comprising: A third transmitter, sending a first set of parameters and a first message; the sender of the second message performs an access blocking check according to said first set of parameters; in response to performing said access blocking check, starts a first timer ; A third receiver, receiving the second message, the second message is used to request an RRC connection, the second message includes at least a request reason, and the second message is used to trigger the first message; The sender of the second message operates the first timer after receiving the first message, the operation is to stop or continue to run, and the operation is related to the triggering cause of the second message; Wherein, the operation in the phrase related to the triggering cause of the second message includes: When said triggering cause of said second message is for an information bit generated at said first node, said operation is stopping in response to receiving said first message; When the triggering cause of the second message is to forward information bits generated at the second node, the operation is to continue running. 10. A method used in a first node of wireless communication, comprising: receiving a first set of parameters, performing an access blocking check according to said first set of parameters; in response to performing said access blocking check, starting a first timer; sending a second message, the second message is used to request an RRC connection, the second message includes at least a request reason, the second message is used to trigger the first message; receiving the first message; operating the first timer after receiving the first message, the operation is to stop or continue to run, and the operation is related to the triggering cause of the second message; Wherein, the operation in the phrase related to the triggering cause of the second message includes: When said triggering cause of said second message is for an information bit generated at said first node, said operation is stopping in response to receiving said first message; When the triggering cause of the second message is to forward information bits generated at the second node, the operation is to continue running. 11. A method used in a second node for wireless communication, comprising: The first node, receiving a first set of parameters, performing an access blocking check according to the first set of parameters; in response to performing the access blocking check, starting a first timer; The first node sends a second message, the second message is used to request an RRC connection, the second message includes at least a request reason, and the second message is used to trigger the first message; The first node receives the first message; operates the first timer after receiving the first message, the operation is to stop or continue to run, and the operation is related to the trigger cause of the second message; Wherein, the operation in the phrase related to the triggering cause of the second message includes: When said triggering cause of said second message is for an information bit generated at said first node, said operation is stopping in response to receiving said first message; When the triggering cause of the second message is to forward information bits generated at the second node, the operation is to continue running. 12. A method used in a third node for wireless communication, comprising: Send the first set of parameters; receive the second message; send the first message; the sender of the second message performs an access blocking check according to the first set of parameters; in response to performing the access blocking check, starts a first timer; the second message is used to request an RRC connection, The second message includes at least a reason for the request, the second message is used to trigger the first message; the sender of the second message operates the first timer after receiving the first message, the The operation is to stop or continue to run, and the operation is related to the trigger cause of the second message; Wherein, the operation in the phrase related to the triggering cause of the second message includes: When said triggering cause of said second message is for an information bit generated at said first node, said operation is stopping in response to receiving said first message; When the triggering cause of the second message is to forward information bits generated at the second node, the operation is to continue running.

Images