A method and device for wireless communication

By using the relay node to determine the access parameters according to the service characteristics in wireless communication, the network problem caused by the relay node not taking into account the service characteristics of the remote node is solved, and more efficient access control and service processing are achieved. .

CN115484691BInactive Publication Date: 2024-11-22SHANGHAI LANGBO COMM TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202110598044.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-05-31
Publication Date
2024-11-22
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

In wireless communication, the relay node does not take into account the service characteristics of the remote node when performing access control, which may lead to emergency service delays or be unnecessarily blocked, resulting in network out of control and congestion.

Method used

When performing access blocking checks in the relay node, the applicable access parameters are determined based on the service characteristics of the remote node, ensuring priority processing of emergency services, and adjusting access categories if necessary to avoid unnecessary blocking.

Benefits of technology

It effectively avoids network congestion and emergency service delays caused by access checks of relay nodes, ensures that the service requests of remote nodes are reasonably processed, and improves the reliability and fairness of the network.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115484691B_ABST
    Figure CN115484691B_ABST
Patent Text Reader

Abstract

The present application discloses a method and device for wireless communication, including: initiating an RRC access request and performing an access blocking check according to a second parameter; determining the second parameter according to a triggering reason for initiating the RRC access request; the second parameter is used to indicate the access category of the RRC access request of the first node; the present application ensures fairness and robustness of access blocking through the first parameter and the second parameter.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to a transmission method and device in a wireless communication system, and more particularly to a method and device for reducing service interruption, improving service continuity, enhancing reliability, and ensuring security in wireless communications. Background Art

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

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

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

[0005] In many communication scenarios, the use of relays is involved. For example, when a UE is not within the coverage area of ​​a cell, it can access the network through a relay, and the relay node can be another UE. When accessing the network through a relay, the selected relay node may have established an RRC connection with the network, or it may not have established an RRC connection. If the RRC connection has not been established, the relay node needs to establish an RRC connection to forward or relay the data of the remote node (remote UE). Both the remote node and the relay node need to establish an RRC connection with the network. The request for connection can be to establish a new RRC connection or to resume a suspended RRC connection. Whether it is a remote node or a relay node, if you want to request an RRC connection, you need to perform access control. The access control performed on the UE side can be implemented through a unified access control (UAC) mechanism. When performing access control, the UE needs to perform an access barring check. When the result of the check is not to block, the UE can access the network, otherwise the UE is prohibited from initiating an access request. The data of the remote node involves both the remote node and the relay node. In theory, access blocking checks can be performed in one or both of the remote node and the relay node, or the two can be separated. The access control check for the connection request of the remote node is performed at the remote node, and the relay node only performs access control checks for the access request triggered by its own data. If the relay node accesses the network in order to forward the information bits of the remote node, whether the relay node needs to perform access control is a problem that needs to be solved. If the relay node does not perform access control, it may cause access failure, the network cannot control the access business volume, and even abuse; if the relay node performs access control, the above problems can be avoided, but the emergency business of the remote node may not be accessed because the access check of the relay node fails, causing the remote node to suffer unnecessary losses.

[0006] With regard to the above-mentioned problems, this application provides a solution.

[0007] It should be noted that, in the absence of conflict, the embodiments and features in any node of the present application can be applied to any other node. In the absence of conflict, the embodiments and features in the embodiments of the present application can be arbitrarily combined with each other.

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

[0009] Initiate an RRC access request, and perform an access blocking check according to a second parameter; determine the second parameter according to a triggering cause for initiating the RRC access request; the second parameter is used to indicate an access category of the RRC access request of the first node;

[0010] The sentence determines the second parameter according to the triggering cause of initiating the RRC access request, including:

[0011] When the triggering cause of the behavior initiating the RRC access request is for information bits generated at the first node, the second parameter is indicated by a higher layer;

[0012] When the triggering reason for the behavior to initiate the RRC access request is to forward the information bits generated at the second node, whether the first parameter belongs to the first parameter set is used to determine the second parameter; the first parameter is used to indicate the access category of the second node.

[0013] As an embodiment, the problems to be solved by the present application include: when a relay node performs an access check, if it does not consider the service characteristics of the remote node, but performs the access check according to general or common access control parameters or according to the default configuration of a higher layer of the relay node, the emergency service of the remote node may be delayed.

[0014] As an embodiment, the benefits of the above method include: The method proposed in this application can solve the above problems. The need for the relay node to perform access control checks can avoid network out-of-control and congestion. At the same time, the access of the relay node also fully considers the service requests of the remote node. The parameters applicable to the access check of the relay node itself are reasonably determined according to the different service requests of the remote node, which can avoid the emergency services of the remote node from being improperly blocked.

[0015] Specifically, according to one aspect of the present application, a first wireless signal is received, where the first wireless signal includes a first message, and the first message is used to indicate the first parameter;

[0016] The triggering reason for initiating the RRC access request in the behavior is to forward the information bits generated at the second node.

[0017] Specifically, according to one aspect of the present application, a second wireless signal is received, the second wireless signal includes a second message, the second message is used to request RRC access of the second node; the second message includes a first cause, the first cause is used to indicate the cause of the RRC access requested by the second message, the first cause is associated with the first parameter; the first parameter is used to indicate the access category of the RRC access of the second node requested by the second message.

[0018] Specifically, according to one aspect of the present application, as a response to the behavior that the access blocking check is not blocked, a third message is sent, and the third message is used to request RRC access of the first node; the third message includes a second cause, and the second cause is used to indicate the reason for the RRC access requested by the third message; whether the second cause is associated with the second parameter is related to the triggering cause of the initiation of the RRC access request;

[0019] A fourth message is received, the fourth message being used to approve the request of the third message.

[0020] Specifically, according to one aspect of the present application, as a response to being blocked in performing an access blocking check, a first timer is started and a third wireless signal is sent, the third wireless signal includes a fifth message, the fifth message is used to indicate that access is blocked, and the fifth message is used to indicate the expiration time of the first timer; the operating status of the first timer is used for the access blocking check.

[0021] Specifically, according to one aspect of the present application, whether the fourth message is used to stop the second timer is related to the triggering cause of starting the RRC access request;

[0022] The second timer is associated with an access category; when the fourth message is received, the second timer is in a running state; and the running state of the second timer is used for access blocking check.

[0023] Specifically, according to one aspect of the present application, a fourth wireless signal is sent, the fourth wireless signal includes a sixth message, the sixth message is used to indicate an access category set that is not blocked from access; the access category of the RRC connection request of the second node indicated by the first parameter belongs to the access reason set that is not blocked from access indicated by the sixth message;

[0024] There is at least one timer associated with an access category maintained by the first node and in a running state; the running state of the timer associated with an access category maintained by the first node is used for access blocking check.

[0025] Specifically, according to one aspect of the present application, the first parameter is different from the second parameter, the second parameter does not belong to the first parameter set, and the first parameter set includes at least one access category.

[0026] Specifically, according to one aspect of the present application, when the behavior of initiating the RRC access request is for the information bits generated at the first node to be also forwarded at the information bits generated at the second node, the triggering reason for the behavior of initiating the RRC access request is considered to be for forwarding the information bits generated at the second node.

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

[0028] Specifically, according to one aspect of the present application, the first node is an Internet of Things terminal.

[0029] Specifically, according to one aspect of the present application, the first node is a relay.

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

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

[0032] The present application discloses a first node used for wireless communication, comprising:

[0033] A first transmitter initiates an RRC access request and performs an access blocking check according to a second parameter; the second parameter is determined according to a triggering cause of initiating the RRC access request; the second parameter is used to indicate an access category of the RRC access request of the first node;

[0034] The sentence determines the second parameter according to the triggering cause of initiating the RRC access request, including:

[0035] When the triggering cause of the behavior initiating the RRC access request is for information bits generated at the first node, the second parameter is indicated by a higher layer;

[0036] When the triggering reason for the behavior to initiate the RRC access request is to forward the information bits generated at the second node, whether the first parameter belongs to the first parameter set is used to determine the second parameter; the first parameter is used to indicate the access category of the second node.

[0037] As an embodiment, compared with the traditional solution, the present application has the following advantages: unified access control is executed and guaranteed, avoiding the access blocking check caused by the access triggered by the relay node due to the access of the remote UE from being circumvented. It is conducive to alleviating network congestion and ensuring access fairness in a congested state.

[0038] As an embodiment, compared with the traditional solution, the present application has the following advantages: the relay node notifies the network of its own access blocking situation, which is conducive to the network's scheduling. For example, when it is still in the access blocking state, only the data of the remote UE can be scheduled without scheduling the data of the relay UE, thus ensuring fairness.

[0039] As an embodiment, compared with the traditional solution, the present application has the following advantages: the relay node notifies the remote node of the access blocking situation, including the operation status and expiration time of the timer associated with the access category, which is beneficial to the relay selection of the remote node, and determines in advance whether to perform service transmission and access, reduces unnecessary signaling processes, and reduces latency.

[0040] As an embodiment, compared with the traditional solution, the present application has the following advantages: the emergency services of the remote UE will not be blocked by the relay node; the high-priority services of the remote node can also be properly handled by the relay node, and the access blocking check is performed using the parameters related to the access blocking check applicable to the high priority.

[0041] As an embodiment, compared with the traditional solution, the present application has the following advantages: when the remote UE initiates a low-priority service, the relay node can continue to use the access check parameters configured at its own higher layer to perform access check, which is conducive to avoiding network congestion as much as possible, because once accessed, the relay node may also send some information, such as access layer signaling, which will also occupy resources and aggravate network congestion. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0043] Figure 1 A flowchart showing initiating an RRC access request and performing an access blocking check according to a second parameter according to an embodiment of the present application is shown;

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

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

