CN115379530A

CN115379530A - Method and equipment used for wireless communication

Info

Publication number: CN115379530A
Application number: CN202110537270.6A
Authority: CN
Inventors: 陈宇; 张晓博
Original assignee: Shanghai Langbo Communication Technology Co Ltd
Current assignee: Shanghai Langbo Communication Technology Co Ltd
Priority date: 2021-05-18
Filing date: 2021-05-18
Publication date: 2022-11-22

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

Method and equipment used for wireless communication

Technical Field

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

Background

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

In Communication, both LTE (Long Term Evolution) and 5G NR relate to Reliable accurate reception of information, optimized energy efficiency ratio, determination of information validity, flexible resource allocation, scalable system structure, efficient non-access stratum information processing, lower service interruption and dropped rate, support for Low power consumption, which is important for normal Communication between a base station and user equipment, reasonable scheduling of resources, and balance of system load, so to speak, high throughput rate, meet Communication requirements of various services, improve spectrum utilization rate, and improve foundation of service quality, and are indispensable for enhanced Mobile BroadBand (eMBB) Communication, ultra Mobile Low Latency (ullc) or enhanced Machine Type Communication (eMTC). Meanwhile, in the Internet of Things in the field of industry, in V2X (Vehicular to X), communication between devices (Device to Device) is performed, in communication of unlicensed spectrum, in user communication quality monitoring, network planning optimization, in NTN (Non-terrestrial Network communication), in TN (terrestrial Network communication), in Dual connectivity (Dual connectivity) system, in wireless resource management and codebook selection of multiple antennas, there are wide requirements in signaling design, neighborhood management, service management, and beamforming, and the transmission mode of information is divided into broadcast and unicast, and both transmission modes are indispensable for the 5G system, because they help to meet the above requirements.

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

Disclosure of Invention

In various communication scenarios, the use of relays may be involved, e.g. when one UE is not within the coverage area of a cell, the network may be accessed by a relay, and the relay node may be another UE. When the relay accesses the network, the selected relay node may or may not have established an RRC connection with the network, and if the RRC connection is not established, the relay node needs to establish the RRC connection to forward or relay data of a remote node (remote UE). Both the remote node and the relay node need to establish an RRC connection with the network. The requested connection may be either a newly established RRC connection or a resume (resume) suspended RRC connection. No matter the remote node or the relay node, if RRC and connection are requested, access Control needs to be performed, and the Access Control performed at the UE end may be implemented by a Unified Access Control (UAC) mechanism. When performing Access control, the UE needs to perform Access blocking Check (Access blocking Check), and when the Check result is that no blocking is performed, the UE can Access the network, otherwise, the UE prohibits initiating an Access request. The data of the remote node relates to the remote node and the relay node at the same time, theoretically, access blocking check can be executed on one or two of the remote node and the relay node, the remote node and the relay node can also be separated from each other, access control check aiming at the connection request of the remote node is executed on the remote node, and the relay node only executes the access control check aiming at the access request triggered by the data of the relay node. In this case, the two nodes are relatively independent, and the relay node does not affect the access of the remote node even if the relay node is in the blocking state after the access control check, and the blocking state of the relay only affects the relay node but does not affect the remote node. The blocking state may last for a period of time, configured by the system, during which the UE is not allowed to initiate an access request for a particular access class. If the UE communicates directly with the network, the blocking state is meaningless once the UE accesses the network, and the UE will leave the blocking state immediately, but the situation when using the relay node to communicate is different, and whether the relay node is in the blocking state or not, the UE may access the network for forwarding data of the remote node.

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

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

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

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

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 a run, the operation being related to a trigger cause of the second message;

wherein the phrase that the operation relates to a trigger cause of the second message comprises:

when the trigger cause of the second message is for an information bit generated at the first node, the operation is to stop in response to receiving the first message;

the operation is to continue when the trigger cause of the second message is to forward information bits generated at the second node.

As an embodiment, the problem to be solved by the present application includes: when the relay node and the remote node independently perform access control check, the access of the remote node is not affected by whether the relay node is in the blocking state, and the access of the remote node should not affect the current blocking state of the relay node. Therefore, how to avoid the access of the relay node for the access of the remote node is a problem to be solved by the application.

As an example, the benefits of the above method include: the method proposed by the present application can solve the above problems. Meanwhile, the method provided by the application can enable the access control of the relay node and the remote node to be relatively independent, so that the access control can be favorably carried out according to different access requirements, and the remote node and the relay node are prevented from carrying out two repeated access control checks. In the method, the access of the relay node to the relay node can not be influenced by the access of the remote node, so that the unified access control arranged by the network is more stable and reliable.

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

sending a fourth message through a Uu interface, the fourth message being generated by the third message, the fourth message being used for requesting an RRC connection of the second node; the third message and the fourth message comprise the same request reason.

Specifically, according to an aspect of the present application, a second parameter set is sent, and the first parameter set is used for generating the second parameter set; the second set of parameters is used to perform an access barring check for the transmission of the third message.

Specifically, according to an 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 values of the second domain and the third domain are the same; the third message is used to determine a value of the first domain;

the first domain, the second domain and the third domain are respectively used for indicating a request reason for requesting RRC connection.

Specifically, according to an 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 for releasing RRC connection; the fifth message comprises a first length of time; the fifth message comprises that the first length of time is used to trigger the start of a second timer; the expired value of the second timer is equal to the first length of time; the starting time of the second timer is less than the expiration value of the second timer from the receiving time of the sixth message; the second timer starts earlier than the second message is sent; the sixth message is received later than the second message is sent; the sixth message comprises a second length of time; the sixth message comprises that the second length of time is used to trigger a restart of a second timer; an expiration value of the second timer after the restart is equal to the second length of time; the running status of the second timer is used for access blocking checking.