[0046] Figure 4 A first node according to an embodiment of the present application is shown;

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

[0048] Figure 6 A flow chart showing transmission according to an embodiment of the present application is shown;

[0049] Figure 7 A schematic diagram showing that the running state of a first timer is used for access blocking check according to an embodiment of the present application;

[0050] Figure 8 A schematic diagram showing that the running state of the second timer is used for access blocking check according to an embodiment of the present application;

[0051] Fig. 9 A schematic diagram showing whether a first parameter belongs to a first parameter set is used to determine a second parameter according to an embodiment of the present application;

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

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

[0054] Example 1

[0055] Embodiment 1 illustrates a flowchart of initiating an RRC access request according to an embodiment of the present application and performing an access blocking check according to a second parameter, as shown in the attached Figure 1 Attached Figure 1 In the figure, each box represents a step. It should be emphasized that the order of the boxes in the figure does not represent the temporal relationship between the steps represented.

[0056] In Embodiment 1, the first node in the present application initiates an RRC access request in step 101; performs an access blocking check according to the second parameter in step 102;

[0057] The first node determines the second parameter according to the triggering cause of initiating the RRC access request; the second parameter is used to indicate the access category of the RRC access request of the first node; and the sentence determines the second parameter according to the triggering cause of initiating the RRC access request, including:

[0058] When the triggering cause of the behavior initiating the RRC access request is for information bits generated at the first node, the second parameter is indicated by a higher layer;

[0059] When the triggering reason for the behavior to initiate the RRC access request is to forward the information bits generated at the second node, whether the first parameter belongs to the first parameter set is used to determine the second parameter; the first parameter is used to indicate the access category of the second node.

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

[0061] As an embodiment, the second node is a UE.

[0062] As an embodiment, the second node is a remote UE.

[0063] As an embodiment, the second node is any remote UE.

[0064] As an embodiment, the second node is any UE that requests relaying.

[0065] As an embodiment, the second node is any UE other than the first node.

[0066] As an embodiment, the interface for communication between the first node and the second node is a PC5 interface.

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

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

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

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

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

[0072] As an embodiment, the first node is a type I relay node of the second node.

[0073] As an embodiment, the first node is a type II relay node of the second node.

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

[0075] As an embodiment, the first node sends a first discovery message, and the first discovery message is used to instruct the first node to provide a relay service.

[0076] As a sub-embodiment of the above embodiment, the first discovery message includes a relay service code, and the relay service code is used to indicate that the relay service provided by the first node is an L2 relay service.

[0077] As a sub-embodiment of the above embodiment, the first discovery message includes that the relay service provided by the first node is an L2 relay service.

[0078] As a sub-embodiment of the above embodiment, the first discovery message is used for discovery or to be discovered.

[0079] As an embodiment, the behavior of initiating an RRC access request includes initiating an RRC connection establishment.

[0080] As an embodiment, the behavior of initiating an RRC access request includes initiating an RRC connection continuation.

[0081] As an embodiment, the behavior of initiating an RRC access request includes initiating an RRC connection reestablishment.

[0082] As an embodiment, the behavior of initiating an RRC access request does not include initiating an RRC connection reestablishment.

[0083] As an embodiment, the first parameter includes an access category (Access Category).

[0084] As an embodiment, the second parameter includes an access category (Access Category).

[0085] As an embodiment, the first parameter includes an access identity (Access Identity).

[0086] As an embodiment, the second parameter includes an access identity (Access Identity).

[0087] As an embodiment, the phrase access barring check is access barring check.

[0088] As an embodiment, when performing an access blocking check, the node performing the access blocking check generates a random number. If the generated random number is less than the first threshold, access is allowed; if the generated random number is not less than the first threshold, access is blocked; the first threshold is configured or pre-configured by the network.

[0089] As an embodiment, the result of the access blocking check only includes access blocked and access allowed, and the meaning of access allowed is equal to access not blocked.

[0090] As an embodiment, the second parameter is the access category corresponding to the RRC access request of the first node.

[0091] As an embodiment, the second parameter is the access category associated with the RRC access request of the first node.

[0092] As an embodiment, the second parameter is the access category of the RRC access request of the first node.

[0093] As an embodiment, the first parameter is the access category corresponding to the RRC access request of the second node.

[0094] As an embodiment, the first parameter is the access category associated with the RRC access request of the second node.

[0095] As an embodiment, the first parameter is the access category of the RRC access request of the second node.

[0096] As an embodiment, the reason for the RRC access request of the second node is used to determine the first parameter.

[0097] As a sub-embodiment of the above embodiment, there is a mapping relationship between the reason for the RRC access request of the second node and the first parameter.

[0098] As a sub-embodiment of the above embodiment, the reason for the RRC access request of the second node includes responding to paging.

[0099] As a sub-embodiment of the above embodiment, the reason for the RRC access request of the second node includes handover.

[0100] As a sub-embodiment of the above embodiment, the reason for the RRC access request of the second node includes for emergency services.

[0101] As a sub-embodiment of the above embodiment, the reason for the RRC access request of the second node includes a service defined by an operator.

[0102] As a sub-embodiment of the above embodiment, the reason for the RRC access request of the second node includes exception data for MO (Mobile originated).

[0103] As a sub-embodiment of the above embodiment, the reason for the RRC access request of the second node includes for a delay-insensitive service.

[0104] As a sub-embodiment of the above embodiment, the reason for the RRC access request of the second node includes non-access stratum signaling.

[0105] As a sub-embodiment of the above embodiment, the reason for the RRC access request of the second node includes a location request.

[0106] As a sub-embodiment of the above embodiment, the reason for the RRC access request of the second node includes data for a PDU session using suspended user plane resources.

[0107] As an embodiment, the value range of the first parameter is an integer between 0 and 63, including 0 and 63.

[0108] As an embodiment, the value range of the second parameter is an integer between 0 and 63, including 0 and 63.

[0109] As an embodiment, the value range of the first parameter is an integer between 0 and 15, including 0 and 15.

[0110] As an embodiment, the value range of the second parameter is an integer between 0 and 15, including 0 and 15.

[0111] As an embodiment, the sentence when the triggering reason for the behavior to initiate the RRC access request is for the information bit generated at the first node includes the following meaning: the generator of the information bit is the first node.

[0112] As an embodiment, the sentence when the triggering reason for the behavior to initiate the RRC access request is for the information bit generated at the first node includes the following meaning: the information bit is generated by the RRC entity or RRC layer of the first node.

[0113] As an embodiment, the sentence when the triggering reason for the behavior to initiate the RRC access request is for the information bit generated at the first node includes the following meaning: the information bit is generated by the PDCP entity or PDCP layer of the first node.

[0114] As an embodiment, the sentence when the triggering reason for the behavior to initiate the RRC access request is for the information bit generated at the first node includes the following meaning: the information bit is generated by the non-access layer of the first node.

[0115] As an embodiment, the sentence when the triggering reason of the behavior initiating the RRC access request is for the information bit generated at the first node includes the following meaning: the information bit is generated by the SDAP layer of the first node.

[0116] As an embodiment, the sentence when the triggering reason for the behavior to initiate the RRC access request is for the information bit generated at the first node includes the following meaning: the information bit belongs to a QoS flow of the first node.

[0117] As an embodiment, the sentence when the triggering reason for the behavior to initiate the RRC access request is for the information bits generated at the first node includes the following meaning: the information bits do not belong to the bits of other UEs using L2 relay.

[0118] As an embodiment, the sentence when the triggering reason for the behavior to initiate the RRC access request is for the information bits generated at the first node includes the following meaning: the requested RRC connection is for transmitting the information bits generated by the first node rather than for transmitting information bits from other UEs.

[0119] As an embodiment, the sentence when the triggering reason for the behavior to initiate the RRC access request is for the information bits generated at the first node includes the following meaning: the requested RRC connection is for transmitting the service of the first node rather than for transmitting the service from other UEs.

[0120] As an embodiment, the sentence when the triggering reason for the behavior to initiate the RRC access request is for the information bits generated at the first node includes the following meaning: the requested RRC connection is not for relay.

[0121] As an embodiment, the sentence when the triggering reason for the behavior to initiate the RRC access request is for the information bits generated at the first node includes the following meaning: the requested RRC connection is not for layer 2 relay.

[0122] As an embodiment, the sentence when the triggering reason for the behavior to initiate the RRC access request is to forward the information bits generated at the second node includes the following meaning: the generator of the information bits is the second node.

[0123] As an embodiment, the sentence when the triggering reason of the behavior initiating the RRC access request is to forward the information bits generated at the second node includes the following meaning: the information bits are generated by the RRC entity or RRC layer of the second node.

[0124] As an embodiment, the sentence when the triggering reason for the behavior to initiate the RRC access request is to forward the information bits generated at the second node includes the following meaning: the information bits are generated by the PDCP entity or PDCP layer of the second node.

[0125] As an embodiment, the sentence when the triggering reason of the behavior initiating the RRC access request is to forward the information bits generated at the second node includes the following meaning: the information bits are generated by the non-access layer of the second node.

[0126] As an embodiment, the sentence when the triggering reason of the behavior initiating the RRC access request is to forward the information bits generated at the second node includes the following meaning: the information bits are generated by the SDAP layer of the second node.