Specifically, according to an aspect of the present application, a sixth message is received, and the sixth message is used for releasing RRC connection; operating the first timer after receiving the sixth message, the operation being a stop or a continuation of a run, the operation being related to a trigger cause of the second message; when the sixth message is received, the first timer is in a running state;

wherein the phrase the operation relates to a trigger cause of the second message comprises:

when the trigger cause of the second message is for an information bit generated at the first node, the operation is to stop in response to receiving the sixth message;

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

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

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

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

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

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

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

a first node receiving a first parameter set, and performing access blocking check according to the first parameter set; in response to performing the access barring check, starting a first timer;

a first node that transmits 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 a first message;

a first node receiving the first message; operating the first timer after receiving the first message, the operation being a stop or a continuation of a run, the operation being related to a trigger cause of the second message;

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

the first node sends a fourth message through a Uu interface, wherein the fourth message is generated by the third message, and the fourth message is used for requesting RRC connection of the second node; the third message and the fourth message comprise the same request reason.

In particular, according to an aspect of the present application, a second set of parameters is received, the first set of parameters being used to generate the second set of parameters; the second set of parameters is used to perform an access blocking check for the transmission of the third message; in response to performing the access barring check, a third timer is started.

Specifically, according to an aspect of the present application, an eighth message is received, the eighth message being used to grant the request of the third message to the RRC connection of the second node, or the eighth message being used to release the request of the third message to the RRC connection of the second node; in response to receiving the eighth message, stopping the third timer.

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

transmitting a first set of parameters;

receiving a second message;

sending a first message;

a sender of the second message performs an access blocking check according to the first set of parameters; starting a first timer in response to performing the access barring check; the second message is used to request an RRC connection, the second message including at least a request cause, 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, wherein the operation is stopping or continuing to run, and the operation is related to the trigger reason of the second message;

Specifically, according to an 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 an aspect of the present application, a fifth message and a sixth message are sent, where the fifth message and the sixth message are used to release the RRC connection, respectively; the fifth message comprises a first length of time; the fifth message comprises that the first length of time is used to trigger the start of a second timer; the second timer has an expiration value equal to the first length of time; the starting time of the second timer is less than the expiration value of the second timer from the receiving time of the sixth message; the second timer starts earlier than the second message is sent; the sixth message is received later than the second message is sent; the sixth message comprises a second length of time; the sixth message comprises that the second length of time is used to trigger a restart of a second timer; an expiration value of the second timer after the restart is equal to the second length of time; the running status of the second timer is used for access blocking checking.

Specifically, according to an aspect of the present application, a sixth message is sent, and the sixth message is used for releasing RRC connection; the receiver of the sixth message operates the first timer after receiving the sixth message, wherein the operation is stopping or continuing to run, and the operation is related to the trigger reason of the second message; when the sixth message is received, the first timer is in a running state;

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

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

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

In particular, according to an aspect of the application, the third node is a cell or a group of cells.

In particular, according to an aspect of the application, the third node is a gateway.

In particular, according to an aspect of the application, the third node is an access point.

A first node used for wireless communication, comprising:

a first receiver to receive a first set of parameters and a first message; performing an access blocking check according to the first set of parameters; starting a first timer in response to performing the access barring check;

a first transmitter to transmit 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; 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 application discloses 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 the first set of parameters; in response to performing the access barring check, starting a first timer;

a first node that transmits 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; operating the first timer after receiving the first message, the operation being a stop or a continuation of a run, the operation being related to a trigger cause of the second message;

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

a third transmitter to transmit the first set of parameters and 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 barring check, starting a first timer;

a third receiver to receive the 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; the sender of the second message operates the first timer after receiving the first message, wherein the operation is stopping or continuing to run, and the operation is related to the trigger reason of the second message;

As an example, compared with the conventional scheme, the present application has the following advantages: the method provided by the application can enable the access control check executed by the remote UE and the relay UE when the remote UE and the relay UE request RRC connection to be relatively independent; whether the remote UE is allowed to access is determined by the remote UE, and whether the relay UE is in the access blocking state or not is irrelevant, the relay UE cannot prevent the remote UE from accessing due to the access blocking state of the relay UE, and the access of the relay UE triggered by the access of the remote UE and the access request and data forwarding requirements of the remote UE cannot influence the access blocking state of the relay UE.

As an example, compared with the conventional scheme, the present application has the following advantages: unified access control is executed and guaranteed, and access blocking caused by access triggered by remote UE access of a relay node is avoided. The method is favorable for relieving network congestion and ensuring the fairness of access in a congestion state.

As an example, compared with the conventional scheme, the present application has the following advantages: the relay node informs the network of the access blocking condition, so that the network can schedule the access blocking condition, for example, when the access blocking condition still exists, only the data of the remote UE can be scheduled without scheduling the data of the relay UE, and the fairness is ensured.

As an example, compared with the conventional scheme, the method has the following advantages: the access of the remote UE only depends on the access control check of the remote UE, which is beneficial to avoiding repeated blockage and ensuring the service quality of the remote UE.

As an example, compared with the conventional scheme, the method has the following advantages: the RRC connection requested by the relay node for forwarding data of the remote UE uses a special request cause, thereby facilitating the network to identify the access cause.

Drawings

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

fig. 1 shows a flow diagram of receiving a first set of parameters and a first message, sending a second message according to one embodiment of the application;

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

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

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

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

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