[0127] As an embodiment, the sentence when the triggering reason of the behavior initiating the RRC access request is to forward the information bits generated at the second node includes the following meaning: the information bits belong to a QoS flow of the second node.

[0128] As an embodiment, the sentence when the triggering reason of the behavior initiating the RRC access request is to forward the information bits generated at the second node includes the following meaning: the information bits belong to bits of other remoteUEs using L2 relay.

[0129] As an embodiment, the sentence when the triggering reason for the behavior to initiate the RRC access request is to forward the information bits generated at the second node includes the following meaning: the requested RRC connection is to transmit the information bits generated by the second node.

[0130] As an embodiment, the sentence when the triggering reason for the behavior to initiate the RRC access request is to forward the information bits generated at the second node includes the following meaning: the requested RRC connection is for transmitting the service of the second node.

[0131] As an embodiment, the sentence when the triggering reason of the behavior initiating the RRC access request is to forward the information bits generated at the second node includes the following meaning: the requested RRC connection is for relaying.

[0132] As an embodiment, the sentence when the triggering reason for the behavior to initiate the RRC access request is to forward the information bits generated at the second node includes the following meaning: the requested RRC connection is for layer 2 relay.

[0133] As an embodiment, the sentence when the triggering reason for the behavior to initiate the RRC access request is to forward the information bits generated at the second node includes the following meaning: the requested RRC connection is for L2 or Layer-2 or Layer2 relay.

[0134] As an embodiment, when the behavior initiates the RRC access request for information bits generated at the first node and forwarding information bits generated at the second node, the triggering cause of the behavior initiating the RRC access request is considered to be for forwarding the information bits generated at the second node.

[0135] As an embodiment, when the behavior initiates an RRC access request for information bits generated at the first node and forwarding information bits generated at the second node, whether the first parameter belongs to a first parameter set is used to determine the second parameter; the first parameter is used to indicate the access category of the second node.

[0136] As an embodiment, when the behavior of initiating an RRC access request is for transmitting information bits including the second node, the triggering cause of the behavior of initiating the RRC access request is considered to be for forwarding information bits generated at the second node.

[0137] As an embodiment, when the behavior initiates an RRC access request in order to transmit information bits including a second node, whether the first parameter belongs to a first parameter set is used to determine the second parameter; the first parameter is used to indicate an access category of the second node.

[0138] As an embodiment, the first parameter is different from the second parameter.

[0139] As an embodiment, the second parameter does not belong to the first parameter set.

[0140] As an embodiment, the first parameter set includes at least one access category.

[0141] As an embodiment, the first parameter set includes emergency services.

[0142] As an embodiment, the first parameter set includes high priority services.

[0143] As an embodiment, the first parameter set includes emergency.

[0144] As an embodiment, the first parameter set includes {emergency, highPriorityAccess}.

[0145] As an embodiment, the first parameter set includes {emergency, highPriorityAccess, mps-PriorityAccess, mcs-PriorityAccess}.

[0146] As an embodiment, the first parameter set includes {access identity 1, access identity 2}.

[0147] As an embodiment, the first parameter set includes at least one of {access identity 11, access identity 12, access identity 13, access identity 14, access identity 15}.

[0148] As an embodiment, the first parameter set includes {access category 2}.

[0149] As an embodiment, the first parameter set includes {access category 0}.

[0150] As an embodiment, the first parameter set includes {access category 0, access category 2}.

[0151] As an embodiment, the first node is in an RRC idle state when initiating an RRC access request.

[0152] As an embodiment, the first node is in an RRC inactive state when initiating an RRC access request.

[0153] As an embodiment, the sentence includes that the second parameter is indicated by a higher layer, and the second parameter is indicated by a non-access layer.

[0154] As an embodiment, the sentence includes that the second parameter is indicated by a higher layer, and the second parameter is indicated by an RRC layer.

[0155] As an embodiment, the sentence includes the second parameter indicated by a higher layer, and the second parameter is indicated by the PC5-S layer.

[0156] As an embodiment, the sentence includes the second parameter indicated by a higher layer, and the second parameter is indicated by a core network.

[0157] As an embodiment, the serving cell of the first node indicates a second parameter set, and the second parameter set is used for access barring check.

[0158] As an embodiment, the second parameter set includes blocking parameters.

[0159] As an embodiment, the second parameter set includes unified access barring (UAC) parameters.

[0160] As an embodiment, the second parameter set includes uac-BarringInfo.

[0161] As an embodiment, the second parameter set includes uac-BarringForCommon.

[0162] As an embodiment, the second parameter set includes uac-BarringPerPLMN-List.

[0163] As an embodiment, the second parameter set includes uac-BarringInfoSetList.

[0164] As an embodiment, the second parameter set includes uac-AccessCategory1-SelectionAssistanceInfo.

[0165] As an embodiment, the phrase access barring check is access barring check.

[0166] Example 2

[0167] Embodiment 2 illustrates a schematic diagram of a network architecture according to an embodiment of the present application, as shown in the attached Figure 2 Attached Figure 2 The V2X communication architecture under the 5G NR (New Radio), LTE (Long-Term Evolution) and LTE-A (Long-Term Evolution Advanced) system architecture is described. The 5G NR or LTE network architecture may be referred to as 5GS (5G System) / EPS (Evolved Packet System) or some other appropriate terminology.

[0168] The V2X communication architecture of embodiment 2 includes UE (User Equipment) 201, UE 241, 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 can be interconnected with other access networks, but these entities / interfaces are not shown for simplicity. As shown, the V2X communication architecture provides packet switching services, but technicians in the field will easily understand that the various concepts presented throughout this application can be extended to networks that provide circuit switching services or other cellular networks. NG-RAN includes NR Node B (gNB) 203 and other gNBs 204. gNB 203 provides user and control plane protocol termination towards UE 201. gNB 203 can be connected to other gNBs 204 via an Xn interface (e.g., backhaul). The gNB 203 may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP (transmit receive node), or some other suitable term. The gNB 203 provides an access point to the 5GC / EPC 210 for the UE 201. Examples of UE 201 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop computer, a personal digital assistant (PDA), a satellite radio, non-terrestrial base station communications, satellite mobile communications, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a drone, an aircraft, a narrowband Internet of Things device, a machine type communication device, a land vehicle, an automobile, a wearable device, or any other similarly functional device. The UE 201 may also be referred to by those skilled in the art as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable term. The gNB 203 is connected to the 5GC / EPC 210 via an S1 / NG interface.5GC / EPC210 includes MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MME / AMF / SMF214, S-GW (Service Gateway) / UPF (User Plane Function) 212 and P-GW (Packet Data Network Gateway) / UPF213. MME / AMF / SMF211 is the control node that handles the signaling between UE201 and 5GC / EPC210. ​​In general, MME / AMF / SMF211 provides bearer and connection management. All user IP (Internet Protocal) packets are transmitted through S-GW / UPF212, which itself is connected to P-GW / UPF213. P-GW provides UE IP address allocation and other functions. P-GW / UPF213 is connected to Internet service 230. Internet service 230 includes Internet protocol services corresponding to operators, which may specifically include Internet, intranet, IMS (IP Multimedia Subsystem) and packet switching streaming services. The ProSe function 250 is a logical function for network-related behaviors required for Proximity-based Service (ProSe); including DPF (Direct Provisioning Function), Direct Discovery Name Management Function, EPC-level Discovery ProSe Function, etc. The ProSe application server 230 has the functions of storing EPC ProSe user identities, mapping between application layer user identities and EPC ProSe user identities, and allocating ProSe restricted code suffix pools.

[0169] As an embodiment, the UE201 and the UE241 are connected via a PC5 reference point (Reference Point).

[0170] As an embodiment, the ProSe function 250 is connected to the UE 201 and the UE 241 via a PC3 reference point respectively.

[0171] As an embodiment, the ProSe function 250 is connected to the ProSe application server 230 via a PC2 reference point.

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

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

[0174] As an embodiment, the second node in the present application is UE241.

[0175] As an embodiment, the wireless link between the UE201 and the UE241 corresponds to the side link (Sidelink, SL) in this application.

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

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

[0178] As an embodiment, the UE 201 supports relay transmission.

[0179] As an embodiment, the UE 241 supports relay transmission.

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

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

[0182] As an embodiment, the gNB203 is a macrocellular base station.

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

[0184] As an embodiment, the gNB203 is a picoCell base station.

[0185] As an embodiment, the gNB203 is a flying platform device.

[0186] As an embodiment, the gNB203 is a satellite device.

[0187] Example 3

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

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

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

[0191] As an embodiment, the first message in the present application is generated in RRC306 or PC5-S307.

[0192] As an embodiment, the fifth message in the present application is generated in RRC306 or PC5-S307.

[0193] As an embodiment, the sixth message in the present application is generated in RRC306 or PC5-S307.

[0194] As an embodiment, the second message in the present application is generated in RRC306 or PC5-S307.

[0195] As an embodiment, the third message in the present application is generated in RRC306.

[0196] As an embodiment, the fourth message in the present application is generated in RRC306.

[0197] As an embodiment, the first wireless signal in the present application is generated by PHY301 or PHY351.

[0198] As an embodiment, the second wireless signal in the present application is generated by PHY301 or PHY351.

[0199] As an embodiment, the third wireless signal in the present application is generated by PHY301 or PHY351.

[0200] As an embodiment, the fourth line signal in the present application is generated by PHY301 or PHY351.

[0201] As an embodiment, the first parameter set in the present application is generated in the non-access layer.

[0202] As an embodiment, the second parameter set in the present application is generated in the non-access layer.

[0203] Example 4

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

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

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

[0207] In 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 transmission from the second communication device 410 to the first communication device 450, the controller / processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation to the first communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for retransmission of lost packets and signaling to the first communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (i.e., the physical layer). The transmit processor 416 implements coding and interleaving to facilitate forward error correction (FEC) at the second communication device 410, as well as mapping of signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing on the coded and modulated symbols to generate one or more spatial streams. The transmit processor 416 then maps each spatial stream to a subcarrier, multiplexes it with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then uses an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain multi-carrier symbol stream. The multi-antenna transmit processor 471 then performs a transmit analog precoding / beamforming operation on the time-domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multi-carrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream, and then provides it to a different antenna 420.

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

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

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

[0211] As an embodiment, the first communication device 450 apparatus includes: at least one processor and at least one memory, the at least one memory includes a computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor, and the first communication device 450 apparatus at least:

[0212] As an embodiment, the first communication device 450 includes: a memory storing a computer-readable instruction program, wherein the computer-readable instruction program generates actions when executed by at least one processor, and the actions include:

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

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

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

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

[0217] As an embodiment, the first communication device 450 is a relay.

[0218] As an embodiment, the second communication device 410 is a UE.

[0219] As an embodiment, the receiver 456 (including the antenna 460), the receiving processor 452 and the controller / processor 490 are used to receive the first wireless signal in the present application.

[0220] As an embodiment, the receiver 456 (including the antenna 460), the receiving processor 452 and the controller / processor 490 are used to receive the second wireless signal in the present application.

[0221] As an embodiment, the receiver 456 (including the antenna 460), the receiving processor 452 and the controller / processor 490 are used to receive the fourth message in the present application.

[0222] As an embodiment, the transmitter 456 (including the antenna 460), the transmission processor 455 and the controller / processor 490 are used to send the third wireless signal in the present application.

[0223] As an embodiment, the transmitter 456 (including the antenna 460), the transmit processor 455 and the controller / processor 490 are used to transmit the fourth line signal in the present application.

[0224] As an embodiment, the transmitter 456 (including the antenna 460), the transmit processor 455 and the controller / processor 490 are used to send the third message in the present application.

[0225] Example 5

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

[0227] for First node U01 , receiving a first wireless signal in step S5101; receiving a second wireless signal in step S5102; initiating an RRC access request in step S5103; performing an access blocking check according to a second parameter in step S5104; sending a third message in step S5105; and receiving a fourth message in step S5106.

[0228] for Second node U02 , sending a first wireless signal in step S5201; sending a second wireless signal in step S5202.

[0229] for The third node U03 , receiving the third message in step S5301; sending the fourth message in step S5302.

[0230] In embodiment 5, the first node U01 determines the second parameter according to the triggering cause of initiating the RRC access request; the second parameter is used to indicate the access category of the RRC access request of the first node;

[0231] The sentence determines the second parameter according to the triggering cause of initiating the RRC access request, including:

[0232] When the triggering cause of the behavior initiating the RRC access request is for information bits generated at the first node U01, the second parameter is indicated by a higher layer;

[0233] When the triggering reason for the behavior to initiate the RRC access request is to forward the information bits generated at the second node U02, whether the first parameter belongs to the first parameter set is used to determine the second parameter; the first parameter is used to indicate the access category of the second node.

[0234] As an embodiment, the second node U02 is a UE.

[0235] As an embodiment, the third node U02 is a base station.

[0236] As an embodiment, the third node U02 is a resident cell of the first node U01.

[0237] As an embodiment, the third node U02 is a cell selected by the first node U01.

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

[0239] As an embodiment, the first node U01 is a relay for connecting the second node U02 to the network.

[0240] As a sub-embodiment of the above embodiment, the first node U01 is a layer 2 relay.

[0241] As an embodiment, the second node U02 is any remote UE that accesses the network through the first node U01.

[0242] As an embodiment, the first wireless signal is sent at the PC5 interface.

[0243] As an embodiment, the first wireless signal is sent via a secondary link.

[0244] As an embodiment, the physical channel occupied by the first wireless signal includes PSSCH (Physical Sidelink Shared Channel).

[0245] As an embodiment, the first wireless signal includes a first MAC PDU, the first MAC PDU includes a first MAC sub-PDU, the header of the first MAC sub-PDU is a first MAC sub-header, the first MAC sub-header includes the 16 most significant bits of a first identity and the 8 most significant bits of a second identity; the second identity is used to identify the first node U01.

[0246] As a sub-embodiment of the above embodiment, the first identity and the second identity are link layer identities respectively.

[0247] As a sub-embodiment of the above embodiment, the first identity and the second identity are Layer-2 identities respectively.

[0248] As a sub-embodiment of the above embodiment, the second identity is used to identify the first node U01.

[0249] As a sub-embodiment of the above embodiment, the first identity is used to identify the second node U02.

[0250] As a sub-embodiment of the above embodiment, the first MAC sub-PDU includes the first message.

[0251] As an embodiment, the first message includes an RRC message.

[0252] As an embodiment, the first message is an RRC message.

[0253] As an embodiment, the first message includes a PC5-RRC message.

[0254] As an embodiment, the first message includes a PC5-S message.

[0255] As an embodiment, the first message includes a Direct link establishment request.

[0256] As an embodiment, the first message includes a Direct link modification request.

[0257] As an embodiment, the first message includes RRCReconfigurationSidelink.

[0258] As an embodiment, the first message includes RRCSetupRequest.

[0259] As an embodiment, the first message includes RRCResumeRequest.

[0260] As an embodiment, the first message includes RRCResumeRequest1.

[0261] As an embodiment, the first message includes RRCConnectionSetupRequest.

[0262] As an embodiment, the first message includes RRCConnectionSetupResume.

[0263] As an embodiment, the logical channel occupied by the first message includes CCCH.

[0264] As an embodiment, the logical channel occupied by the first message includes CCCH1.

[0265] As an embodiment, the logical channel occupied by the first message includes DCCH.

[0266] As an embodiment, the first message requests to establish an RRC connection.

[0267] As an embodiment, the first message requests to continue the RRC connection.

[0268] As an embodiment, the first message is used to indicate the first parameter.

[0269] As a sub-embodiment of the above embodiment, the first message includes the parameter.

[0270] As a sub-embodiment of the above embodiment, the first message includes establishmentCause, and there is a mapping relationship between the establishmentCause and the first parameter. The first message indicates the first parameter by indicating the establishmentCause.

[0271] As a sub-embodiment of the above embodiment, the first message includes resumeCause, and there is a mapping relationship between resumeCause and the first parameter. The first message indicates the first parameter by indicating resumeCause.

[0272] As a sub-embodiment of the above embodiment, the first message indicates a reason for RRC access of the second node, and there is a mapping relationship between the reason for RRC access of the second node indicated by the first message and the first parameter.

[0273] As a sub-embodiment of the above embodiment, the first message indicates that the reason for the RRC access of the second node includes data initiated by the mobile terminal.

[0274] As a sub-embodiment of the above embodiment, the first message indicates that the reason for the RRC access of the second node includes a paging response.

[0275] As a sub-embodiment of the above embodiment, the first message indicates that the reason for the RRC access of the second node includes a high priority service.

[0276] As a sub-embodiment of the above embodiment, the first message indicates that the reason for the RRC access of the second node includes emergency services.

[0277] As an embodiment, the second wireless signal is sent at the PC5 interface.

[0278] As an embodiment, the second wireless signal is sent via a secondary link.

[0279] As an embodiment, the physical channel occupied by the second wireless signal includes PSSCH (Physical Sidelink Shared Channel).

[0280] As an embodiment, the physical channel occupied by the second wireless signal includes PSCCH (Physical Sidelink Control Channel).

[0281] As an embodiment, the second wireless signal includes a second MAC PDU, the second MAC PDU includes a second MAC sub-PDU, the header of the second MAC sub-PDU is a second MAC sub-header, the second MAC sub-header includes the 16 most significant bits of the first identity and the 8 most significant bits of the second identity; the second identity is used to identify the first node U01.

[0282] As a sub-embodiment of the above embodiment, the first identity and the second identity are link layer identities respectively.

[0283] As a sub-embodiment of the above embodiment, the first identity and the second identity are Layer-2 identities respectively.

[0284] As a sub-embodiment of the above embodiment, the second identity is used to identify the first node U01.

[0285] As a sub-embodiment of the above embodiment, the first identity is used to identify the second node U02.

[0286] As a sub-embodiment of the above embodiment, the second MAC sub-PDU includes the first message.

[0287] As an embodiment, the second wireless signal includes a second MAC PDU, the second MAC PDU includes a second MAC sub-PDU, the header of the second MAC sub-PDU is a second MAC sub-header, and the second MAC sub-header includes 16 most significant bits of the third identity and 8 most significant bits of the fourth identity;

[0288] As a sub-embodiment of the above embodiment, the third identity and the fourth identity are link layer identities respectively.

[0289] As a sub-embodiment of the above embodiment, the third identity and the fourth identity are Layer-2 identities respectively.

[0290] As a sub-embodiment of the above embodiment, the fourth identity is used to identify the destination link layer identity.

[0291] As a sub-embodiment of the above embodiment, the third identity is used to identify the second node U02.

[0292] As a sub-embodiment of the above embodiment, the second MAC sub-PDU includes the first message.

[0293] As a sub-embodiment of the above embodiment, the fourth identity is used to identify a link layer identity used for broadcasting.

[0294] As a sub-embodiment of the above embodiment, the fourth identity is used to identify a link layer identity used for multicast.