fig. 7 illustrates a diagram where a third message is used to determine a value of a first domain according to an embodiment of the application;

FIG. 8 illustrates a diagram where a seventh message is used to indicate a first timer according to one embodiment of the present application;

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

figure 10 illustrates a schematic diagram of a processing arrangement for use in a second node according to an embodiment of the present application;

figure 11 illustrates a schematic diagram of a processing device for use in a second node according to an embodiment of the present application;

Detailed Description

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

Example 1

Embodiment 1 illustrates a flow chart of receiving 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 fig. 1, each block represents a step, and it is particularly emphasized that the sequence of the blocks in the figure does not represent a chronological relationship between the represented steps.

In embodiment 1, a first node in the present application receives a first parameter set in step 101; sending a second message in step 102; receiving a first message in step 103;

wherein the first node performs an access barring check according to the first set of parameters; in response to performing the access barring check, starting a first timer; the second message is 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; 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 phrase the operation relating to a trigger cause of the second message comprises:

As an embodiment, the first node is a UE (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 one embodiment, the first node is an L2 relay node of the second node.

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

As one embodiment, the first node and the second node communicate using a sidelink.

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

In one embodiment, the first message comprises an RRC message.

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

For one embodiment, the first message comprises a RRCSetup.

For one embodiment, the first message includes RRCResume.

For one embodiment, the first message comprises rrcreelease.

For one embodiment, the first message comprises RRCConnectionSetup.

For one embodiment, the first message includes rrcconnectionresponse.

For one embodiment, the first message comprises RRCConnectionRelease.

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

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

As an embodiment, the logical Channel occupied by the first message includes a DCCH (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 reception of the first message is used to trigger the action to operate the first timer.

In one embodiment, the first message is used for feeding back the second message.

As a sub-embodiment of the above embodiment, the second message is an RRCSetupRequest, and the first message is an 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 rrcreelease.

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 an rrcconnectionresumerrequest, and the first message is an RRCConnectionSetup.

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

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

As an embodiment, the first set of parameters comprises blocking parameters.

For one embodiment, the first set of parameters includes a unified access blocking (UAC) parameter.

For one embodiment, the first set of parameters includes uac-BarringInfo.

As an embodiment, the first set of parameters comprises uac-BarringForCommon.

As an embodiment, the first set of parameters comprises a uac-BarringPerPLMN-List.

As an embodiment, the first set of parameters comprises uac-BarringInfoSetList.

For one embodiment, the first set of parameters includes uac-Access category 1-SelectionAccessInfo.

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

For one embodiment, the first set of parameters includes blocking parameters for at least one Access category (Access category).

As an embodiment, the first set of parameters includes blocking parameters for at least one 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 said access identity.

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

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

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

As an embodiment, a SIM of the first node is preconfigured 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 to the first node.

For one embodiment, the first timer includes T390.

For one embodiment, the first timer includes T302.

For one embodiment, the first timer includes T303.

For one embodiment, the first timer includes T305.

For one embodiment, the first timer includes T306.

For one embodiment, the first timer includes T308.

For one embodiment, the first timer includes T309.

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

As one embodiment, the first timer is associated with a first access category, the trigger cause of the second message corresponding to the first access category.

As an embodiment, the first timer is associated with a first access identity to which the trigger reason for the second message belongs.

As one 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, an RRC connection is blocked for access requests or requests for information bits generated at the first node, wherein the information bits generated at the first node belong to the first access category.

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

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

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

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

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

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

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

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

For one embodiment, the first set of parameters is used to calculate an expiration value for the first timer.

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

For one embodiment, the second message comprises an RRC message.

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

For one embodiment, the second message comprises an RRCSetupRequest.

For one embodiment, the second message comprises an RRCResumeRequest.

For one embodiment, the second message comprises RRCResumeRequest1.

As an embodiment, the second message includes RRCConnectionSetupRequest.

As an embodiment, the second message comprises rrcconnectionsetupume.

In one embodiment, the logical channel occupied by the second message includes a CCCH.

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

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

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

As an embodiment, the second message requests establishment of an RRC connection.

As an embodiment, the second message requests that the RRC connection be continued.

As an embodiment, the second message includes an essabilismentaucause indicating a request reason.

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

As an embodiment, the receiving of the first message is used to trigger the operation of the first timer, the operation being a stop or a continuation.

As an embodiment, the first timer is operated after receiving the first message, the operation is to stop or continue running, and the operation is related to a trigger reason of the second message; the meaning of the behavior continuing is not to stop.

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

As an embodiment, when the trigger cause of the second message is for an information bit generated at the first node, the second message is triggered by an Access Stratum (Access Stratum) request.

As an embodiment, when the trigger cause of the second message is for an information bit generated at the first node, the second message is triggered by at least one of: { responding to RAN paging, uplink triggering RNA updates while the UE is in RRC _ INACTIVE, for sidelink communications }.

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

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

As an example, the reason why the sentence is the trigger of the second message is that the information bit generated at the first node includes the following meaning: the information bits are generated by a PDCP entity or PDCP layer of the first node.

As an example, the reason for the trigger of the sentence when the second message is for the information bit generated at the first node includes the following meaning: the information bits are generated by an SDAP layer of the first node.

As an example, the reason why the sentence is the trigger of the second message is that the information bit generated at the first node includes the following meaning: the information bits belong to one QoS flow of the first node.

As an example, the reason why the sentence is the trigger of the second message is that the information bit generated at the first node includes the following meaning: the information bits do not belong to bits of other UEs using L2 relay.

As an embodiment, the sentence includes a meaning when the trigger cause of the second message is for information bits generated at the first node, the RRC connection requested by the second message is for transmitting the information bits generated by the first node and not for transmitting information bits from other UEs.

As an embodiment, the sentence includes a meaning when the trigger cause of the second message is for an information bit generated at the first node, the RRC connection requested by the second message is for transmitting traffic of the first node and not for transmitting traffic from other UEs.

As an embodiment, the sentence includes a meaning that the RRC connection requested by the second message is not for relaying when the trigger reason for the second message is for an information bit generated at the first node.

As an embodiment, the sentence includes a meaning when the trigger cause of the second message is for an information bit generated at the first node that the RRC connection requested by the second message is not for layer 2 relaying.

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

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

In one 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 for the second message is the request reason included in the second message.

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

As a sub-embodiment of the above-mentioned embodiment, when the trigger cause of the second message is to relay an information bit generated at the second node, the first field in the second message is generated by the second node.

As a sub-embodiment of the foregoing embodiment, when the trigger cause of the second message is to relay an information bit generated at the second node, the first field in the second message is generated according to an indication of the second node.

As a sub-embodiment of the foregoing embodiment, when the trigger reason of the second message is to relay an information bit generated at the second node, the first field in the second message is generated according to a received third message sent by the second node.

As a sub-embodiment of the foregoing embodiment, when the trigger cause of the second message is to relay information bits generated at the second node, the first field in the second message reuses a Spare state in a Release16 message.

As a sub-embodiment of the foregoing embodiment, when the trigger cause of the second message is to relay information bits generated at the second node, the first field in the second message reuses a Spare state of an essabilishmentcause field in a Release16 message.

As a sub-embodiment of the foregoing embodiment, when the trigger reason of the second message is to relay information bits generated at the second node, an establishmentause 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, said sentence when said trigger reason for said second message is to forward information bits generated at said second node comprises the following meaning: the second node is a node other than the first node; the second message requests an RRC connection in order to receive and forward information bits of the second node.

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

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

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

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

As an embodiment, the first node determines the trigger reason of the second message by receiving a 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 SRB0.

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

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

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

As one embodiment, the first set of parameters is included within SIB 1.

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

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

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

As an embodiment, when performing an access barring check, if the first timer is not running and the first parameter set is used to indicate a first threshold and a first barring time, a node performing the access barring check generates a random number, if the generated random number is smaller than the first threshold, access is allowed, if the generated random number is not smaller than the first threshold, access is barred and the first timer is started, and an expiration value of the first timer is set to the first barring 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. Fig. 2 illustrates a V2X communication architecture under a 5G NR (new radio, new air interface), LTE (Long-Term Evolution), and LTE-a (Long-Term Evolution Advanced, enhanced Long-Term Evolution) system architecture. The 5G NR or LTE network architecture may be referred to as 5GS (5 GSystem)/EPS (Evolved Packet System) or some other suitable terminology.

The V2X communication architecture of embodiment 2 includes UE (User Equipment) 201, ue241, ng-RAN (next generation radio access network) 202,5gc (5G Core network )/EPC (Evolved Packet Core) 210, hss (Home Subscriber Server )/UDM (Unified Data Management) 220, proSe function 250, and ProSe application Server 230. The V2X communication architecture may interconnect with other access networks, but these entities/interfaces are not shown for simplicity. As shown, the V2X communication architecture provides packet switched services, however those skilled in the art will readily appreciate that the various concepts presented throughout this application may be extended to networks providing circuit switched services or other cellular networks. The NG-RAN includes NR node bs (gnbs) 203 and other gnbs 204. The gNB203 provides user and control plane protocol termination towards the UE 201. The gnbs 203 may be connected to other gnbs 204 via an Xn interface (e.g., backhaul). The gNB203 may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a Basic Service Set (BSS), an Extended Service Set (ESS), a TRP (transmit receive node), or some other suitable terminology. The gNB203 provides the UE201 with an access point to the 5GC/EPC210. Examples of UEs 201 include cellular phones, smart phones, session Initiation Protocol (SIP) phones, laptops, personal Digital Assistants (PDAs), satellite radios, non-terrestrial base station communications, satellite mobile communications, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, drones, aircraft, narrowband internet of things equipment, machine-type communication equipment, land vehicles, automobiles, wearable equipment, or any other similar functioning device. Those skilled in the art may also refer to UE201 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. The gNB203 is connected to the 5GC/EPC210 via an S1/NG interface. The 5GC/EPC210 includes MME (Mobility Management Entity)/AMF (Authentication Management Field)/SMF (Session Management Function) 211, other MME/AMF/SMF214, S-GW (serving Gateway)/UPF (user plane Function) 212, and P-GW (Packet data Network Gateway)/UPF 213. The MME/AMF/SMF211 is a control node that handles signaling between the UE201 and the 5GC/EPC210. In general, the MME/AMF/SMF211 provides bearer and connection management. All user IP (Internet protocol) packets are transported through the S-GW/UPF212, which S-GW/UPF212 itself is connected to the P-GW/UPF213. The P-GW provides UE IP address assignment as well as other functions. The P-GW/UPF213 is connected to the internet service 230. The internet service 230 includes an operator-corresponding internet protocol service, and may specifically include the internet, an intranet, an IMS (IP Multimedia Subsystem), and a packet-switched streaming service. The ProSe function 250 is a logical function for network-related behavior required for location-based Service (ProSe); including a DPF (Direct Provisioning Function), a Direct Discovery Name Management Function (Direct Discovery Name Management Function), an EPC-level Discovery ProSe Function (EPC-level Discovery ProSe Function), and the like. The ProSe application server 230 has functions of storing EPC ProSe subscriber identities, mapping between application layer subscriber identities and EPC ProSe subscriber identities, allocating a pool of code suffixes restricted by ProSe, and the like.

As an embodiment, the UE201 and the UE241 are connected through a PC5 Reference Point (Reference Point).

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

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

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

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

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

As an example, the third node gNB203 in the present application.

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

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

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

As an embodiment, the UE201 supports relay transmission.

As an embodiment, the UE241 supports relay transmission.

As an embodiment, the UE201 is a vehicle including an automobile.

As an embodiment, the UE241 is a vehicle including an automobile.

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

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

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

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

As an embodiment, the gNB203 is a satellite device.

Example 3

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

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

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

The radio protocol architecture of fig. 3 applies, as an example, to the third node in the present 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 example, the third message in this application is generated in 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 set of parameters 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 communications device 450 includes a controller/processor 459, a memory 460, a data source 467, a transmit processor 468, a receive processor 456, a multi-antenna transmit processor 457, a multi-antenna receive processor 458, a transmitter/receiver 454, and an antenna 452.

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

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

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

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

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

As an embodiment, the first communication device 450 apparatus includes: at least one processor and at least one memory including computer program code; the at least one memory and the computer program code configured to, for use with the at least one processor, the first communication device 450 apparatus at least: receiving a first set of parameters, and performing an access blocking check according to the first set of parameters; 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 a run, the operation being related to a trigger cause of the second message; wherein the phrase that the operation relates to a trigger cause of the second message comprises: when the trigger cause of the second message is for an information bit generated at the first node, the operation is to stop in response to receiving the first message; the operation is to continue when the trigger cause of the second message is to forward information bits generated at the second node.

As an embodiment, the first communication device 450 includes: a memory storing a program of computer readable instructions that when executed by at least one processor result in actions comprising: receiving a first set of parameters, and performing an access blocking check according to the first set of parameters; 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; wherein the phrase the operation relates to a trigger cause of the second message comprises: when the trigger cause of the second message is for an information bit generated at the first node, the operation is to stop in response to receiving the first message; the operation is to continue when the trigger cause of the second message is to forward information bits generated at the second node.

As an embodiment, the second communication device 410 apparatus includes: at least one processor and at least one memory including computer program code; the at least one memory and the computer program code are configured for use with the at least one processor. The second communication device 410 means at least: transmitting a first set of parameters; receiving a second message; sending a first message; a sender of the second message performs an access blocking check according to the first set of parameters; in response to performing the access barring check, starting a first timer; the second message is 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; the sender of the second message operates the first timer after receiving the first message, wherein the operation is stopping or continuing to run, and the operation is related to the trigger reason of the second message; wherein the phrase that the operation relates to a trigger cause of the second message comprises: when the trigger cause of the second message is for an information bit generated at the first node, the operation is to stop in response to receiving the first message; the operation is to continue when the trigger cause of the second message is to forward information bits generated at the second node.

As an embodiment, the second communication device 410 apparatus includes: a memory storing a program of computer readable instructions that when executed by at least one processor result in actions comprising: transmitting a first set of parameters; receiving a second message; sending a first message; a sender of the second message performs an access blocking check according to the first set of parameters; starting a first timer in response to performing the access barring check; the second message is 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; the sender of the second message operates the first timer after receiving the first message, wherein the operation is stopping or continuing to run, and the operation is related to the trigger reason of the second message; wherein the phrase that the operation relates to a trigger cause of the second message comprises: when the trigger cause of the second message is for an information bit generated at the first node, the operation is to stop in response to receiving the first message; the operation is to continue when the trigger cause of the second message is to forward information bits generated at the second node.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

For one embodiment, a transmitter 456 (including an antenna 460), a transmit processor 455, and a controller/processor 490 are used to transmit the second message.

For one embodiment, a transmitter 456 (including an antenna 460), a transmit processor 455, and a controller/processor 490 are used to transmit the third message.

For one embodiment, a transmitter 456 (including an antenna 460), a transmit processor 455, and a controller/processor 490 are used to transmit the fourth message.

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

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

For one embodiment, transmitter 416 (including antenna 420), transmit processor 412, and controller/processor 440 are used to transmit the fifth message.

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

For one embodiment, the transmitter 416 (including the antenna 420), the transmit processor 412, and the controller/processor 440 are used to transmit the eighth message.

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

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

For one embodiment, receiver 416 (including antenna 420), receive processor 412, and controller/processor 440 are used to receive the fourth message.

Example 5

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

ForFirst node U01Receiving a first set of parameters in step S5101; sending a second set of parameters in step S5102; receiving a third message in step S5103; sending a second message in step S5104; receiving a first message in step S5105; sending a fourth message in step S5106; a seventh message is sent in step S5107.

ForSecond node U02Receiving a second set of parameters in step S5201; transmitting a third message in step S5202; the eighth message is received in step S5203.

For theThird node U03Transmitting the first set of parameters in step S5301; receiving the second message in step S5302; transmitting a first message in step S5303; receiving a fourth message in step S5304; transmitting an eighth message in step S5305; the seventh message is received in step S5306.

In embodiment 5, the first node U01 performs an access blocking check according to the first set of parameters; in response to performing the access barring check, starting a first timer; the second message is 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; 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;

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 group of cells.

As an embodiment, the first set of parameters is transmitted by broadcasting.

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

As an embodiment, the first set of parameters is included in SIB 1.

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

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

As an embodiment, the second parameter set is sent by means of multicast.

As an embodiment, the second set of parameters is sent over a PC5 interface.

As an embodiment, the second set of parameters is sent via a PC5-RRC message.

As an embodiment, the second set of parameters is sent via a PC5-S message.

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

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

For one embodiment, the second set of parameters includes a Unified Access Check (UAC) parameter.

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

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

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

For one embodiment, the second parameter set belongs to a Direct Link Establishment message.

As an embodiment, the second set of parameters is used to perform an access barring check for the transmission of 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 needs to first 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 perform a blocking check first before sending the third message, and when the result of the access check is that access is allowed, the second node U02 sends the third message.

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

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

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

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

As a sub-embodiment of the above embodiment, the second node U02 sends the third message with a default layer 2 configuration, which 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 comprises a reason for the request.

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

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

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

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

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

As a sub-embodiment of the above embodiment, said 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 one of { emergency, highPriorityAccess, mt-Access, mo-signaling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, mps-PriorityAccess, mcs-PriorityAccess }.

As a sub-embodiment of the above embodiment, the request reason included in the third message belongs to one of { emergency, highrichioryaccess, mt-Access, mo-signaling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, 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 { recornfiguration failure, handoverFailure, otherFailure, relayreeselection, relayfaily }.

As a sub-embodiment of the above embodiment, the third message indicates that a new RRC connection is requested to be established.

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

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

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 the 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 the shortMAC-I are ciphered 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 the MAC layer or physical layer.

As a sub-embodiment of the above embodiment, the third message comprises one container, the one container comprising RRCResumeRequest.

As a sub-embodiment of the above embodiment, the third message comprises one container, and the one container comprises rrcreestablshmentirequest.

As a sub-embodiment of the above embodiment, the third message comprises one container, and the one container comprises rrcreestablshmentirequest 1.

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 SRB 2.

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

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

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

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

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

As a sub-embodiment of the above embodiment, the third message includes resumediversity and resumeMAC-I, and the resumediversity and the resumeMAC-I are encrypted or scrambled by a MAC layer or a 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 RRC connection through 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, the reception of the third message triggers the first node U01 to send the second message.

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

For one embodiment, the second message triggers the first message.

In one embodiment, the first message is used to grant 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 a random access procedure, and the first message is msg4 in a random access procedure.

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

In one embodiment, the fourth message is generated by the third message, and the fourth message is used for requesting 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 the 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 the shortMAC-I come from the third message, and the c-RNTI and the shortMAC-I are not encrypted.

As a sub-embodiment of this embodiment, the fourth message includes resumedenity and resumeMAC-I, and the resumedenty and the resumeMAC-I come from the third message.

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

As a sub-embodiment of this embodiment, the fourth message includes the same establishmentause as the establishmentause of the third message.

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

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

As an embodiment, the third message and the fourth message include the same request reason.

For one embodiment, the fourth message comprises an RRC message.

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

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

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

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

As a sub-embodiment of the above embodiment, the fourth message comprises an rrcconnectionresumerrequest.

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

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

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

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

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

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

As an embodiment, the fourth message is included in a container of RRC messages of 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 for feeding back the fourth message.

As an embodiment, the eighth message is used for feeding back the third message.

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

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

For one embodiment, the eighth message comprises a RRCSetup.

For one embodiment, the eighth message includes RRCResume.

For one embodiment, the eighth message includes rrcreestablistering.

For one embodiment, the eighth message includes rrcreelease.

For one embodiment, the eighth message comprises RRCReject.

For one embodiment, the seventh message comprises an RRC message.

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

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

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

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

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

As an embodiment, said seventh message belongs to msgA.

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

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

As an embodiment, the random access procedure to which the second message belongs uses dedicated time-frequency resources for indicating the trigger cause of the second message is to forward information bits generated at nodes other than the first node U01.

As an embodiment, the random access procedure to which the second message belongs uses a dedicated Preamble for indicating that the trigger reason of the second message is to forward an information bit generated by a node other than the first node U01.

Example 6

Embodiment 6 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in fig. 6. In fig. 6, U11 corresponds to the first node of the present application, and U13 corresponds to the third node of the present application, and it is specifically noted that the sequence in this example does not limit the sequence of signal transmission and the sequence of implementation in the present application, and the steps in F61 are optional; example 6 is based on example 5, and the parts required in example 6 but not shown can be referred to in example 5.

For theFirst node U11Receiving a fifth message in step S6101; sending a second message in step S6102; receiving a first message in step S6103; a sixth message is received in step S6104.

For theThird node U13A fifth message is transmitted in step S6301; receiving a second message in step S6302; transmitting a first message in step S6303; a sixth message is transmitted in step S6304.

As an embodiment, the fifth message is used to release RRC connection; the fifth message comprises a first length of time; the fifth message comprises that the first length of time is used to trigger the start of a second timer; the expired value of the second timer is equal to the first length of time; the starting time of the second timer is less than the expiration value of the second timer from the receiving time of the sixth message; the second timer is started earlier than the transmission 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 rrcreelease.

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

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

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

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

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

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

As a sub-embodiment of the above embodiment, the second timer comprises 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 an expired value of the second timer to the first time length indicated by the fifth message.

As an embodiment, the running status of the second timer is used for access barring checking.

As a sub-embodiment of the above embodiment, when the second timer is running, the access barring check is considered to be barred for access categories other than the class 0 and class 2 access categories.

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

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

As an embodiment, when the trigger cause of the second message is to forward an information bit generated at the second node, the reception of the first message does not affect the running state of the second timer.

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

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

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

As an embodiment, the fifth message is used for feeding 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 comprises a second length of time; the sixth message comprises that the second length of time is used to trigger a restart of a second timer; an expiration value of the second timer after the restart is equal to the second length of time.

As an embodiment, the sixth message is received later than the second message is sent; the sixth message comprises a second length of time; the sixth message comprises that the second length of time is used to trigger a restart of a second timer; the expired value after the restart of the second timer is equal to the second length of time; the trigger cause of the second message is to forward information bits generated at the second node.

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 comprises rrcreelease.

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

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

As a sub-embodiment of the above embodiment, the sixth message comprises 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 foregoing embodiment, a 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 equals 1, for example X2 equals 16.

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

As a sub-embodiment of the above embodiment, the sentence, the sixth message, including the second length of time, is used to trigger a restart of a second timer, includes the second timer starting immediately after stopping.

As a sub-embodiment of the above embodiment, said sentence, said sixth message comprises that said second length of time is used to trigger a restart of a second timer comprises that said second timer is stopped and said second timer is started in response to receiving said sixth message.

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

As an embodiment, the sixth message is used to release RRC connection; operating the first timer after receiving the sixth message, the operation being a stop or a continuation, the operation being related to a trigger cause of the second message; when the sixth message is received, the first timer is in a running state;

when the trigger cause of the second message is to forward information bits generated at the second node, the operation is to continue running or to 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, and when the trigger cause of the second message is for an information bit generated at the first node, the receiving 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 reason for the second message is for an information bit generated at the first node, the second timer is operated after receiving the first message, and the behavior operation is continued.

As a sub-embodiment of the above embodiment, the first node U11 receives an indication from the network to trigger the start of the second timer.

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 a stop of the second timer.

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

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

Example 7

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

In one embodiment, the first node receives a third message requesting an RRC connection of the second node.

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

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

For one embodiment, the second message includes a first field and the third message includes a second field; the first domain and the second domain are respectively used for indicating a request reason for requesting 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 domain and the third domain are the same; the third message is used to determine a value of the first domain.

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

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

As one embodiment, the first domain is a resumecuse domain of the second message.

For one embodiment, the first field is a resendapalishmenthouse field of the second message.

For one embodiment, the second field is an establishmencause field of the third message.

As an embodiment, the second domain is a resumecuse domain of the third message.

For one embodiment, the second field is a resessamblinghouse field of the third message.

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

As an embodiment, the third domain is a resumecuse domain of the fourth message.

For one embodiment, the third field is a resessamblinghouse field of the fourth message.

As one embodiment, if the second field of the third message is an establishmentause field, the third field of the fourth message is an establishmentause field.

As an embodiment, if the second domain of the third message is a resumecuse domain, the third domain of the fourth message is a resumecuse domain.

As one embodiment, if the second field of the third message is a resendabilitlistengoushouse field, the third field of the fourth message is a resendalistengoushouse 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 embodiment, if the second field of the third message is one of { emergency, highPriorityAccess, mt-Access, mo-Signalling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, mps-PriorityAccess, mcs-PriorityAccess }, 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 embodiment, if the second field of the third message is one of { 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 a value other than { emergency, highPriorityAccess, mt-Access, mo-signaling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, mps-PriorityAccess, mcs-PriorityAccess }.

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

As an embodiment, when the trigger 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 trigger 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 trigger 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 trigger 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 trigger 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-data.

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

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

As an embodiment, when the trigger 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 trigger 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, the reception of the third message is used to determine that there are information bits generated by the second node that need to be forwarded.

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

As an embodiment, the reception of the third message triggers the transmission of 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 a request reason is related to relaying.

As an embodiment, the reception of the third message triggers the sending of the second message, and the first domain indication of the second message is related to relaying.

As an embodiment, the first node maps the value of the second domain of the third message to an access type according to a preconfigured mapping table, and then maps the access type to the value of the first domain of the second message according to the preconfigured mapping table.

Example 8

Embodiment 8 illustrates a schematic diagram where a 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 comprises an RRC message.

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

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

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

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

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

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 not prematurely expired.

As an embodiment, the seventh message indicates an expiry time of the first timer if not intervened.

As an embodiment, the seventh message indicates a time determined by an 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 one embodiment, the seventh message indicates an expected expiration time of the first timer when the seventh message was sent.

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

As one 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 a QoS flow blocked due to the running of the first timer.

As an embodiment, the seventh message indicates a QoS flow that is 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 not prematurely expired.

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

As an embodiment, the seventh message indicates a time determined by an 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 one embodiment, the seventh message indicates an expected expiration time of the second timer at the time the seventh message was sent.

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

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

Example 9

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

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

a first transmitter 902 that transmits 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; operating the first timer after receiving the first message, the operation being a stop or a continuation of a run, the operation being related to a trigger cause of the second message;

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

the first transmitter 902, configured to send a fourth message through a Uu interface, where the fourth message is generated by the third message, and the fourth message is used to request an RRC connection of the second node; the third message and the fourth message comprise the same request reason.

As an embodiment, the first transmitter 902, transmits a second set of parameters, the first set of parameters being used to generate the second set of parameters; the second set of parameters is used to perform an access barring check for the transmission of the third message.

For one 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 domain and the third domain are the same; the third message is used to determine a value of the first domain;

As an embodiment, the first receiver 901 receives a fifth message and a sixth message, where the fifth message and the sixth message are respectively used to release an RRC connection; the fifth message comprises a first length of time; the fifth message comprises that the first length of time is used to trigger the start of a second timer; the expired value of the second timer is equal to the first length of time; the starting time of the second timer is less than the expiration value of the second timer from the receiving time of the sixth message; the second timer starts earlier than the second message is sent; the sixth message is received later than the second message is sent; the sixth message comprises a second length of time; the sixth message comprises that the second length of time is used to trigger a restart of a second timer; an expiration value of the second timer after the restart is equal to the second length of time; the running status of the second timer is used for access blocking checking.

As an embodiment, the first receiver 901 receives a sixth message, where the sixth message is used to release an RRC connection; operating the first timer after receiving the sixth message, the operation being a stop or a continuation of a run, the operation being related to a trigger cause of the second message; when the sixth message is received, the first timer is in a running state;

For one embodiment, the first transmitter 902 transmits a seventh message, the seventh message being 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 an industrial internet of things.

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

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

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

Example 10

Embodiment 10 illustrates a block diagram of a processing apparatus for use in a second node according to an embodiment of the present application; as shown in fig. 10. In fig. 10, the processing means 1000 in the second node comprises a second receiver 1002 and a second transmitter 1001. In the case of the embodiment 10, the following,

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

For one embodiment, second receiver 1002 receives a second set of parameters, the first set of parameters being used to generate the second set of parameters; the second set of parameters is used to perform an access blocking check for the transmission of the third message; in response to performing the access barring check, a third timer is started.

As an embodiment, the second receiver 1002 receives an eighth message, the eighth message being used to grant the RRC connection of the second node requested by the third message, or the eighth message being used to release the RRC connection of the second node requested by the third message; in response to receiving the eighth message, stopping the 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-mounted 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 an industrial internet of things.

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

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

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

Example 11

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

a third transmitter 1101 that transmits the first parameter set and the first message; the sender of the second message performs an access blocking check according to the first set of parameters; starting a first timer in response to performing the access barring check;

a third receiver 1102 that receives the 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; the sender of the second message operates the first timer after receiving the first message, wherein the operation is stopping or continuing to run, and the operation is related to the trigger reason of the second message;

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 transmits a fifth message and a sixth message, and the fifth message and the sixth message are respectively used for releasing RRC connection; the fifth message comprises a first length of time; the fifth message comprises that the first length of time is used to trigger the start of a second timer; the second timer has an expiration value equal to the first length of time; the starting time of the second timer is less than the expiration value of the second timer from the receiving time of the sixth message; the second timer starts earlier than the second message is sent; the sixth message is received later than the second message is sent; the sixth message comprises a second length of time; the sixth message comprises that the second length of time is used to trigger a restart of a second timer; the expired value after the restart of the second timer is equal to the second length of time; the running status of the second timer is used for access blocking checking.

For one embodiment, the third transmitter 1101 transmits a sixth message, the sixth message being used to release the RRC connection; the receiver of the sixth message operates the first timer after receiving the sixth message, wherein the operation is stopping or continuing to run, and the operation is related to the trigger reason of the second message; when the sixth message is received, the first timer is in a running state;

For one embodiment, the third receiver 1102 receives a seventh message, and the seventh message is used to indicate the first timer.

As an embodiment, the third transmitter 1101 transmits an eighth message, and the eighth message is used for granting 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 large delay differences.

As one embodiment, the third node is a satellite.

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

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

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

The third receiver 1102 includes at least one of the antenna 420, the receiver 418, the receive processor 470, the multi-antenna receive processor 472, the controller/processor 475, and the memory 476 of embodiment 4.

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

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

Claims

1. A first node for wireless communication, comprising:

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

2. The first node of claim 1, comprising:

the first receiver receives a third message through a PC5 interface, wherein the third message is used for requesting RRC connection of the second node;

the first transmitter transmits a fourth message through a Uu interface, wherein the fourth message is generated by the third message, and the fourth message is used for requesting RRC connection of the second node; the third message and the fourth message comprise the same request reason.

3. The first node of claim 2, comprising:

the first transmitter to transmit a second set of parameters, the first set of parameters being used to generate the second set of parameters; the second set of parameters is used to perform an access blocking check for the transmission of the third message.

4. The first node of claim 2 or 3,

the second message comprises a first domain, the third message comprises a second domain, and the fourth message comprises a third domain; the values of the second domain and the third domain are the same; the third message is used to determine a value of the first domain;

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

the first receiver receives a fifth message and a sixth message, wherein the fifth message and the sixth message are respectively used for releasing RRC connection; the fifth message comprises a first length of time; the fifth message comprises the first length of time used to trigger the start of a second timer; the second timer has an expiration value equal to the first length of time; the starting time of the second timer is less than the expiration value of the second timer from the receiving time of the sixth message; the second timer starts earlier than the second message is sent; the sixth message is received later than the second message is sent; the sixth message comprises a second length of time; the sixth message comprises that the second length of time is used to trigger a restart of a second timer; the expired value after the restart of the second timer is equal to the second length of time; the running status of the second timer is used for access blocking checking.

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

the first receiver receives a sixth message, the sixth message being used to release the RRC connection; operating the first timer after receiving the sixth message, the operation being a stop or a continuation, the operation being related to a trigger cause of the second message; when the sixth message is received, the first timer is in a running state;

7. The first node according to any 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 for wireless communication, comprising:

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

a first node that transmits 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; 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;

9. A third node for wireless communication, comprising:

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

receiving a first parameter set, and executing access blocking check according to the first parameter set; starting a first timer in response to performing the access barring check;

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

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

12. A method in a third node used for wireless communication, comprising:

transmitting a first set of parameters;

receiving a second message;

sending a first message;

a sender of the second message performs an access blocking check according to the first set of parameters; in response to performing the access barring check, starting a first timer; the second message is 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; the sender of the second message operates the first timer after receiving the first message, wherein the operation is stopping or continuing to run, and the operation is related to the trigger reason of the second message;