[0295] As an embodiment, the second message includes an RRC message.

[0296] As an embodiment, the second message includes a PC5-RRC message.

[0297] As an embodiment, the second message includes a PC5-S message.

[0298] As an embodiment, the second message includes a discovery message.

[0299] As an embodiment, the sending method of the second message includes broadcasting.

[0300] As an embodiment, the sending method of the second message includes multicast.

[0301] As an embodiment, the sending method of the second message includes unicast.

[0302] As an embodiment, the second message is used to request RRC access of the second node; the second message includes a first cause, the first cause is used to indicate the reason for the RRC access requested by the second message, and the first cause is associated with the first parameter; the first parameter is used to indicate the access category of the RRC access of the second node requested by the second message.

[0303] As a sub-embodiment of the above embodiment, the second message is sent via SRB0.

[0304] As a sub-embodiment of the above embodiment, the second message is not encrypted.

[0305] As a sub-embodiment of the above embodiment, the second message includes RRCSetupRequest.

[0306] As a sub-embodiment of the above embodiment, the second message is RRCResumeRequest.

[0307] As a sub-embodiment of the above embodiment, the second message RRCResumeRequest1.

[0308] As a sub-embodiment of the above embodiment, the first cause includes establishmentCause.

[0309] As a sub-embodiment of the above embodiment, the first cause includes resumeCause.

[0310] As a sub-embodiment of the above embodiment, there is a mapping relationship between the first cause and the first parameter.

[0311] As a sub-embodiment of the above embodiment, the first parameter is used to derive the first cause.

[0312] As a sub-embodiment of the above embodiment, the first parameter and a fixed or preconfigured mapping rule are used together to derive the first cause.

[0313] As a sub-embodiment of the above embodiment, the access category of the RRC access of the second node indicated by the first parameter and the first cause included in the second message are consistent.

[0314] As a sub-embodiment of the above embodiment, the first parameter is the access category of the RRC access request of the second node.

[0315] As a sub-embodiment of the above embodiment, the RRC access requested by the second message includes RRC connection establishment.

[0316] As a sub-embodiment of the above embodiment, the RRC access requested by the second message includes RRC connection continuation.

[0317] As a sub-embodiment of the above embodiment, the value of the first cause belongs to one of {emergency, highPriorityAccess, mt-Access, mo-Signalling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, mps-PriorityAccess, mcs-PriorityAccess}.

[0318] As a sub-embodiment of the above embodiment, the value of the first reason belongs to one of {emergency, highPriorityAccess, mt-Access, mo-Signalling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, rna-Update, mps-PriorityAccess, mcs-PriorityAccess}.

[0319] As a sub-embodiment of the above embodiment, the value of the first cause belongs to one of {reconfigurationFailure, handoverFailure, otherFailure, relayreselection, relayfailure}.

[0320] As an embodiment, the reception of the first wireless signal triggers the first node U01 to initiate the RRC access request.

[0321] As an embodiment, the reception of the first message triggers the first node U01 to initiate the RRC access request.

[0322] As an embodiment, the sentence performs access blocking check according to the second parameter, including: the second parameter is an access category, and the second parameter serves as an input parameter of the access blocking check.

[0323] As an embodiment, the sentence performs access blocking check according to the second parameter, including: when the second parameter is 0, the result of the access blocking check is allowing access.

[0324] As an embodiment, the sentence performs access blocking check according to the second parameter, including: when the second parameter is 2, the result of the access blocking check is allowing access.

[0325] As an embodiment, the sentence performs an access blocking check according to a second parameter, including: when the second parameter is a positive integer other than 0 or 2, the first node U01 generates a first random number, and when the first random number is less than a first blocking threshold, access is blocked; when the first random number is greater than the first blocking threshold, access is allowed, wherein the first blocking threshold is for the access category indicated by the second parameter, and the first blocking threshold is configured by a system broadcast message.

[0326] As an embodiment, the first node U01 needs to first perform a blocking check before sending the third message.

[0327] As an embodiment, the first node U01 needs to first perform a blocking check according to the second parameter before sending the third message.

[0328] As an embodiment, as an unblocked response to the access blocking check performed by the behavior, the first node U01 sends the third message, and the third message is used to request RRC access of the first node U01; the third message includes a second cause, and the second cause is used to indicate the reason for the RRC access requested by the third message; whether the second cause is associated with the second parameter is related to the triggering cause of initiating the RRC access request.

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

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

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

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

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

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

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

[0336] As a sub-embodiment of the above embodiment, the third message is sent via SRB0.

[0337] As a sub-embodiment of the above embodiment, the physical channel occupied by the third message includes PUSCH.

[0338] As a sub-embodiment of the above embodiment, the result of performing the blocking check according to the second parameter in step S5104 is that the access is allowed.

[0339] As a sub-embodiment of the above embodiment, the phrase "a response of not being blocked as the action of performing the access blocking check" means a response of allowing access as a result of the action of performing the access blocking check.

[0340] As a sub-embodiment of the above embodiment, the sentence that the third message is used to request RRC access of the first node U01 includes: the third message is used to request RRC connection establishment of the first node U01.

[0341] As a sub-embodiment of the above embodiment, the sentence that the third message is used to request RRC access of the first node U01 includes: the third message is used to request continuation of the RRC connection of the first node U01.

[0342] As a sub-embodiment of the above embodiment, the second cause includes establishmentCause.

[0343] As a sub-embodiment of the above embodiment, the second cause includes resumeCauseCause.

[0344] As a sub-embodiment of the above embodiment, the value of the second reason belongs to one of {emergency, highPriorityAccess, mt-Access, mo-Signalling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, mps-PriorityAccess, mcs-PriorityAccess}.

[0345] As a sub-embodiment of the above embodiment, the value of the second cause belongs to one of {emergency, highPriorityAccess, mt-Access, mo-Signalling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, rna-Update, mps-PriorityAccess, mcs-PriorityAccess}.

[0346] As a sub-embodiment of the above embodiment, the value of the second cause belongs to one of {reconfigurationFailure, handoverFailure, otherFailure, relayreselection, relayfailure}.

[0347] As a sub-embodiment of the above embodiment, when the triggering reason for the behavior to initiate the RRC access request is for the information bit generated at the first node U01, the access category indicated by the second parameter determines the second cause, the value range of the access category indicated by the second parameter is more than one, the value range of the second cause is more than one, and there is a mapping relationship between the second parameter and the second cause.

[0348] As a sub-embodiment of the above embodiment, when the triggering reason for the behavior to initiate the RRC access request is for the information bit generated at the first node U01, the access category indicated by the second parameter determines the second reason, the access category indicated by the second parameter has a value range of more than one, the value range of the second reason is more than one, and the second parameter and the second reason can be obtained through a predefined mapping table.

[0349] As a sub-embodiment of the above embodiment, when the triggering reason for the behavior to initiate the RRC access request is to forward the information bit generated in the second node U02, no matter how the second parameter takes the value, the value of the second reason is a spare bit in release 16.

[0350] As a sub-embodiment of the above embodiment, when the triggering reason for the behavior to initiate the RRC access request is to forward the information bits generated in the second node U02, no matter what the value of the second parameter is, the value of the second reason is relay.

[0351] As a sub-embodiment of the above embodiment, when the triggering reason for the behavior to initiate the RRC access request is to forward the information bits generated in the second node U02, no matter how the second parameter takes the value, the value of the second reason includes relay.

[0352] As a sub-embodiment of the above embodiment, when the triggering reason for the behavior to initiate the RRC access request is to forward the information bits generated at the second node U02, the second parameter is determined by the first parameter, and no matter how the first parameter takes a value, the value of the second reason includes relay.

[0353] As a sub-embodiment of the above embodiment, when the triggering reason for the behavior to initiate the RRC access request is to forward the information bits generated at the second node U02, the second parameter is the same as the first parameter, and no matter what the value of the first parameter is, the value of the second reason includes relay.

[0354] As an embodiment, the fourth message is used to approve the request of the third message.

[0355] As a sub-embodiment of the above embodiment, the fourth message is an RRC message.

[0356] As a sub-embodiment of the above embodiment, the fourth message is transmitted through the Uu interface.

[0357] As a sub-embodiment of the above embodiment, the physical channel occupied by the fourth message includes PDSCH (physical downlink shared channel).

[0358] As a sub-embodiment of the above embodiment, the physical channel occupied by the fourth message includes PDCCH (physical downlink control channel).

[0359] As a sub-embodiment of the above embodiment, the fourth message includes RRCSetup.

[0360] As a sub-embodiment of the above embodiment, the fourth message includes RRCResume.

[0361] As a sub-embodiment of the above embodiment, the fourth message includes RRCEstablishment.

[0362] As a sub-embodiment of the above embodiment, the fourth message includes RRCConnectionSetup.

[0363] As a sub-embodiment of the above embodiment, the fourth message includes RRCConnectionResume.

[0364] As a sub-embodiment of the above embodiment, the fourth message includes RRCConnectionEstablishment.

[0365] As an embodiment, the sentence that the triggering reason for initiating the RRC access request is to forward the information bits generated at the second node includes that the triggering reason for initiating the RRC access request is to relay the information bits generated at the second node.

[0366] As an embodiment, whether the fourth message is used to stop the second timer is related to the triggering cause of initiating the RRC access request; wherein, the second timer is associated with an access category; when the fourth message is received, the second timer is in a running state; and the running state of the second timer is used for access blocking check.

[0367] As a sub-embodiment of the above embodiment, for an access attempt of an access category associated with the second timer, the second timer is started when the access attempt is blocked after performing an access blocking check.

[0368] As a sub-embodiment of the above embodiment, after cell selection or reselection is performed, the second timer is stopped.

[0369] As a sub-embodiment of the above embodiment, when entering the RRC connected state, the second timer is stopped.

[0370] As a sub-embodiment of the above embodiment, when an RRCReconfiguration message including reconfigurationWithSync is received, the second timer is stopped.

[0371] As a sub-embodiment of the above embodiment, when the PCell is changed, the second timer is stopped.

[0372] As a sub-embodiment of the above embodiment, when MobilityFromNRCommand is received, the second timer is stopped.

[0373] As a sub-embodiment of the above embodiment, when RRCRelease. is received, the second timer is stopped.

[0374] As a sub-embodiment of the above embodiment, expiration of the second timer is used to determine that access blocking of an access category associated with the second timer is released.

[0375] As a sub-embodiment of the above embodiment, when the second timer is running, access of an access category associated with the second timer is blocked.

[0376] As a sub-embodiment of the above embodiment, the second timer includes T390.

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

[0378] As a sub-embodiment of the above embodiment, when the triggering reason for the behavior to initiate the RRC access request is for the information bit generated at the first node U01, the fourth message is used to stop the second timer.

[0379] As a sub-embodiment of the above embodiment, when the triggering reason of the behavior to initiate the RRC access request is to forward the information bits generated in the second node U02, the fourth message is not used to stop the second timer.

[0380] Example 6

[0381] Embodiment 6 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in the attached Figure 6 Attached Figure 6 In the example, U11 corresponds to the first node of the present application, and U12 corresponds to the second node of the present application. It is particularly noted that the order in this example does not limit the signal transmission order and implementation order in the present application, wherein the steps in F61 and F62 are optional; Example 6 is based on Example 5, and the parts required but not shown in Example 6 can be referred to Example 5.

[0382] for First node U11 , sending a fourth wireless signal in step S6101; starting an RRC access request in step S6102; performing an access blocking check according to the second parameter in step S6103; and sending a third wireless signal in step S6104.

[0383] for Second node U12 , receiving the fourth wireless signal in step S6201; receiving the third wireless signal in step S6202.

[0384] As an embodiment, the fourth wireless signal is sent at the PC5 interface.

[0385] As an embodiment, the fourth wireless signal is sent via a secondary link.

[0386] As an embodiment, the physical channel occupied by the fourth wireless signal includes PSSCH (Physical Sidelink Shared Channel).

[0387] As an embodiment, the physical channel occupied by the fourth wireless signal includes PSCCH (Physical Sidelink Control Channel).

[0388] As an embodiment, the fourth wireless signal includes a fourth MAC PDU, the fourth MAC PDU includes a fourth MAC sub-PDU, the header of the fourth MAC sub-PDU is a fourth MAC sub-header, the fourth MAC sub-header includes the 16 most significant bits of the first identity and the 8 most significant bits of the second identity; the second identity is used to identify the first node U11.

[0389] As a sub-embodiment of the above embodiment, the first identity and the second identity are link layer identities respectively.

[0390] As a sub-embodiment of the above embodiment, the first identity and the second identity are Layer-2 identities respectively.

[0391] As a sub-embodiment of the above embodiment, the second identity is used to identify the first node U11.

[0392] As a sub-embodiment of the above embodiment, the first identity is used to identify the second node U12.

[0393] As a sub-embodiment of the above embodiment, the fourth MAC sub-PDU includes the sixth message.

[0394] As an embodiment, the fourth wireless signal includes a fifth MAC PDU, the fifth MAC PDU includes a fifth MAC sub-PDU, the header of the fifth MAC sub-PDU is a fifth MAC sub-header, and the fifth MAC sub-header includes 16 most significant bits of the third identity and 8 most significant bits of the fourth identity;

[0395] As a sub-embodiment of the above embodiment, the third identity and the fourth identity are link layer identities respectively.

[0396] As a sub-embodiment of the above embodiment, the third identity and the fourth identity are Layer-2 identities respectively.

[0397] As a sub-embodiment of the above embodiment, the fourth identity is used to identify the destination link layer identity.

[0398] As a sub-embodiment of the above embodiment, the third identity is used to identify the second node U12.

[0399] As a sub-embodiment of the above embodiment, the fourth MAC sub-PDU includes the sixth message.

[0400] As a sub-embodiment of the above embodiment, the fourth identity is used to identify a link layer identity used for broadcasting.

[0401] As a sub-embodiment of the above embodiment, the fourth identity is used to identify a link layer identity used for multicast.

[0402] As an embodiment, the fourth wireless signal includes a sixth message.

[0403] As an embodiment, the sixth message is used to indicate a set of access categories that are not blocked from access; the access category of the RRC connection request of the second node indicated by the first parameter belongs to the set of access reasons that are not blocked from access indicated by the sixth message;

[0404] There is at least one timer associated with an access category maintained by the first node and in a running state; the running state of the timer associated with an access category maintained by the first node is used for access blocking check.

[0405] As an embodiment, the sixth message includes a PC5-RRC message.

[0406] As an embodiment, the sixth message includes a PC5-S message.

[0407] As an embodiment, the sixth message includes a discovery message.

[0408] As an embodiment, the sixth message includes RRCReconfigurationSidelink.

[0409] As an embodiment, the sixth message includes a set of access categories that are not blocked from access.

[0410] As an embodiment, the sixth message includes a set of access categories that are blocked from access.

[0411] As a sub-embodiment of the above embodiment, the sixth message indicates the access category set that is not blocked from access by indicating the access category set that is blocked from access.

[0412] As an embodiment, any access category is associated with a timer, and when the timer associated with any access category is in a running state, access belonging to any access category is blocked.

[0413] As an embodiment, the first access category is any access category, the first access category is associated with a timer, and when the timer associated with the first access category is in a running state, access belonging to the first access category is blocked.

[0414] As an embodiment, the first access category is any access category, the first access category is associated with a timer, and when the timer associated with the first access category is in a running state, the access associated with the first access category is blocked.

[0415] As an embodiment, a timer associated with any access category in the set of access categories that are not blocked from access is not in a running state.

[0416] As an embodiment, the timer associated with the access category is T390.

[0417] As an embodiment, the first parameter belongs to the set of access categories that are not blocked from access.

[0418] As an embodiment, when there is at least one timer associated with any access category maintained by the first node U11 and in a running state, the sixth message is used to indicate a set of access categories that are not blocked from access.

[0419] As an embodiment, when the timer associated with any access category maintained by the first node U11 is not in a running state, the sixth message does not include a set of access categories that are not blocked from access.

[0420] As a sub-embodiment of the above embodiment, the timer associated with any access category is T390.

[0421] As a sub-embodiment of the above embodiment, the sixth message is used to indicate that a set of access categories that are not blocked from access indicates that the first parameter is not restricted.

[0422] As a sub-embodiment of the above embodiment, the sixth message is used to indicate a set of access categories that are not blocked from access and the first parameter may be any access category.

[0423] As an embodiment, the sentence that the running status of the timer associated with an access category maintained by the first node is used for access blocking check includes: the running status of the timer associated with an access category maintained by the first node is used as an input parameter of the access blocking check.

[0424] As an embodiment, the sentence that the running status of the timer associated with an access category maintained by the first node is used for access blocking check includes: when the timer associated with an access category maintained by the first node is in a running state, the access belonging to the access category maintained by the first node is blocked.

[0425] As an embodiment, as a blocked response to the behavior performing the access blocking check, the first node U11 starts a first timer and sends a third wireless signal, the third wireless signal includes a fifth message, the fifth message is used to indicate that the access is blocked, and the fifth message is used to indicate the expiration time of the first timer; the running status of the first timer is used for the access blocking check.

[0426] As a sub-embodiment of this embodiment, when the result of the access blocking check performed by the behavior according to the second parameter is access blocking or access is not allowed, the first timer is started and the third wireless signal is sent.

[0427] As a sub-embodiment of this embodiment, the first timer is T390.

[0428] As a sub-embodiment of this embodiment, the third wireless signal is sent at the PC5 interface.

[0429] As a sub-embodiment of this embodiment, the third wireless signal is sent via a secondary link.

[0430] As a sub-embodiment of this embodiment, the physical channel occupied by the third wireless signal includes PSSCH (Physical Sidelink Shared Channel).

[0431] As a sub-embodiment of this embodiment, the physical channel occupied by the third wireless signal includes PSCCH (Physical Sidelink Control Channel, physical sidelink shared channel).

[0432] As a sub-embodiment of this embodiment, the fifth message includes a PC5-RRC message.

[0433] As a sub-embodiment of this embodiment, the fifth message includes a PC5-S message.

[0434] As a sub-embodiment of this embodiment, the fifth message includes a discovery message.

[0435] As a sub-embodiment of this embodiment, the fifth message includes Direct link release request.

[0436] As a sub-embodiment of this embodiment, the fifth message includes RRCReconfigurationSidelink.

[0437] As a sub-embodiment of this embodiment, the fifth message includes RRCReconfigurationFailureSidelink.

[0438] As a sub-embodiment of this embodiment, the fifth message includes the expiration time of the first timer.

[0439] As a sub-embodiment of this embodiment, the fifth message includes a time determined by an expiration value of the first timer after the start of the first timer.

[0440] As a sub-embodiment of this embodiment, the fifth message indicates the time when the access category associated with the first timer is blocked.

[0441] As a sub-embodiment of this embodiment, the fifth message indicates a time interval during which the access category associated with the first timer is blocked.

[0442] As a sub-embodiment of this embodiment, the fifth message indicates a time when the access category associated with the first timer is not blocked.

[0443] As a sub-embodiment of this embodiment, the fifth message indicates a time interval in which the access category associated with the first timer is not blocked.

[0444] As a sub-embodiment of this embodiment, the first timer is associated with the access category indicated by the first parameter.

[0445] As a sub-embodiment of this embodiment, the fifth message is used to trigger the second node U12 to perform relay selection or relay reselection.

[0446] Example 7

[0447] Embodiment 7 illustrates a schematic diagram of a first timer operating state being used for access blocking check according to an embodiment of the present application, as shown in the attached figure. Figure 7 shown.

[0448] As an embodiment, the first timer is associated with an access category.

[0449] As an embodiment, the first timer is associated with the access category indicated by the first parameter.

[0450] As an embodiment, the first timer is associated with the access category of the first parameter.

[0451] As an embodiment, for an access attempt of an access category associated with the first timer, the first timer is started when the access attempt is blocked after performing an access blocking check.

[0452] As an embodiment, after cell selection or reselection is performed, the first timer is stopped.

[0453] As an embodiment, when entering the RRC connection state, the first timer is stopped.

[0454] As an embodiment, when an RRCReconfiguration message including reconfigurationWithSync is received, the first timer is stopped.

[0455] As an embodiment, when the PCell is changed, the first timer is stopped.

[0456] As an embodiment, when MobilityFromNRCommand is received, the first timer is stopped.

[0457] As an embodiment, when RRCRelease. is received, the first timer is stopped.

[0458] As an embodiment, the expiration of the first timer is used to determine that the access blocking of the access category associated with the first timer is lifted.

[0459] As an embodiment, while the first timer is running, access to an access category associated with the first timer is blocked.

[0460] As an embodiment, the first timer includes T390.

[0461] As an embodiment, the first timer includes T302.

[0462] As an embodiment, when the first timer is in a running state, access to an access category associated with the first timer is blocked.

[0463] As an embodiment, when the first timer is in the running state, access of access categories other than access category '0' and access category '2' is blocked.

[0464] As an embodiment, when the first timer is in a running state, access of access categories other than the access categories included in the first parameter set is blocked.

[0465] As an embodiment, the behavior access includes RRC access.

[0466] As an embodiment, the behavior access includes sending data.

[0467] As an embodiment, the behavioral access includes initiating a service.

[0468] As an embodiment, the behavior access includes establishing an RRC connection.

[0469] As an embodiment, the behavior access includes establishing a PDU session.

[0470] Example 8

[0471] Embodiment 8 illustrates a schematic diagram of the operation state of the second timer according to an embodiment of the present application being used for access blocking check, as shown in the attached figure. Figure 8 shown.

[0472] As an embodiment, the second timer is associated with an access category.

[0473] As an embodiment, the second timer is associated with an access category other than the access category indicated by the first parameter.

[0474] As an embodiment, the second timer is associated with an access category other than the access category of the second parameter.

[0475] As an embodiment, for an access attempt of an access category associated with the second timer, the second timer is started when the access attempt is blocked after performing an access blocking check.

[0476] As an embodiment, after cell selection or reselection is performed, the second timer is stopped.

[0477] As an embodiment, when entering the RRC connection state, the second timer is stopped.

[0478] As an embodiment, when an RRCReconfiguration message including reconfigurationWithSync is received, the second timer is stopped.

[0479] As an embodiment, when the PCell is changed, the second timer is stopped.

[0480] As an embodiment, when MobilityFromNRCommand is received, the second timer is stopped.

[0481] As an embodiment, when RRCRelease. is received, the second timer is stopped.

[0482] As an embodiment, the expiration of the second timer is used to determine that the access blocking of the access category associated with the second timer is lifted.

[0483] As an embodiment, while the second timer is running, access to an access category associated with the second timer is blocked.

[0484] As an embodiment, the second timer includes T390.

[0485] As an embodiment, the second timer includes T302.

[0486] As an embodiment, when the second timer is in a running state, access to an access category associated with the second timer is blocked.

[0487] As an embodiment, when the second timer is in the running state, access of access categories other than access category '0' and access category '2' is blocked.

[0488] As an embodiment, when the second timer is in a running state, access of access categories other than the access categories included in the first parameter set is blocked.

[0489] As an embodiment, the behavior access includes RRC access.

[0490] As an embodiment, the behavior access includes sending data.

[0491] As an embodiment, the behavioral access includes initiating a service.

[0492] As an embodiment, the behavior access includes establishing an RRC connection.

[0493] As an embodiment, the behavior access includes establishing a PDU session.

[0494] Example 9

[0495] Embodiment 9 illustrates a schematic diagram of whether a first parameter belongs to a first parameter set according to an embodiment of the present application and is used to determine a second parameter, as shown in the attached figure. Fig. 9 shown.

[0496] As an embodiment, the first parameter set includes K1 parameters, any parameter of the K1 parameters is an access category, and K1 is a positive integer.

[0497] As a sub-embodiment of the above embodiment, K1 is equal to 64.

[0498] As a sub-embodiment of the above embodiment, K1 is equal to 1.

[0499] As a sub-embodiment of the above embodiment, K1 is equal to 2.

[0500] As a sub-embodiment of the above embodiment, K1 is equal to 3.

[0501] As a sub-embodiment of the above embodiment, K1 is equal to 4.

[0502] As a sub-embodiment of the above embodiment, K1 is equal to 8.

[0503] As a sub-embodiment of the above embodiment, the first parameter set includes access category '0'.

[0504] As a sub-embodiment of the above embodiment, the first parameter set includes access category '2'.

[0505] As a sub-embodiment of the above embodiment, the first parameter set includes an access category corresponding to a high priority service.

[0506] As a sub-embodiment of the above embodiment, the first parameter set includes an access category corresponding to an emergency service.

[0507] As an embodiment, the first parameter set only includes access category '0'.

[0508] As an embodiment, the first parameter set only includes access category '2'.

[0509] As an embodiment, the first parameter set only includes access category '0' and access category '2'.

[0510] As an embodiment, the first parameter set only includes access categories.

[0511] As an embodiment, the first parameter set is fixed.

[0512] As an embodiment, the first parameter set is system configured.

[0513] As an embodiment, the first parameter set is preconfigured.

[0514] As an embodiment, the first parameter set is configured via a SIB message.

[0515] As an embodiment, the first parameter set is defined by a protocol.

[0516] As an embodiment, the first parameter set includes access category '0'.

[0517] As an embodiment, the first parameter set includes access category '2'.

[0518] As an embodiment, the first parameter is an access category.

[0519] As an embodiment, when the first parameter belongs to the first parameter set, the first parameter is determined as the second parameter.

[0520] As an embodiment, when the first parameter belongs to the first parameter set, if the second parameter does not belong to the first parameter set, the first parameter is determined as the second parameter; when the first parameter belongs to the first parameter set, if the second parameter belongs to the first parameter set, the first parameter is not used to be determined as the second parameter.

[0521] As an embodiment, when the first parameter belongs to the first parameter set, if the second parameter does not belong to the first parameter set, the first parameter is determined as the second parameter; when the first parameter belongs to the first parameter set, if the second parameter belongs to the first parameter set and the value of the access category indicated by the second parameter is greater than the value of the access category indicated by the first parameter, the first parameter is determined as the second parameter; when the first parameter belongs to the first parameter set, if the second parameter belongs to the first parameter set and the value of the access category indicated by the second parameter is not greater than the value of the access category indicated by the first parameter, the first parameter is not used to be determined as the second parameter.

[0522] As an embodiment, when the first parameter belongs to the first parameter set and the value of the access category indicated by the second parameter is greater than the value of the access category indicated by the first parameter, the first parameter is determined to be the second parameter.

[0523] As an embodiment, when the first parameter does not belong to the first parameter set, the first parameter is not used to determine the second parameter.

[0524] As an embodiment, when the first parameter does not belong to the first parameter set, the second parameter is indicated by a higher layer of the first node.

[0525] As an embodiment, when the first parameter does not belong to the first parameter set, the second parameter is indicated by a non-access layer of the first node.

[0526] As an embodiment, when the first parameter does not belong to the first parameter set, the second parameter is fixed.

[0527] As an embodiment, when the first parameter does not belong to the first parameter set, the second parameter is default.

[0528] As an embodiment, when the first parameter does not belong to the first parameter set, the second parameter is defined by the protocol.

[0529] As an embodiment, when the first parameter does not belong to the first parameter set, the second parameter is indicated by a higher layer.

[0530] As an embodiment, when the first parameter does not belong to the first parameter set, the second parameter is the access category corresponding to mo-Signalling.

[0531] As an embodiment, when the first parameter does not belong to the first parameter set, the second parameter is the access category corresponding to mo-relay.

[0532] As an embodiment, when the first parameter does not belong to the first parameter set, the second parameter is the access category corresponding to the relay.

[0533] As an embodiment, when the first parameter does not belong to the first parameter set, the second parameter is access category '8'.

[0534] As an embodiment, when the first parameter belongs to the first parameter set, the larger one of the first parameter and the third parameter is determined as the value of the second parameter; wherein the third parameter is an access category indicated by a higher layer.

[0535] As a sub-embodiment of the above embodiment, the access category indicated by the third parameter is the access category of the RRC access request of the first node.

[0536] Example 10

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

[0538] The first transmitter 1002 initiates an RRC access request and performs an access blocking check according to a second parameter; the second parameter is determined according to a triggering cause of initiating the RRC access request; the second parameter is used to indicate an access category of the RRC access request of the first node 1000;

[0539] The sentence determines the second parameter according to the triggering cause of initiating the RRC access request, including:

[0540] When the triggering cause of the behavior initiating the RRC access request is for information bits generated at the first node 1000, the second parameter is indicated by a higher layer;

[0541] When the triggering reason for the behavior to initiate the RRC access request is to forward the information bits generated at the second node, whether the first parameter belongs to the first parameter set is used to determine the second parameter; the first parameter is used to indicate the access category of the second node.

[0542] As an embodiment, a first receiver 1001 receives a first wireless signal, where the first wireless signal includes a first message, and the first message is used to indicate the first parameter;

[0543] The triggering reason for initiating the RRC access request in the behavior is to forward the information bits generated at the second node.

[0544] As an embodiment, the first receiver 1001 receives a second wireless signal, the second wireless signal includes a second message, the second message is used to request RRC access of the second node; the second message includes a first cause, the first cause is used to indicate the cause of the RRC access requested by the second message, the first cause is associated with the first parameter; the first parameter is used to indicate the access category of the RRC access of the second node requested by the second message.

[0545] As an embodiment, the first transmitter 1002, as a response to the behavior of performing an access blocking check that is not blocked, sends a third message, the third message is used to request RRC access of the first node 1000; the third message includes a second cause, the second cause is used to indicate the reason for the RRC access requested by the third message; whether the second cause is associated with the second parameter is related to the triggering cause of initiating the RRC access request;

[0546] The first receiver 1001 receives a fourth message, where the fourth message is used to approve the request of the third message.

[0547] As an embodiment, the first transmitter 1002, as a response to being blocked in performing the access blocking check, starts a first timer and sends a third wireless signal, wherein the third wireless signal includes a fifth message, wherein the fifth message is used to indicate that access is blocked, and the fifth message is used to indicate the expiration time of the first timer; the operating status of the first timer is used for the access blocking check.

[0548] As an embodiment, whether the fourth message is used to stop the second timer is related to the triggering cause of starting the RRC access request;

[0549] The second timer is associated with an access category; when the fourth message is received, the second timer is in a running state; and the running state of the second timer is used for access blocking check.

[0550] As an embodiment, the first transmitter 1002 sends a fourth wireless signal, the fourth wireless signal includes a sixth message, the sixth message is used to indicate an access category set that is not blocked from access; the access category of the RRC connection request of the second node indicated by the first parameter belongs to the access reason set that is not blocked from access indicated by the sixth message;

[0551] Among them, there is at least one timer associated with an access category maintained by the first node 1000 and is in a running state; the running state of the timer associated with an access category maintained by the first node 1000 is used for access blocking check.

[0552] As an embodiment, the first parameter is different from the second parameter, the second parameter does not belong to the first parameter set, and the first parameter set includes at least one access category.

[0553] As an embodiment, when the behavior initiates the RRC access request for information bits generated at the first node 1000 and also forwards information bits generated at the second node, the triggering cause of the behavior initiating the RRC access request is considered to be for forwarding the information bits generated at the second node.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0567] The above is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. 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, wherein: include: The first transmitter initiates an RRC access request and performs an access blocking check according to a second parameter; Determining the second parameter according to the triggering cause of initiating the RRC access request; The second parameter is used to indicate an access category of the RRC access request of the first node; The determining the second parameter according to the triggering cause of initiating the RRC access request includes: When the triggering reason for initiating the RRC access request is for information bits generated at the first node, the second parameter is indicated by a higher layer; When the triggering reason for initiating the RRC access request is to forward the information bits generated at the second node, whether the first parameter belongs to the first parameter set is used to determine the second parameter; the first parameter is used to indicate the access category of the second node.

2. The first node according to claim 1, characterized in that: include: A first receiver receives a first wireless signal, where the first wireless signal includes a first message, and the first message is used to indicate the first parameter; The triggering reason for initiating the RRC access request is to forward the information bits generated at the second node.

3. The first node according to claim 1, characterized in that: include: A first receiver receives a second wireless signal, where the second wireless signal includes a second message, where the second message is used to request RRC access of the second node; The second message includes a first cause, the first cause is used to indicate the cause of the RRC access requested by the second message, the first cause is associated with the first parameter; the first parameter is used to indicate the access category of the RRC access of the second node requested by the second message.

4. The first node according to any one of claims 2 to 3, characterized in that: include: The first transmitter sends a third message as a response to the access blocking check being performed and being not blocked, the third message being used to request RRC access of the first node; the third message includes a second cause, the second cause being used to indicate a cause of the RRC access requested by the third message; whether the second cause is associated with the second parameter is related to a triggering cause of initiating the RRC access request; The first receiver receives a fourth message, where the fourth message is used to approve the request of the third message.

5. The first node according to any one of claims 1 to 4, characterized in that: include: The first transmitter, as a response to being blocked from performing the access blocking check, starts a first timer and sends a third wireless signal, wherein the third wireless signal includes a fifth message, wherein the fifth message is used to indicate that access is blocked, and the fifth message is used to indicate an expiration time of the first timer; the operating status of the first timer is used for the access blocking check.

6. The first node according to claim 4, characterized in that: Whether the fourth message is used to stop the second timer is related to the triggering cause of starting the RRC access request; The second timer is associated with an access category; when the fourth message is received, the second timer is in a running state; and the running state of the second timer is used for access blocking check.

7. The first node according to any one of claims 1 to 6, characterized in that: The first transmitter sends a fourth wireless signal, the fourth wireless signal includes a sixth message, the sixth message is used to indicate an access category set that is not blocked by access; the category of the RRC connection request of the second node indicated by the first parameter belongs to the access reason set that is not blocked by access indicated by the sixth message; There is at least one timer associated with an access category maintained by the first node and in a running state; the running state of the timer associated with an access category maintained by the first node is used for access blocking check.

8. The first node according to any one of claims 1 to 7, characterized in that: The first parameter is different from the second parameter, the second parameter does not belong to the first parameter set, and the first parameter set includes at least one access category.

9. The first node according to any one of claims 1 to 8, characterized in that: When the initiation of the RRC access request is for information bits generated at the first node and forwarded to information bits generated at the second node, the triggering cause of initiating the RRC access request is considered to be for forwarding information bits generated at the second node.

10. A method in a first node for wireless communication, wherein: include: Initiate an RRC access request and perform an access blocking check according to the second parameter; Determining the second parameter according to the triggering cause of initiating the RRC access request; The second parameter is used to indicate an access category of the RRC access request of the first node; The determining the second parameter according to the triggering cause of initiating the RRC access request includes: When the triggering reason for initiating the RRC access request is for information bits generated at the first node, the second parameter is indicated by a higher layer; When the triggering reason for initiating the RRC access request is to forward the information bits generated at the second node, whether the first parameter belongs to the first parameter set is used to determine the second parameter; the first parameter is used to indicate the access category of the second node.

11. The method in the first node according to claim 10, characterized in that: receiving a first wireless signal, wherein the first wireless signal includes a first message, and the first message is used to indicate the first parameter; The triggering reason for initiating the RRC access request is to forward the information bits generated at the second node.

12. The method in the first node according to claim 10 or 11, characterized in that: A second wireless signal is received, wherein the second wireless signal includes a second message, wherein the second message is used to request RRC access of the second node; the second message includes a first cause, wherein the first cause is used to indicate the cause of the RRC access requested by the second message, and the first cause is associated with the first parameter; and the first parameter is used to indicate the access category of the RRC access of the second node requested by the second message.

13. The method in the first node according to any one of claims 10 to 12, characterized in that: As a response to the access blocking check being performed and being not blocked, sending a third message, the third message being used to request RRC access of the first node; the third message including a second cause, the second cause being used to indicate a cause of the RRC access requested by the third message; whether the second cause is associated with the second parameter is related to the triggering cause of initiating the RRC access request; A fourth message is received, the fourth message being used to approve the request of the third message.

14. The method in the first node according to any one of claims 10 to 13, characterized in that: As a response to being blocked from performing the access blocking check, a first timer is started and a third wireless signal is sent, wherein the third wireless signal includes a fifth message, wherein the fifth message is used to indicate that access is blocked and the fifth message is used to indicate an expiration time of the first timer; the operating status of the first timer is used for the access blocking check.

15. The method in the first node according to claim 13, characterized in that: Whether the fourth message is used to stop the second timer is related to the triggering cause of starting the RRC access request; The second timer is associated with an access category; when the fourth message is received, the second timer is in a running state; and the running state of the second timer is used for access blocking check.

16. The method in the first node according to any one of claims 10 to 15, characterized in that: sending a fourth wireless signal, the fourth wireless signal including a sixth message, the sixth message being used to indicate a set of access categories that are not blocked from access; the access category of the RRC connection request of the second node indicated by the first parameter belongs to the set of access reasons that are not blocked from access indicated by the sixth message; There is at least one timer associated with an access category maintained by the first node and in a running state; the running state of the timer associated with an access category maintained by the first node is used for access blocking check.

17. The method in the first node according to any one of claims 10 to 16, characterized in that: The first parameter is different from the second parameter, the second parameter does not belong to the first parameter set, and the first parameter set includes at least one access category.

18. The method in the first node according to any one of claims 10 to 17, characterized in that: When the initiation of the RRC access request is for information bits generated at the first node and forwarded to information bits generated at the second node, the triggering cause of initiating the RRC access request is considered to be for forwarding information bits generated at the second node.