CN115484691A - Method and equipment used for wireless communication - Google Patents

Method and equipment used for wireless communication Download PDF

Info

Publication number
CN115484691A
CN115484691A CN202110598044.9A CN202110598044A CN115484691A CN 115484691 A CN115484691 A CN 115484691A CN 202110598044 A CN202110598044 A CN 202110598044A CN 115484691 A CN115484691 A CN 115484691A
Authority
CN
China
Prior art keywords
node
access
parameter
message
rrc
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202110598044.9A
Other languages
Chinese (zh)
Inventor
陈宇
张晓博
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shanghai Langbo Communication Technology Co Ltd
Original Assignee
Shanghai Langbo Communication Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shanghai Langbo Communication Technology Co Ltd filed Critical Shanghai Langbo Communication Technology Co Ltd
Priority to CN202110598044.9A priority Critical patent/CN115484691A/en
Publication of CN115484691A publication Critical patent/CN115484691A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/22—Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Landscapes

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

Abstract

The application discloses a method and a device used for wireless communication, comprising the following steps: starting an RRC access request, and executing access blocking check according to the second parameter; determining the second parameter according to the trigger reason for starting the RRC access request; the second parameter is used to indicate an access category of the RRC access request of the first node; the method and the device ensure fairness and robustness of access blocking through the first parameter and the second parameter.

Description

Method and equipment used for wireless communication
Technical Field
The present application relates to a transmission method and apparatus in a wireless communication system, and more particularly, to a method and apparatus for reducing service interruption, improving service continuity, enhancing reliability, and improving security in wireless communication.
Background
In the future, the application scenes of the wireless communication system are more and more diversified, and different application scenes put different performance requirements on the system. In order to meet different performance requirements of various application scenarios, research on New air interface technology (NR, new Radio) (or Fifth Generation, 5G) is decided over #72 sessions of 3GPP (3 rd Generation Partner Project) RAN (Radio Access Network), and standardization Work on NR begins over 3GPP RAN #75 sessions over WI (Work Item ) of NR.
In Communication, both LTE (Long Term Evolution) and 5G NR relate to Reliable accurate reception of information, optimized energy efficiency ratio, determination of information validity, flexible resource allocation, scalable system structure, efficient non-access stratum information processing, lower service interruption and dropped rate, support for Low power consumption, which is important for normal Communication between a base station and user equipment, reasonable scheduling of resources, and balance of system load, so to speak, high throughput rate, meet Communication requirements of various services, improve spectrum utilization rate, and improve foundation of service quality, and are indispensable for enhanced Mobile BroadBand (eMBB) Communication, ultra Mobile Low Latency (ullc) or enhanced Machine Type Communication (eMTC). Meanwhile, in the Internet of Things in the field of industry, in V2X (Vehicular to X), communication between devices (Device to Device) is performed, in communication of unlicensed spectrum, in user communication quality monitoring, network planning optimization, in NTN (Non-terrestrial Network communication), in TN (terrestrial Network communication), in Dual connectivity (Dual connectivity) system, in wireless resource management and codebook selection of multiple antennas, there are wide requirements in signaling design, neighborhood management, service management, and beamforming, and the transmission mode of information is divided into broadcast and unicast, and both transmission modes are indispensable for the 5G system, because they help to meet the above requirements.
With the continuous increase of the scenes and the complexity of the system, higher requirements are put forward on the reduction of the interruption rate, the reduction of the time delay, the enhancement of the reliability, the enhancement of the stability of the system, the flexibility of the service and the saving of the power, and meanwhile, the compatibility among different versions of different systems needs to be considered when the system is designed.
Disclosure of Invention
In various communication scenarios, the use of relays may be involved, e.g. when one UE is not within the coverage area of a cell, the network may be accessed by a relay, and the relay node may be another UE. When the relay accesses the network, the selected relay node may or may not have established an RRC connection with the network, and if the RRC connection is not established, the relay node needs to establish the RRC connection to forward or relay data of a remote node (remote UE). Both the remote node and the relay node need to establish an RRC connection with the network. The requested connection may be a newly established RRC connection or may be a resume (resume) suspended RRC connection. No matter the remote node or the relay node, if RRC and connection are requested, access Control needs to be performed, and the Access Control performed at the UE end may be implemented by a Unified Access Control (UAC) mechanism. When performing Access control, the UE needs to perform Access blocking Check (Access blocking Check), and when the Check result is that no blocking is performed, the UE can Access the network, otherwise, the UE prohibits initiating an Access request. The data of the remote node relates to the remote node and the relay node at the same time, theoretically, access blocking check can be executed on one or two of the remote node and the relay node, the remote node and the relay node can also be separated from each other, access control check aiming at the connection request of the remote node is executed on the remote node, and the relay node only executes the access control check aiming at the access request triggered by the data of the relay node. If the relay node accesses the network for forwarding the information bits of the remote node, it is a problem to be solved whether the relay node needs to perform access control. If the relay node does not execute access control, access failure can be caused, the network can not control the accessed traffic, and even the abused condition occurs; if the relay node performs access control, the above-mentioned problems may be avoided, but it may occur that the emergency service of the remote node may not be accessed because the access check of the relay node is not passed, so that the remote node suffers unnecessary loss.
In view of the above, the present application provides a solution.
It should be noted that, in the case of no conflict, the embodiments and features in the embodiments in any node of the present application may be applied to any other node. The embodiments and features of the embodiments of the present application may be combined with each other arbitrarily without conflict.
The application discloses a method in a first node used for wireless communication, comprising:
starting an RRC access request, and executing access blocking check according to the second parameter; determining the second parameter according to the trigger reason for starting the RRC access request; the second parameter is used to indicate an access category of the RRC access request of the first node;
wherein the sentence determines the second parameter according to the trigger reason for starting the RRC access request, and the method comprises the following steps:
the second parameter is indicated by a higher layer when the trigger cause of the behavior-initiated RRC access request is for an information bit generated at the first node;
when the trigger reason for the behavior-initiated RRC access request is to forward information bits generated at the second node, whether the first parameter belongs to a first set of parameters is used to determine the second parameter; the first parameter is used to indicate an access category of the second node.
As an embodiment, the problem to be solved by the present application includes: when the relay node performs the access check, if the access check is performed according to the access control parameters which are generic or general or are configured by default at a higher layer of the relay node without considering the service characteristics of the remote node, the emergency service of the remote node may be delayed.
As an example, the benefits of the above method include: the method proposed by the present application can solve the above problems. The relay node needs to execute access control check to avoid the out-of-control and congestion of the network, meanwhile, the access of the relay node also fully considers the service request of the remote node, and parameters suitable for the access check of the relay node are reasonably determined according to different service requests of the remote node, so that the emergency service of the remote node can be prevented from being blocked inappropriately.
In particular, according to an aspect of the present application, a first wireless signal is received, the first wireless signal including a first message, the first message being used to indicate the first parameter;
wherein the trigger reason for the behavior to initiate the RRC access request is to forward information bits generated at the second node.
Specifically, according to an aspect of the present application, a second wireless signal is received, where the second wireless signal includes a second message, and the second message is used for requesting RRC access of the second node; the second message comprises a first reason indicating a reason for the RRC access requested by the second message, the first reason being associated with the first parameter; the first parameter is used to indicate an access category of the RRC access of the second node requested by the second message.
Specifically, according to an aspect of the present application, a third message is sent as an unblocked response to the action performing an access blocking check, the third message being used to request RRC access of the first node; the third message comprises a second reason for indicating a reason for the RRC access requested by the third message; whether the second reason is associated with the second parameter, relating to the trigger reason for initiating the RRC access request;
receiving a fourth message, the fourth message used to approve the request of the third message.
Specifically, according to one aspect of the present application, in response to the act performing a blocked access blocking check, starting a first timer, transmitting a third wireless signal, the third wireless signal including a fifth message, the fifth message being used to indicate that access is blocked, the fifth message being used to indicate an expiration time of the first timer; the running status of the first timer is used for access blocking checking.
Specifically, according to an aspect of the present application, whether the fourth message is used to stop the second timer is related to the trigger reason for starting the RRC access request;
wherein the second timer is associated with one access category; when the fourth message is received, the second timer is in a running state; the running status of the second timer is used for access blocking checking.
In particular, according to an aspect of the present application, a fourth wireless signal is transmitted, the fourth wireless signal comprising a sixth message, the sixth message being used to indicate a set of access classes that are not access-blocked; the access category of the RRC connection request of the second node indicated by the first parameter belongs to the set of access reasons indicated by the sixth message which are not blocked by access;
wherein there is at least one timer associated with an access category maintained by the first node that is running; the running state of a timer maintained by the first node associated with one access class is used for access blocking checking.
Specifically, according to an 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 at least includes one access category.
Specifically, according to an aspect of the present application, when the action-initiated RRC access request is for information bits generated at the first node and information bits generated at the second node are also forwarded, the trigger reason for the action-initiated RRC access request is considered to be for forwarding information bits generated at the second node.
Specifically, according to an aspect of the present application, the first node is a user equipment.
Specifically, according to an aspect of the present application, the first node is an internet of things terminal.
In particular, according to an aspect of the present application, the first node is a relay.
Specifically, according to an aspect of the present application, the first node is a vehicle-mounted terminal.
In particular, according to one aspect of the application, the first node is an aircraft.
The application discloses a first node used for wireless communication, comprising:
a first transmitter for starting the RRC access request and executing the access blocking check according to the second parameter; determining the second parameter according to the trigger reason for starting the RRC access request; the second parameter is used to indicate an access category of the RRC access request of the first node;
wherein the sentence determining the second parameter according to the trigger reason for starting the RRC access request includes:
the second parameter is indicated by a higher layer when a trigger reason for the behavior-initiated RRC access request is an information bit generated at the first node;
when the trigger reason for the behavior-initiated RRC access request is to forward information bits generated at the second node, whether the first parameter belongs to a first set of parameters is used to determine the second parameter; the first parameter is used to indicate an access category of the second node.
As an example, compared with the conventional scheme, the method has the following advantages: unified access control is executed and guaranteed, and access blocking check caused by access triggered by remote UE access of a relay node is avoided. The method is favorable for relieving network congestion and ensuring the fairness of access in a congestion state.
As an example, compared with the conventional scheme, the present application has the following advantages: the relay node informs the network of the access blocking condition, so that the network can schedule the access blocking condition, for example, when the access blocking condition is still met, only the data of the remote UE can be scheduled without scheduling the data of the relay UE, and the fairness is ensured.
As an example, compared with the conventional scheme, the method has the following advantages: the relay node informs the remote node of the access blocking condition, including the running condition expiration time of the timer associated with the access category and the like, so that the relay selection of the remote node is facilitated, whether the service transmission and the access are carried out or not is judged in advance, unnecessary signaling flow is reduced, and the time delay is reduced.
As an example, compared with the conventional scheme, the method has the following advantages: the emergency service of the remote UE is not blocked by the relay node; the high priority service of the remote node can also be properly processed by the relay node, and the parameters related to the access blocking check applicable to the high priority are adopted to execute the access blocking check.
As an example, compared with the conventional scheme, the method has the following advantages: when the far-end UE initiates a low-priority service, the relay node may continue to perform access check using the access check parameters configured in its higher layer, which is beneficial to avoid network congestion, because once accessed, the relay node may also send some information, such as signaling of the access layer, which may also occupy resources and aggravate network congestion.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the detailed description of the non-limiting embodiments with reference to the following drawings in which:
fig. 1 shows a flow diagram of initiating an RRC access request, performing an access barring check according to a second parameter according to an embodiment of the application;
FIG. 2 shows a schematic diagram of a network architecture according to an embodiment of the present application;
figure 3 shows a schematic diagram of an embodiment of a radio protocol architecture for the user plane and the control plane according to an embodiment of the present application;
FIG. 4 illustrates a first node according to an embodiment of the present application;
FIG. 5 shows a flow diagram of a transmission according to an embodiment of the application;
FIG. 6 shows a flow diagram of a transmission according to an embodiment of the present application;
fig. 7 shows a schematic diagram in which the running state of the first timer is used for access blocking checking according to an embodiment of the present application;
fig. 8 shows a schematic diagram in which the running state of the second timer is used for access blocking checking according to an embodiment of the present application;
FIG. 9 shows a schematic diagram of whether a first parameter belongs to a first set of parameters is used to determine a second parameter according to an embodiment of the application;
fig. 10 illustrates a schematic diagram of a processing device for use in a first node according to an embodiment of the application.
Detailed Description
The technical solutions of the present application will be further described in detail with reference to the accompanying drawings, and it should be noted that the embodiments and features of the embodiments in the present application can be arbitrarily combined with each other without conflict.
Example 1
Embodiment 1 illustrates a flowchart of initiating an RRC access request and performing an access barring check according to a second parameter according to an embodiment of the present application, as shown in fig. 1. In fig. 1, each block represents a step, and it is particularly emphasized that the sequence of the blocks in the figure does not represent a chronological relationship between the represented steps.
In embodiment 1, a first node in the present application starts an RRC access request in step 101; performing an access barring check according to the second parameter in step 102;
the first node determines the second parameter according to the trigger reason for starting the RRC access request; the second parameter is used to indicate an access category of the RRC access request of the first node; the sentence determines the second parameter according to the trigger reason for starting the RRC access request, and the method comprises the following steps:
the second parameter is indicated by a higher layer when a trigger reason for the behavior-initiated RRC access request is an information bit generated at the first node;
when the trigger reason for the behavior-initiated RRC access request is to forward information bits generated at the second node, whether the first parameter belongs to a first set of parameters is used to determine the second parameter; the first parameter is used to indicate an access category of the second node.
As an embodiment, the first node is a UE (User Equipment).
As an embodiment, the second node is a UE.
As an embodiment, the second node is a remote UE.
As an embodiment, the second node is an arbitrary remote UE.
As an embodiment, the second node is any UE requesting a relay.
As an embodiment, the second node is a UE other than any of the first nodes.
As an embodiment, the interface through which the first node communicates with the second node is a PC5 interface.
As an embodiment, the first node is a relay node of the second node.
As one embodiment, the first node is an L2 relay node of the second node.
As one embodiment, the first node is a layer 2 relay node of the second node.
As an embodiment, the first node is a layer 2 relay node of the second node.
As one embodiment, the first node is an L2 relay node of the second node.
As one embodiment, the first node is a type I relay node of the second node.
As an embodiment, the first node is a type II relay node of the second node.
As one embodiment, the first node and the second node communicate using a sidelink.
In one embodiment, the first node sends a first discovery message, which is used to instruct the first node to provide a relay service.
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.
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.
As a sub-embodiment of the above embodiment, the first discovery message is used for discovery or discovery.
As an embodiment, the action initiating an RRC access request comprises initiating an RRC connection establishment.
As one embodiment, the behavior initiating the RRC access request includes initiating RRC connection continuation.
As one embodiment, the behavior initiating the RRC access request includes initiating an RRC connection reestablishment.
As an embodiment, the behavior-initiated RRC access request does not include initiating RRC connection reestablishment.
For one embodiment, the first parameter includes an Access Category (Access Category).
For one embodiment, the second parameter includes an Access Category (Access Category).
For one embodiment, the first parameter includes an Access Identity (Access Identity).
As an embodiment, the second parameter includes an Access Identity (Access Identity).
As one embodiment, the phrase access barring check is an access barring check.
As an embodiment, when performing an access blocking check, a node performing the access blocking check generates a random number, if the generated random number is smaller than the first threshold, then access is allowed, if the generated random number is not smaller than the first threshold, then access is blocked; the first threshold is configured or preconfigured by the network.
As an embodiment, the result of the access barring check only comprises that access is barred and that access is allowed, which means that access is not barred.
As an embodiment, the second parameter is a corresponding access category of the RRC access request of the first node.
As one embodiment, the second parameter is the associated access category of the RRC access request of the first node.
As an embodiment, the second parameter is an access category of the RRC access request of the first node.
As an embodiment, the first parameter is a corresponding access category of the RRC access request of the second node.
As an embodiment, the first parameter is the associated access category of the RRC access request of the second node.
As an embodiment, the first parameter is an access category of the RRC access request of the second node.
As an embodiment, the cause of the RRC access request of the second node is used to determine the first parameter.
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.
As a sub-embodiment of the above embodiment, the reason for the RRC access request of the second node includes to respond to paging.
As a sub-embodiment of the above embodiment, the reason for the RRC access request of the second node includes for handover.
As a sub-embodiment of the above embodiment, the reason for the RRC access request of the second node includes for emergency services.
As a sub-embodiment of the above embodiment, the reason for the RRC access request of the second node includes services defined for an operator.
As a sub-embodiment of the foregoing embodiment, the reason for the RRC access request of the second node includes data outside a Mobile Originated (MO) column.
As a sub-embodiment of the above embodiment, the reason for the RRC access request of the second node includes a traffic that is not sensitive to a delay.
As a sub-embodiment of the above embodiment, the reason for the RRC access request of the second node includes for non-access stratum signaling.
As a sub-embodiment of the above embodiment, the reason for the RRC access request of the second node comprises for a location request.
As a sub-embodiment of the above embodiment, the cause of the RRC access request of the second node comprises data for a PDU session using suspended user plane resources.
As an embodiment, the value range of the first parameter is an integer between 0 and 63, and includes 0 and 63.
As an embodiment, the value range of the second parameter is an integer between 0 and 63, and includes 0 and 63.
As an embodiment, the value range of the first parameter is an integer between 0 and 15, and includes 0 and 15.
As an embodiment, the value range of the second parameter is an integer between 0 and 15, and includes 0 and 15.
As an embodiment, the reason why the sentence triggers the RRC access request when the behavior is initiated is that the information bits generated at the first node include the following meaning: the generator of the information bits is the first node.
As an embodiment, the reason why the sentence triggers the RRC access request when the behavior is initiated is that the information bits generated at the first node include the following meaning: the information bits are generated by an RRC entity or RRC layer of the first node.
As an embodiment, the reason why the sentence triggers the RRC access request when the behavior is initiated is that the information bits generated at the first node include the following meaning: the information bits are generated by a PDCP entity or PDCP layer of the first node.
As an embodiment, the reason why the sentence triggers the RRC access request when the behavior is initiated is that the information bits generated at the first node include the following meaning: the information bits are generated by a non-access stratum of the first node.
As an embodiment, the reason why the sentence triggers the RRC access request when the behavior starts is that the information bits generated at the first node include the following meaning: the information bits are generated by an SDAP layer of the first node.
As an embodiment, the reason why the sentence triggers the RRC access request when the behavior is initiated is that the information bits generated at the first node include the following meaning: the information bits belong to one QoS flow of the first node.
As an embodiment, the reason why the sentence triggers the RRC access request when the behavior starts is that the information bits generated at the first node include the following meaning: the information bits do not belong to bits of other UEs using L2 relay.
As an embodiment, the reason why the sentence triggers the RRC access request when the behavior is initiated is that the information bits generated at the first node include the following meaning: the requested RRC connection is for transmitting information bits generated by the first node and not for transmitting information bits from other UEs.
As an embodiment, the reason why the sentence triggers the RRC access request when the behavior is initiated is that the information bits generated at the first node include the following meaning: the requested RRC connection is for transmitting traffic of the first node and not for transmitting traffic from other UEs.
As an embodiment, the reason why the sentence triggers the RRC access request when the behavior starts is that the information bits generated at the first node include the following meaning: the RRC connection requested is not for relaying.
As an embodiment, the reason why the sentence triggers the RRC access request when the behavior starts is that the information bits generated at the first node include the following meaning: the RRC connection requested is not for layer 2 relaying.
As an embodiment, the reason why the action triggers the RRC access request is to forward information bits generated at the second node includes the following meaning: the generator of the information bits is the second node.
As an embodiment, the reason why the sentence triggers the RRC access request when the behavior is initiated is to forward information bits generated at the second node includes the following meaning: the information bits are generated by an RRC entity or an RRC layer of the second node.
As an embodiment, the reason why the action triggers the RRC access request is to forward information bits generated at the second node includes the following meaning: the information bits are generated by a PDCP entity or PDCP layer of the second node.
As an embodiment, the reason why the sentence triggers the RRC access request when the behavior is initiated is to forward information bits generated at the second node includes the following meaning: the information bits are generated by a non-access stratum of the second node.
As an embodiment, the reason why the action triggers the RRC access request is to forward information bits generated at the second node includes the following meaning: the information bits are generated by an SDAP layer of the second node.
As an embodiment, the reason why the sentence triggers the RRC access request when the behavior is initiated is to forward information bits generated at the second node includes the following meaning: the information bits belong to one QoS flow of the second node.
As an embodiment, the reason why the sentence triggers the RRC access request when the behavior is initiated is to forward information bits generated at the second node includes the following meaning: the information bits belong to bits of other remote UEs using L2 relay.
As an embodiment, the reason why the sentence triggers the RRC access request when the behavior is initiated is to forward information bits generated at the second node includes the following meaning: the RRC connection requested is for transmitting information bits generated by the second node.
As an embodiment, the reason why the action triggers the RRC access request is to forward information bits generated at the second node includes the following meaning: the RRC connection requested is for transmitting traffic of the second node.
As an embodiment, the reason why the sentence triggers the RRC access request when the behavior is initiated is to forward information bits generated at the second node includes the following meaning: the RRC connection requested is for relaying.
As an embodiment, the reason why the action triggers the RRC access request is to forward information bits generated at the second node includes the following meaning: the RRC connection requested is for layer 2 relay.
As an embodiment, the reason why the sentence triggers the RRC access request when the behavior is initiated is to forward information bits generated at the second node includes the following meaning: the RRC connection requested is for L2 or Layer-2 or Layer 2 relay.
As an embodiment, when the behavior-initiated RRC access request is for information bits generated at the first node and information bits generated at the second node are forwarded, the trigger reason for the behavior-initiated RRC access request is considered to be for forwarding information bits generated at the second node.
As an embodiment, when the behavior-initiated RRC access request is for information bits generated at the first node and information bits generated at a second node are forwarded, whether the first parameter belongs to a first set of parameters is used to determine the second parameter; the first parameter is used to indicate an access category of the second node.
As an embodiment, when the behavior-initiated RRC access request is for transmission of information bits including the second node, the trigger reason for the behavior-initiated RRC access request is considered to be for forwarding information bits generated at the second node.
As an embodiment, when the behavior-initiated RRC access request is for transmission of an information bit including a second node, whether the first parameter belongs to a first set of parameters is used to determine the second parameter; the first parameter is used to indicate an access category of the second node.
As an embodiment, the first parameter is different from the second parameter.
As an embodiment, the second parameter does not belong to the first set of parameters.
As an embodiment, the first set of parameters comprises at least one access category.
For one embodiment, the first set of parameters includes emergency traffic.
For one embodiment, the first set of parameters includes high priority traffic.
As one embodiment, the first set of parameters includes emergency.
As an embodiment, the first set of parameters comprises { emergency, highpreference access }.
As an embodiment, the first set of parameters includes { emergency, highprioritylaccess, mps-prioritylaccess, mcs-prioritylaccess }.
As an embodiment, the first set of parameters comprises { access identity 1, access identity 2}.
As an embodiment, the first set of parameters comprises at least one of { access identity 11, access identity 12, access identity 13, access identity 14, access identity 15 }.
For one embodiment, the first set of parameters includes { access class 2}.
For one embodiment, the first set of parameters includes { access class 0}.
For one embodiment, the first set of parameters includes { access class 0, access class 2}.
For one embodiment, the first node is in an RRC idle state when initiating an RRC access request.
For one embodiment, the first node is in an RRC inactive state when initiating an RRC access request.
As an embodiment, the sentence said second parameter is comprised by a higher layer indication, said second parameter being indicated by a non-access stratum indication.
As an embodiment, the sentence said second parameter is indicated by a higher layer comprises said second parameter is indicated by an RRC layer.
As an embodiment, the sentence said second parameter is comprised by a higher layer indication, said second parameter being indicated by a PC5-S layer.
As an embodiment, the sentence includes the second parameter indicated by a higher layer, and the second parameter is indicated by a core network.
As an embodiment, the serving cell of the first node indicates a second set of parameters, which is used for access blocking checking.
As an embodiment, the second set of parameters comprises blocking parameters.
For one embodiment, the second set of parameters includes a unified access blocking (UAC) parameter.
As an embodiment, the second set of parameters comprises uac-BarringInfo.
As an embodiment, the second set of parameters comprises uac-BarringForCommon.
As an embodiment, the second set of parameters comprises uac-BarringPerPLMN-List.
As an embodiment, the second set of parameters comprises uac-BarringInfoSetList.
For one embodiment, the second set of parameters includes uac-Access category 1-SelectionAccessInfo.
As one embodiment, the phrase access blocking check is an access barring check.
Example 2
Embodiment 2 illustrates a schematic diagram of a network architecture according to an embodiment of the present application, as shown in fig. 2. Fig. 2 illustrates a V2X communication architecture under a 5G NR (new radio, new air interface), LTE (Long-Term Evolution ), and LTE-a (Long-Term Evolution Advanced) system architecture. The 5G NR or LTE network architecture may be referred to as 5GS (5 GSystem)/EPS (Evolved Packet System) or some other suitable terminology.
The V2X communication architecture of embodiment 2 includes UE (User Equipment) 201, UE241, ng-RAN (next generation radio access network) 202,5gc (5G Core network )/EPC (Evolved Packet Core) 210, hss (Home Subscriber Server )/UDM (Unified Data Management, unified Data Management) 220, proSe function 250, and ProSe application Server 230. The V2X communication architecture may interconnect with other access networks, but these entities/interfaces are not shown for simplicity. As shown, the V2X communication architecture provides packet switched services, however those skilled in the art will readily appreciate that the various concepts presented throughout this application may be extended to networks providing circuit switched services or other cellular networks. The NG-RAN includes NR node bs (gnbs) 203 and other gnbs 204. The gNB203 provides user and control plane protocol termination towards the UE201. The gnbs 203 may be connected to other gnbs 204 via an Xn interface (e.g., backhaul). The gNB203 may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a Basic Service Set (BSS), an Extended Service Set (ESS), a TRP (transmit receive node), or some other suitable terminology. The gNB203 provides the UE201 with an access point to the 5GC/EPC210. Examples of the UE201 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, 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., MP3 player), a camera, a game console, a drone, an aircraft, a narrowband internet of things device, a machine type communication device, a terrestrial vehicle, an automobile, a wearable device, or any other similar functioning device. Those skilled in the art may also refer to UE201 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. The gNB203 is connected to the 5GC/EPC210 via an S1/NG interface. The 5GC/EPC210 includes MME (Mobility Management Entity)/AMF (Authentication Management domain)/SMF (Session Management Function) 211, other MME/AMF/SMF214, S-GW (serving Gateway)/UPF (user plane Function) 212, and P-GW (Packet data Network Gateway)/UPF 213. The MME/AMF/SMF211 is a control node that handles signaling between the UE201 and the 5GC/EPC210. In general, the MME/AMF/SMF211 provides bearer and connection management. All user IP (Internet protocol) packets are transported through the S-GW/UPF212, which S-GW/UPF212 itself is connected to the P-GW/UPF213. The P-GW provides UE IP address allocation as well as other functions. The P-GW/UPF213 is connected to the internet service 230. The internet service 230 includes an operator-corresponding internet protocol service, and may specifically include the internet, an intranet, an IMS (IP Multimedia Subsystem), and a packet-switched streaming service. The ProSe function 250 is a logical function for network-related behavior required for location-based services (ProSe); including a DPF (Direct Provisioning Function), a Direct Discovery Name Management Function (Direct Discovery Name Management Function), an EPC-level Discovery ProSe Function (EPC-level Discovery ProSe Function), and the like. The ProSe application server 230 has functions of storing EPC ProSe subscriber identities, mapping between application layer subscriber identities and EPC ProSe subscriber identities, allocating a pool of code suffixes restricted by ProSe, and the like.
As an embodiment, the UE201 and the UE241 are connected through a PC5 Reference Point (Reference Point).
As an embodiment, the ProSe function 250 is connected with the UE201 and the UE241 through PC3 reference points, respectively.
As an embodiment, the ProSe function 250 is connected with the ProSe application server 230 through a PC2 reference point.
As an embodiment, the ProSe application server 230 is connected with the ProSe application of the UE201 and the ProSe application of the UE241 through a PC1 reference point, respectively.
As an embodiment, the first node in the present application is a UE201.
As an embodiment, the second node in this application is a UE241.
As an embodiment, the wireless link between the UE201 and the UE241 corresponds to a Sidelink (SL) in the present application.
As an embodiment, the radio link from the UE201 to the NR node B is an uplink.
As an embodiment, the radio link from the NR node B to the UE201 is the downlink.
As an embodiment, the UE201 supports relay transmission.
As an embodiment, the UE241 supports relay transmission.
As an embodiment, the UE201 is a vehicle including an automobile.
As an embodiment, the UE241 is a vehicle including an automobile.
As an example, the gNB203 is a macro cellular (MarcoCellular) base station.
As an embodiment, the gNB203 is a Micro Cell (Micro Cell) base station.
As an embodiment, the gNB203 is a pico cell (PicoCell) base station.
As an example, the gNB203 is a flight platform device.
As an embodiment, the gNB203 is a satellite device.
Example 3
Embodiment 3 shows a schematic diagram of an embodiment of a radio protocol architecture for the user plane and the control plane according to the present application, as shown in fig. 3. Fig. 3 is a schematic diagram illustrating an embodiment of radio protocol architecture for the user plane 350 and the control plane 300, fig. 3 showing the radio protocol architecture for the control plane 300 for a first node (UE, satellite or aircraft in gNB or NTN) and a second node (satellite or aircraft in gNB, UE or NTN), or between two UEs, in three layers: layer 1, layer 2 and layer 3. Layer 1 (L1 layer) is the lowest layer and implements various PHY (physical layer) signal processing functions. The L1 layer will be referred to herein as PHY301. Layer 2 (L2 layer) 305 is above PHY301 and is responsible for the link between the first and second nodes 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 ciphering data packets and provides handoff support between second nodes to the first node. The RLC sublayer 303 provides segmentation and reassembly of upper layer packets, retransmission of lost packets, and reordering of packets to compensate for out-of-order reception due to HARQ. The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating the various radio resources (e.g., resource blocks) in one cell between the first nodes. The MAC sublayer 302 is also responsible for HARQ operations. A RRC (Radio Resource Control) sublayer 306 in layer 3 (L3 layer) in the Control plane 300 is responsible for obtaining Radio resources (i.e., radio bearers) and configuring the lower layers using RRC signaling between the second node and the first node. The PC5-S (PC 5Signaling Protocol) sublayer 307 is responsible for processing of the Signaling Protocol of the PC5 interface. The radio protocol architecture of the user plane 350 includes layer 1 (L1 layer) and layer 2 (L2 layer), the radio protocol architecture in the user plane 350 for the first and second nodes is substantially the same for the physical layer 351, the PDCP sublayer 354 in the L2 layer 355, the RLC sublayer 353 in the L2 layer 355, and the MAC sublayer 352 in the L2 layer 355 as the corresponding layers and sublayers in the control plane 300, but the PDCP sublayer 354 also provides header compression for upper layer packets to reduce radio transmission overhead. The L2 layer 355 in the user plane 350 further includes an SDAP (Service Data Adaptation Protocol) sublayer 356, and the SDAP sublayer 356 is responsible for mapping between QoS streams and Data Radio Bearers (DRBs) to support diversity of services. Although not shown, the first node may have several upper layers above the L2 layer 355. Also included are a network layer (e.g., IP layer) that terminates at the P-GW on the network side and an application layer that terminates at the other end of the connection (e.g., far end UE, server, etc.). For UEs involving relay services, the control plane may also include an adaptation sublayer AP308, the user plane may also include an adaptation sublayer AP358, and the introduction of an adaptation layer may facilitate lower layers, such as the MAC layer, e.g., the RLC layer, to multiplex and/or differentiate data from multiple source UEs. In addition, the adaptation sublayers AP308 and AP358 may also be sublayers within the PDCP304 and PDCP354, respectively. RRC306 may be used to handle RRC signaling for the Uu interface and signaling for the PC5 interface.
The radio protocol architecture of fig. 3 applies to the first node in this application as an example.
The radio protocol architecture of fig. 3 applies to the second node in this application as an example.
As an embodiment, the first message in this application is generated in RRC306 or PC5-S307.
As an embodiment, the fifth message in the present application is generated in RRC306 or PC5-S307.
As an embodiment, the sixth message in the present application is generated in RRC306 or PC5-S307.
As an embodiment, the second message in the present application is generated in RRC306 or PC5-S307.
As an embodiment, the third message in this application is generated in RRC306.
As an embodiment, the fourth message in this application is generated in RRC306.
As an example, the first wireless signal in the present application is generated in PHY301 or PHY351.
As an example, the second wireless signal in the present application is generated in PHY301 or PHY351.
The third wireless signal in the present application is generated from PHY301 or PHY351, as one embodiment.
The fourth line signal in this application is generated from PHY301 or PHY351 for one embodiment.
As an embodiment, the first parameter set in the present application is generated in a non-access stratum.
As an embodiment, the second parameter set in this application is generated in a non-access stratum layer.
Example 4
Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to the present application, as shown in fig. 4. Fig. 4 is a block diagram of a first communication device 450 and a second communication device 410 communicating with each other in an access network.
The first communications device 450 includes a controller/processor 459, a memory 460, a data source 467, a transmit processor 468, a receive processor 456, a multi-antenna transmit processor 457, a multi-antenna receive processor 458, a transmitter/receiver 454, and an antenna 452.
The second communication device 410 includes a controller/processor 475, a memory 476, a receive processor 470, a transmit processor 416, a multiple antenna receive processor 472, a multiple antenna transmit processor 471, a transmitter/receiver 418, and an antenna 420.
In the transmission from the second communication device 410 to the first communication device 450, at the second communication device 410, upper layer data packets from the core network are provided to the controller/processor 475. The controller/processor 475 implements the functionality of the L2 layer. In transmissions from the second communications device 410 to the first communications device 450, the controller/processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation to the first communications device 450 based on various priority metrics. The controller/processor 475 is also responsible for retransmission of lost packets, and signaling to the first communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (i.e., the physical layer). The transmit processor 416 implements coding and interleaving to facilitate Forward Error Correction (FEC) at the second communication device 410, as well as mapping of signal constellation based on various modulation schemes (e.g., binary Phase Shift Keying (BPSK), quadrature Phase Shift Keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding, including codebook-based precoding and non-codebook based precoding, and beamforming on the coded and modulated symbols to generate one or more spatial streams. Transmit processor 416 then maps each spatial stream to subcarriers, multiplexes with reference signals (e.g., pilots) in the time and/or frequency domain, and then uses an Inverse Fast Fourier Transform (IFFT) to generate the physical channels carrying the time-domain multicarrier symbol streams. The multi-antenna transmit processor 471 then performs transmit analog precoding/beamforming operations on the time domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multicarrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream that is then provided to a different antenna 420.
In a transmission from the second communications apparatus 410 to the first communications apparatus 450, each receiver 454 receives a signal through its respective antenna 452 at the first communications apparatus 450. Each receiver 454 recovers information modulated onto a radio frequency carrier and converts the radio frequency stream into a baseband multi-carrier symbol stream that is provided to a receive processor 456. Receive processor 456 and multi-antenna receive processor 458 implement the various signal processing functions of the L1 layer. A multi-antenna receive processor 458 performs receive analog precoding/beamforming operations on the baseband multi-carrier symbol stream from the receiver 454. Receive processor 456 converts the baseband multicarrier symbol stream after the receive analog precoding/beamforming operation from the time domain to the frequency domain using a Fast Fourier Transform (FFT). In the frequency domain, the physical layer data signals and the reference signals to be used for channel estimation are demultiplexed by the receive processor 456, and the data signals are subjected to multi-antenna detection in the multi-antenna receive processor 458 to recover any spatial streams destined for the first communication device 450. The symbols on each spatial stream are demodulated and recovered at a receive processor 456 and soft decisions are generated. The receive processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communication device 410 on the physical channel. The upper layer data and control signals are then provided to a controller/processor 459. The controller/processor 459 implements the functions of the L2 layer. The controller/processor 459 may be associated with a memory 460 that stores program codes and data. Memory 460 may be referred to as a computer-readable medium. In transmissions from the second communications device 410 to the second communications device 450, the controller/processor 459 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer packets from the core network. The upper layer packet is then provided to all protocol layers above the L2 layer. Various control signals may also be provided to L3 for L3 processing.
In a transmission from the first communications device 450 to the second communications device 410, a data source 467 is used at the first communications device 450 to provide upper layer data packets to a controller/processor 459. Data source 467 represents all protocol layers above the L2 layer. Similar to the send function at the second communications apparatus 410 described in the transmission from the second communications apparatus 410 to the first communications apparatus 450, the controller/processor 459 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocation, implementing L2 layer functions for the user plane and control plane. The controller/processor 459 is also responsible for retransmission of lost packets and signaling to said second communications device 410. A transmit processor 468 performs modulation mapping, channel coding, and digital multi-antenna spatial precoding by a multi-antenna transmit processor 457 including codebook-based precoding and non-codebook based precoding, and beamforming, and the transmit processor 468 then modulates the resulting spatial streams into multi-carrier/single-carrier symbol streams, which are provided to different antennas 452 via a transmitter 454 after analog precoding/beamforming in the multi-antenna transmit processor 457. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a radio frequency symbol stream and provides the radio frequency symbol stream to the antenna 452.
In a transmission from the first communication device 450 to the second communication device 410, the functionality at the second communication device 410 is similar to the receiving functionality at the first communication device 450 described in the transmission from the second communication device 410 to the first communication device 450. Each receiver 418 receives rf signals through its respective antenna 420, converts the received rf signals to baseband signals, and provides the baseband signals to a multi-antenna receive processor 472 and a receive processor 470. The receive processor 470 and the multiple antenna receive processor 472 collectively implement the functions of the L1 layer. The controller/processor 475 implements the L2 layer functions. The controller/processor 475 may be associated with a memory 476 that stores program codes and data. Memory 476 may be referred to as a computer-readable medium. In transmission from the first communications device 450 to the second communications device 410, the controller/processor 475 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer packets from the UE 450. Upper layer data packets from the controller/processor 475 may be provided to a core network.
As an embodiment, the first communication device 450 apparatus includes: at least one processor and at least one memory including computer program code; the at least one memory and the computer program code configured to, for use with the at least one processor, the first communication device 450 apparatus at least:
as an embodiment, the first communication device 450 includes: a memory storing a program of computer readable instructions that when executed by at least one processor result in actions comprising:
as an embodiment, the first communication device 450 corresponds to a first node in the present application.
As an embodiment, the second communication device 450 corresponds to a second node in the present application.
For one embodiment, the first communication device 450 is a UE.
As an embodiment, the first communication device 450 is a vehicle-mounted terminal.
For one embodiment, the first communication device 450 is a relay.
For one embodiment, the second communication device 410 is a UE.
For one embodiment, receiver 456 (including antenna 460), receive processor 452, and controller/processor 490 are used to receive the first wireless signal.
For one embodiment, receiver 456 (including antenna 460), receive processor 452, and controller/processor 490 are used to receive the second wireless signal.
For one embodiment, receiver 456 (including antenna 460), receive processor 452, and controller/processor 490 are used to receive the fourth message.
For one embodiment, a transmitter 456 (including an antenna 460), a transmit processor 455, and a controller/processor 490 are used to transmit the third wireless signal in this application.
For one embodiment, a transmitter 456 (including an antenna 460), a transmit processor 455, and a controller/processor 490 are used to transmit the fourth line signal.
For one embodiment, a transmitter 456 (including an antenna 460), a transmit processor 455, and a controller/processor 490 are used to transmit the third message.
Example 5
Embodiment 5 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in fig. 5. In fig. 5, U01 corresponds to a first node of the present application, and U02 corresponds to a second node of the present application, and it is specifically illustrated that the sequence in the present example does not limit the sequence of signal transmission and the sequence of implementation in the present application, wherein the steps in F51 and F52 are optional.
For theFirst node U01Receiving a first wireless signal in step S5101; receiving a second wireless signal in step S5102; in step S5103, an RRC access request is initiated; performing an access barring check according to the second parameter in step S5104; sending a third message in step S5105; the fourth message is received in step S5106.
For theSecond node U02Transmitting a first wireless signal in step S5201; the second wireless signal is transmitted in step S5202.
ForThird node U03Receiving a third message in step S5301; the fourth message is transmitted in step S5302.
In embodiment 5, the first node U01 determines the second parameter according to the trigger reason for starting the RRC access request; the second parameter is used to indicate an access category of the RRC access request of the first node;
wherein the sentence determines the second parameter according to the trigger reason for starting the RRC access request, and the method comprises the following steps:
when the trigger reason for the behavior-initiated RRC access request is for an information bit generated at the first node U01, the second parameter is indicated by a higher layer;
when the trigger reason for the behavior-initiated RRC access request is to forward information bits generated at the second node U02, whether the first parameter belongs to the first set of parameters is used to determine the second parameter; the first parameter is used to indicate an access category of the second node.
As an embodiment, the second node U02 is a UE.
As an embodiment, the third node U02 is a base station.
As an embodiment, the third node U02 is a camping cell of the first node U01.
As an embodiment, the third node U02 is a cell selected by the first node U01.
As an embodiment, the first node U01 is a relay, the second node U02 is a remote UE, and the third node U03 is a base station or a cell or a group of cells.
As an embodiment, the first node U01 is a relay of the second node U02 connection network.
As a sub-embodiment of the above embodiment, the first node U01 is a layer 2 relay.
As an embodiment, the second node U02 is an arbitrary remote UE accessing the network through the first node U01.
As an embodiment, the first wireless signal is transmitted at the PC5 interface.
As one embodiment, the first wireless signal is transmitted over a sidelink.
As an embodiment, the Physical Channel occupied by the first wireless signal includes a psch (Physical Sidelink Shared Channel).
For one embodiment, the first wireless signal includes a first MAC PDU including a first MAC sub-PDU, a header of the first MAC sub-PDU is a first MAC sub-header, the first MAC sub-header includes 16 most significant bits of a first identity and 8 most significant bits of a second identity; the second identity is used for identifying the first node U01.
As a sub-embodiment of the above embodiment, the first identity and the second identity are each a link layer identity.
As a sub-embodiment of the above embodiment, the first identity and the second identity are Layer-2 identities, respectively.
As a sub-embodiment of the above embodiment, the second identity is used to identify the first node U01.
As a sub-embodiment of the above embodiment, the first identity is used to identify the second node U02.
As a sub-embodiment of the above embodiment, the first MAC sub-PDU comprises the first message.
In one embodiment, the first message comprises an RRC message.
As an embodiment, the first message is an RRC message.
For one embodiment, the first message comprises a PC5-RRC message.
For one embodiment, the first message comprises a PC5-S message.
For one embodiment, the first message comprises a Direct link examination request.
For one embodiment, the first message includes a Direct link modification request.
As an embodiment, the first message comprises RRCReconfigurationSidelink.
For one embodiment, the first message comprises an RRCSetupRequest.
For one embodiment, the first message comprises an RRCResumeRequest.
For one embodiment, the first message comprises RRCResumeRequest1.
As an embodiment, the first message comprises an RRCConnectionSetupRequest.
As an embodiment, the first message comprises rrcconnectionsetupume.
For an embodiment, the logical channel occupied by the first message includes a CCCH.
For an embodiment, the logical channel occupied by the first message includes CCCH1.
As an embodiment, the logical channel occupied by the first message includes a DCCH.
As an embodiment, the first message requests establishment of an RRC connection.
As an embodiment, the first message requests that the RRC connection be continued.
As one embodiment, the first message is used to indicate the first parameter.
As a sub-embodiment of the above embodiment, the first message includes the parameter.
As a sub-embodiment of the above embodiment, the first message includes establistemcause, and the establistemcause has a mapping relationship with the first parameter, and the first message indicates the first parameter by indicating the establistemcause.
As a sub-embodiment of the above embodiment, the first message includes resumecuse, and the resumecuse has a mapping relation with the first parameter, and the first message indicates the first parameter by indicating resumecuse.
As a sub-embodiment of the above embodiment, the first message indicates a reason for RRC access of the second node, and the reason for RRC access of the second node indicated by the first message has a mapping relationship with the first parameter.
As a sub-embodiment of the above embodiment, the reason that the first message indicates RRC access of the second node includes mobile originated data.
As a sub-embodiment of the above embodiment, the reason that the first message is to indicate RRC access of the second node includes a paging response.
As a sub-embodiment of the above embodiment, the first message is a message indicating that the reason for RRC access by the second node includes high priority traffic.
As a sub-embodiment of the above embodiment, the first message is an RRC message indicating that the reason for RRC access by the second node includes emergency services.
As an embodiment, the second wireless signal is transmitted at the PC5 interface.
As one embodiment, the second wireless signal is transmitted over a sidelink.
As an embodiment, the Physical Channel occupied by the second radio signal includes a psch (Physical Sidelink Shared Channel).
As an embodiment, the Physical Channel occupied by the second wireless signal includes PSCCH (Physical Sidelink Control Channel).
For one embodiment, the second wireless signal comprises a second MAC PDU comprising a second MAC sub-PDU, the header of the second MAC sub-PDU being a second MAC sub-header comprising 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.
As a sub-embodiment of the above embodiment, the first identity and the second identity are each a link layer identity.
As a sub-embodiment of the above embodiment, the first identity and the second identity are Layer-2 identities, respectively.
As a sub-embodiment of the above embodiment, the second identity is used to identify the first node U01.
As a sub-embodiment of the above embodiment, the first identity is used to identify the second node U02.
As a sub-embodiment of the above embodiment, the second MAC sub-PDU comprises the first message.
As an embodiment, the second wireless signal comprises a second MAC PDU comprising a second MAC sub-PDU, the header of the second MAC sub-PDU being a second MAC sub-header, the second MAC sub-header comprising 16 most significant bits of a third identity and 8 most significant bits of a fourth identity;
as a sub-embodiment of the above embodiment, the third identity and the fourth identity are each a link layer identity.
As a sub-embodiment of the above embodiment, the third identity and the fourth identity are Layer-2 identities, respectively.
As a sub-embodiment of the above embodiment, the fourth identity is used to identify a destination link layer identity.
As a sub-embodiment of the above embodiment, the third identity is used to identify the second node U02.
As a sub-embodiment of the above embodiment, the second MAC sub-PDU comprises the first message.
As a sub-embodiment of the above embodiment, the fourth identity is used to identify a link layer identity for broadcasting.
As a sub-embodiment of the above embodiment, said fourth identity is used to identify a link layer identity for multicast.
For one embodiment, the second message comprises an RRC message.
For one embodiment, the second message comprises a PC5-RRC message.
For one embodiment, the second message comprises a PC5-S message.
For one embodiment, the second message comprises a discovery message.
As an embodiment, the transmission mode of the second message includes broadcasting.
As an embodiment, the sending mode of the second message includes multicast.
As an embodiment, the sending mode of the second message includes unicast.
As an embodiment, the second message is used to request RRC access of the second node; the second message comprises a first reason indicating a reason for the RRC access requested by the second message, the first reason being associated with the first parameter; the first parameter is used to indicate an access category of the RRC access of the second node requested by the second message.
As a sub-embodiment of the above embodiment, the second message is sent via SRB 0.
As a sub-embodiment of the above embodiment, the second message does not use encryption.
As a sub-embodiment of the above embodiment, the second message comprises an RRCSetupRequest.
As a sub-embodiment of the above embodiment, the second message RRCResumeRequest.
As a sub-embodiment of the above embodiment, the second message RRCResumeRequest1.
As a sub-embodiment of the above embodiment, the first reason comprises establshmentcause.
As a sub-embodiment of the above embodiment, the first reason comprises resumecuse.
As a sub-embodiment of the above embodiment, the first reason has a mapping relation with the first parameter.
As a sub-embodiment of the above embodiment, the first parameter is used to deduce (derivative) the first cause.
As a sub-embodiment of the above embodiment, the first parameter and a fixed or pre-configured mapping rule are used together to deduce (drive) the first cause.
As a sub-embodiment of the above embodiment, there is consistency between the access category of the RRC access of the second node indicated by the first parameter and the first reason included in the second message.
As a sub-embodiment of the above embodiment, the first parameter is an access category of the RRC access request of the second node.
As a sub-embodiment of the above embodiment, the RRC access requested by the second message comprises RRC connection establishment.
As a sub-embodiment of the above embodiment, the RRC access requested by the second message comprises RRC connection continuation.
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, mps-PriorityAccess, mcs-PriorityAccess }.
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 }.
As a sub-embodiment of the above embodiment, the value of the first reason belongs to one of { recordifiguration failure, handover failure, otherFailure, replayelection, replayfailure }.
As an embodiment, the reception of the first wireless signal triggers the first node U01 to initiate the RRC access request.
As an embodiment, the reception of the first message triggers the first node U01 to initiate the RRC access request.
As one embodiment, the sentence performing the access blocking check according to the second parameter includes: the second parameter is an access category, the second parameter being an input parameter for the access barring check.
As one embodiment, the sentence performing the access blocking check according to the second parameter includes: when the second parameter is 0, the result of the access blocking check is to allow access.
As one embodiment, the sentence performing the access blocking check according to the second parameter includes: when the second parameter is 2, the result of the access blocking check is to allow access.
As one embodiment, the sentence performing the access blocking check according to the second parameter includes: when the second parameter is a positive integer except 0 or 2, the first node U01 generates a first random number, and when the first random number is smaller than a first blocking threshold, access is blocked; access is allowed when the first random number is greater than the first blocking threshold, wherein the first blocking threshold is for an access category indicated by the second parameter, the first blocking threshold being configured by system broadcast messages.
As an embodiment, the first node U01 needs to first perform a blocking check before sending the third message.
As an embodiment, the first node U01 needs to first perform a blocking check according to the second parameter before sending the third message.
As an embodiment, the first node U01 sends the third message as an unblocked response to the action performing an access blocking check, the third message being used to request RRC access for the first node U01; the third message comprises a second reason for indicating a reason for the RRC access requested by the third message; whether the second reason is associated with the second parameter is related to the trigger reason for initiating the RRC access request.
As a sub-embodiment of the above embodiment, the third message is an RRC message.
As a sub-embodiment of the above embodiment, the third message comprises a reason for the request.
As a sub-embodiment of the above embodiment, the third message comprises an RRCSetupRequest.
As a sub-embodiment of the above embodiment, the third message comprises a RRCResumeRequest.
As a sub-embodiment of the above embodiment, the third message comprises RRCResumeRequest1.
As a sub-embodiment of the above embodiment, the third message comprises an RRCConnectionSetupRequest.
As a sub-embodiment of the above embodiment, the third message comprises an RRCConnectionResumeRequest.
As a sub-embodiment of the above embodiment, the third message is sent over SRB 0.
As a sub-embodiment of the above embodiment, the physical channel occupied by the third message comprises PUSCH.
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 access is allowed.
As a sub-embodiment of the above embodiment, the meaning of the phrase as an unblocked response to the action performing an access blocking check is that the result of the action performing an access blocking check is a response to allow access.
As a sub-embodiment of the above embodiment, said sentence said third message is used to request RRC access of said first node U01 comprises: the third message is used to request RRC connection setup of the first node U01.
As a sub-embodiment of the above embodiment, said sentence said third message is used to request RRC access of said first node U01 comprises: the third message is used to request RRC connection continuation of the first node U01.
As a sub-embodiment of the above embodiment, the second reason comprises estabilishment cause.
As a sub-embodiment of the above embodiment, the second reason includes resumeCauseCause.
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 }.
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 }.
As a sub-embodiment of the above embodiment, the value of the second reason belongs to one of { recordifiguration failure, handover failure, otherFailure, replayelection, replayfailure }.
As a sub-embodiment of the above embodiment, when the trigger reason for the behavior starting the RRC access request is an information bit generated at the first node U01, the access category indicated by the second parameter determines the second reason, where a value range of the access category indicated by the second parameter is more than one, a value range of the second reason is more than one, and a mapping relationship exists between the second parameter and the second reason.
As a sub-embodiment of the above embodiment, when the trigger reason for the behavior starting the RRC access request is an information bit generated at the first node U01, the access category indicated by the second parameter determines the second reason, where a value range of the access category indicated by the second parameter is more than one, a value range of the second reason is more than one, and the second reason can be obtained through a predefined mapping table and the second parameter.
As a sub-embodiment of the above embodiment, when the trigger reason for the behavior starting RRC access request is to forward an information bit generated at the second node U02, the value of the second reason is a spare bit in release 16, regardless of the value of the second parameter.
As a sub-embodiment of the foregoing embodiment, when the trigger reason for the behavior starting RRC access request is to forward an information bit generated at the second node U02, the value of the second reason is relay no matter how the value of the second parameter is.
As a sub-embodiment of the foregoing embodiment, when the trigger reason for the behavior starting RRC access request is to forward an information bit generated at the second node U02, the value of the second reason includes relay regardless of the value of the second parameter.
As a sub-embodiment of the foregoing embodiment, when the trigger reason for the behavior starting RRC access request is to forward an information bit generated at the second node U02, the second parameter is determined by the first parameter, and the value of the second reason includes relay regardless of the value of the first parameter.
As a sub-embodiment of the foregoing embodiment, when the trigger reason for the behavior starting RRC access request is to forward an information bit generated at a second node U02, the second parameter is the same as the first parameter, and regardless of a value of the first parameter, a value of the second reason includes relay.
As an embodiment, the fourth message is used to grant the request of the third message.
As a sub-embodiment of the above embodiment, the fourth message is an RRC message.
As a sub-embodiment of the above embodiment, the fourth message is transmitted over a Uu interface.
As a sub-embodiment of the foregoing embodiment, the physical channel occupied by the fourth message includes a PDSCH (physical downlink shared channel).
As a sub-embodiment of the foregoing embodiment, the physical channel occupied by the fourth message includes a PDCCH (physical downlink control channel).
As a sub-embodiment of the above embodiment, the fourth message comprises an RRCSetup.
As a sub-embodiment of the above embodiment, the fourth message comprises RRCResume.
As a sub-embodiment of the above embodiment, the fourth message comprises RRCEstablishment.
As a sub-embodiment of the above embodiment, the fourth message comprises RRCConnectionSetup.
As a sub-embodiment of the above embodiment, the fourth message comprises rrcconnectionresponse.
As a sub-embodiment of the above embodiment, the fourth message comprises RRCConnectionEstablishment.
As an embodiment, the sentence wherein the meaning that the trigger reason for the behavior initiation RRC access request is to forward information bits generated at the second node includes that the trigger reason for the behavior initiation RRC access request is to relay information bits generated at the second node.
As an embodiment, whether the fourth message is used to stop the second timer is related to the trigger reason for starting the RRC access request; wherein the second timer is associated with one access category; when the fourth message is received, the second timer is in a running state; the running status of the second timer is used for access blocking checking.
As a sub-embodiment of the above embodiment, for an access attempt of an access category associated with said second timer, said second timer is started when the access attempt is blocked after performing an access blocking check.
As a sub-embodiment of the above embodiment, the second timer is stopped after performing cell selection or reselection.
As a sub-embodiment of the above embodiment, the second timer is stopped after entering the RRC connected state.
As a sub-embodiment of the above embodiment, the second timer is stopped when the rrcreeconfiguration message including the recorfigurationwithsync is received.
As a sub-embodiment of the above embodiment, the second timer is stopped after changing the PCell.
As a sub-embodiment of the above embodiment, the second timer is stopped when a MobilityFromNRCommand is received.
As a sub-embodiment of the above embodiment, the second timer is stopped when rrcreelease is received.
As a sub-embodiment of the above embodiment, expiration of the second timer is used to determine that the access blocking of the access category associated with the second timer is released.
As a sub-embodiment of the above embodiment, when the second timer is running, access of the access category associated with the second timer is blocked.
As a sub-embodiment of the above embodiment, the second timer includes T390.
As a sub-embodiment of the above embodiment, the second timer comprises T302.
As a sub-embodiment of the above embodiment, when the trigger reason for the behavior to initiate the RRC access request is an information bit generated at the first node U01, the fourth message is used to stop the second timer.
As a sub-embodiment of the above embodiment, when the trigger reason for the behavior to initiate the RRC access request is to forward an information bit generated at the second node U02, the fourth message is not used to stop the second timer.
Example 6
Embodiment 6 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in fig. 6. In fig. 6, U11 corresponds to a first node of the present application, and U12 corresponds to a second node of the present application, and it is specifically illustrated that the sequence in the present example does not limit the sequence of signal transmission and the sequence of implementation in the present application, and the steps in F61 and F62 are optional; example 6 is based on example 5, and the parts required in example 6 but not shown can be referred to in example 5.
For theFirst node U11In step S6101, a fourth wireless signal is transmitted; an RRC access request is initiated in step S6102; performing an access barring check according to the second parameter in step S6103; in step S6104, a third wireless signal is transmitted.
For theSecond node U12In step S6201, the process is performedReceiving a fourth wireless signal; in step S6202, a third wireless signal is received.
As an embodiment, the fourth wireless signal is transmitted at the PC5 interface.
As one embodiment, the fourth wireless signal is transmitted over a sidelink.
As an embodiment, the Physical Channel occupied by the fourth wireless signal includes a psch (Physical Sidelink Shared Channel).
As an embodiment, the Physical Channel occupied by the fourth wireless signal includes a PSCCH (Physical Sidelink Control Channel).
For one embodiment, the fourth wireless signal includes a fourth MAC PDU including a fourth MAC sub-PDU, a header of the fourth MAC sub-PDU is a fourth MAC sub-header, the fourth MAC sub-header includes 16 most significant bits of the first identity and 8 most significant bits of the second identity; the second identity is used to identify the first node U11.
As a sub-embodiment of the above embodiment, the first identity and the second identity are each a link layer identity.
As a sub-embodiment of the above embodiment, the first identity and the second identity are Layer-2 identities, respectively.
As a sub-embodiment of the above embodiment, said second identity is used to identify the first node U11.
As a sub-embodiment of the above embodiment, the first identity is used to identify the second node U12.
As a sub-embodiment of the above embodiment, the fourth MAC sub-PDU comprises the sixth message.
As an embodiment, the fourth wireless signal includes a fifth MAC PDU including a fifth MAC sub-PDU, a header of the fifth MAC sub-PDU is a fifth MAC sub-header, the fifth MAC sub-header includes 16 most significant bits of a third identity and 8 most significant bits of a fourth identity;
as a sub-embodiment of the above embodiment, the third identity and the fourth identity are each a link layer identity.
As a sub-embodiment of the above embodiment, the third identity and the fourth identity are Layer-2 identities, respectively.
As a sub-embodiment of the above embodiment, the fourth identity is used to identify a destination link layer identity.
As a sub-embodiment of the above embodiment, the third identity is used to identify the second node U12.
As a sub-embodiment of the above embodiment, the fourth MAC sub-PDU comprises the sixth message.
As a sub-embodiment of the above embodiment, said fourth identity is used to identify a link layer identity for broadcasting.
As a sub-embodiment of the above embodiment, the fourth identity is used to identify a link layer identity for multicast.
For one embodiment, the fourth wireless signal includes a sixth message.
As an embodiment, the sixth message is used to indicate a set of access categories that are not access blocked; the access category of the RRC connection request of the second node indicated by the first parameter belongs to the set of access reasons indicated by the sixth message which are not blocked by access;
wherein there is at least one timer associated with an access category maintained by the first node that is running; the running state of a timer maintained by the first node associated with one access class is used for access blocking checking.
As an embodiment, the sixth message comprises a PC5-RRC message.
For one embodiment, the sixth message comprises a PC5-S message.
For one embodiment, the sixth message comprises a discovery message.
For an embodiment, the sixth message includes rrcreconconfiguresildenink.
As an embodiment, the sixth message comprises a set of access classes that are not access blocked.
As an embodiment, the sixth message comprises a set of access classes blocked by access.
As a sub-embodiment of the above embodiment, the sixth message indicates a set of access classes that are not access blocked by indicating a set of access classes that are access blocked.
As an embodiment, any access category is associated with a timer, and access belonging to said any access category is blocked when said one timer associated with said any access category is running.
As an embodiment, the first access category is any access category, said first access category being associated with a timer, access belonging to said first access category being blocked when said one timer associated with said first access category is in a running state.
As an embodiment, the first access category is any access category, the first access category being associated with one timer, access associated with the first access category being blocked when the one timer associated with the first access category is in a running state.
As an embodiment, a timer associated with any access category in the set of access categories that is not access blocked is not running.
For one embodiment, the timer associated with the access category is T390.
As an embodiment, the first parameter belongs to the set of access classes that are not access blocked.
As an embodiment, when there is at least one timer associated with any one access category maintained by the first node U11 in a running state, the sixth message is used to indicate a set of access categories that are not access-blocked.
As an embodiment, when none of the timers associated with any one access class maintained by the first node U11 is in a running state, the sixth message does not include a set of access classes that are not blocked by access.
As a sub-embodiment of the above embodiment, the timer associated with any one access category is T390.
As a sub-embodiment of the above embodiment, the sixth message is used to indicate that the set of access classes that are not access blocked indicate that the first parameter is not restricted.
As a sub-embodiment of the above embodiment, the sixth message is used to indicate that the set of access classes not blocked by access indicates that the first parameter may be any access class.
As an embodiment, said sentence wherein the running state of a timer maintained by said first node associated with an access category is used for access blocking checking comprises: the running state of a timer maintained by the first node associated with one access class serves as an input parameter for an access barring check.
As an embodiment, said sentence wherein the running state of a timer maintained by said first node associated with an access category is used for access blocking checking comprises: when a timer associated with one access category maintained by the first node is running, access belonging to the one access category maintained by the first node is blocked.
As an embodiment, in response to the act performing blocking of the access blocking check, the first node U11 starts a first timer, transmits a third wireless signal comprising a fifth message, the fifth message being used to indicate that access is blocked, the fifth message being used to indicate an expiration of the first timer; the running status of the first timer is used for access blocking checking.
As a sub-embodiment of this embodiment, when the action performs an access blocking check according to the second parameter, resulting in an access blocking or not being allowed to access, the first timer is started and the third radio signal is transmitted.
As a sub-embodiment of this embodiment, the first timer is T390.
As a sub-embodiment of this embodiment, the third wireless signal is transmitted at the PC5 interface.
As a sub-embodiment of this embodiment, the third wireless signal is transmitted over a sidelink.
As a sub-embodiment of this embodiment, the Physical Channel occupied by the third wireless signal includes a psch (Physical Sidelink Shared Channel).
As a sub-embodiment of this embodiment, the Physical Channel occupied by the third wireless signal includes a PSCCH (Physical Sidelink Control Channel).
As a sub-embodiment of this embodiment, the fifth message comprises a PC5-RRC message.
As a sub-embodiment of this embodiment, the fifth message comprises a PC5-S message.
As a sub-embodiment of this embodiment, the fifth message comprises a discovery message.
As a sub-embodiment of this embodiment, the fifth message includes a Direct link release request.
As a sub-embodiment of this embodiment, the fifth message comprises rrcreeconfigurationsidelink.
As a sub-embodiment of this embodiment, the fifth message includes rrcreeconfigurationfailureseweilink.
As a sub-embodiment of this embodiment, the fifth message includes an expiration time of the first timer.
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.
As a sub-embodiment of this embodiment, the fifth message indicates a time at which the access category associated with the first timer is blocked.
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.
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.
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 not blocked.
As a sub-embodiment of this embodiment, the first timer is associated with the access category indicated by the first parameter.
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.
Example 7
Embodiment 7 illustrates a schematic diagram in which the running state of the first timer is used for access blocking check according to an embodiment of the present application, as shown in fig. 7.
As one embodiment, the first timer is associated with one access category.
As one embodiment, the first timer is associated with an access category indicated by the first parameter.
As one embodiment, the first timer is associated with an access category of the first parameter.
As an embodiment, the first timer is started when an access attempt is blocked after performing an access blocking check for an access category of access attempts associated with the first timer.
As an embodiment, the first timer is stopped after performing cell selection or reselection.
As an embodiment, the first timer is stopped after entering the RRC connected state.
As an embodiment, the first timer is stopped upon receiving the rrcreeconfiguration message including the recorfigurationwithsync.
As an embodiment, the first timer is stopped when the PCell is changed.
As an embodiment, the first timer is stopped upon receiving a MobilityFromNRCommand.
As an embodiment, the first timer is stopped upon receiving rrcrelease.
As one embodiment, expiration of the first timer is used to determine that access blocking of the access category associated with the first timer is released.
As an embodiment, when the first timer is running, access to the access category associated with the first timer is blocked.
For one embodiment, the first timer includes T390.
For one embodiment, the first timer includes T302.
As an embodiment, when the first timer is in a running state, access to an access category associated with the first timer is blocked.
As an embodiment, when the first timer is in the running state, access of access categories other than the access category '0' and the access category '2' is blocked.
As an embodiment, when the first timer is in a running state, access of access categories other than the access category included in the first parameter set is blocked.
As one embodiment, the behavioral access includes RRC access.
As one embodiment, the behavioral access includes sending data.
As an embodiment, the behavior access includes initiating a service.
As one embodiment, the behavioral access includes establishing an RRC connection.
As an embodiment, the behavior access includes establishing a PDU session.
Example 8
Embodiment 8 illustrates a schematic diagram in which the running state of the second timer is used for access blocking check according to an embodiment of the present application, as shown in fig. 8.
As an embodiment, the second timer is associated with one access category.
As one embodiment, the second timer is associated with an access category other than the access category indicated by the first parameter.
As one embodiment, the second timer is associated with an access category other than the access category of the second parameter.
As an embodiment, the second timer is started when an access attempt is blocked after performing an access blocking check for an access category of the access attempt associated with the second timer.
As an embodiment, the second timer is stopped after performing cell selection or reselection.
As an embodiment, the second timer is stopped after entering the RRC connected state.
As an embodiment, the second timer is stopped upon receiving the rrcconfiguration message including the recorconfigurewithsync.
As an embodiment, the second timer is stopped after changing the PCell.
As an embodiment, the second timer is stopped when a MobilityFromNRCommand is received.
As an embodiment, the second timer is stopped upon receiving rrcrelease.
As one embodiment, expiration of the second timer is used to determine that access blocking of the access category associated with the second timer is released.
As an embodiment, when the second timer is running, access to the access category associated with the second timer is blocked.
For one embodiment, the second timer includes T390.
For one embodiment, the second timer includes T302.
As an embodiment, when the second timer is in a running state, access to the access category associated with the second timer is blocked.
As an embodiment, when the second timer is in the running state, access of access categories other than the access category '0' and the access category '2' is blocked.
As an embodiment, when the second timer is in a running state, access of an access category other than the access category included in the first parameter set is blocked.
As one embodiment, the behavioral access includes RRC access.
As one embodiment, the behavioral access includes sending data.
As an embodiment, the behavior access includes initiating a service.
As one embodiment, the behavioral access includes establishing an RRC connection.
As one embodiment, the behavioral access includes establishing a PDU session.
Example 9
Embodiment 9 illustrates a schematic diagram in which whether a first parameter belongs to a first parameter set is used for determining a second parameter according to an embodiment of the present application, as shown in fig. 9.
As an embodiment, the first parameter set includes K1 parameters, any one of the K1 parameters is an access category, where K1 is a positive integer.
As a sub-embodiment of the above embodiment, said K1 is equal to 64.
As a sub-embodiment of the above embodiment, said K1 is equal to 1.
As a sub-embodiment of the above embodiment, said K1 is equal to 2.
As a sub-embodiment of the above embodiment, said K1 is equal to 3.
As a sub-embodiment of the above embodiment, said K1 is equal to 4.
As a sub-embodiment of the above embodiment, said K1 is equal to 8.
As a sub-embodiment of the above embodiment, the first set of parameters comprises an access category '0'.
As a sub-embodiment of the above embodiment, the first set of parameters comprises an access category '2'.
As a sub-embodiment of the above embodiment, the first set of parameters includes an access category corresponding to high priority traffic.
As a sub-embodiment of the above embodiment, the first set of parameters includes an access category corresponding to emergency traffic.
As an embodiment, the first set of parameters only includes an access category '0'.
As an embodiment, the first set of parameters only includes access class '2'.
As an embodiment, the first set of parameters only comprises access class '0' and access class '2'.
As an embodiment, the first set of parameters includes only access categories.
As an embodiment, the first set of parameters is fixed.
As one embodiment, the first set of parameters is system configured.
As an embodiment, the first set of parameters is pre-configured.
For one embodiment, the first set of parameters is configured via a SIB message.
As an embodiment, the first set of parameters is protocol defined.
For one embodiment, the first set of parameters includes an access category '0'.
For one embodiment, the first set of parameters includes an access category '2'.
As an embodiment, the first parameter is an access category.
As an embodiment, when the first parameter belongs to the first parameter set, the first parameter is determined to be the second parameter.
As an embodiment, when the first parameter belongs to the first set of parameters, if the second parameter does not belong to the first set of parameters, the first parameter is determined to be the second parameter; when the first parameter belongs to the first set of parameters, the first parameter is not used to be determined as the second parameter if the second parameter belongs to the first set of parameters.
As an embodiment, when the first parameter belongs to the first set of parameters, if the second parameter does not belong to the first set of parameters, the first parameter is determined to be the second parameter; when the first parameter belongs to the first set of parameters, if the second parameter belongs to the first set of parameters 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; when the first parameter belongs to the first set of parameters, the first parameter is not used to be determined as the second parameter if the second parameter belongs to the first set of parameters 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.
As an embodiment, when the first parameter belongs to the first set of parameters 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.
As an embodiment, the first parameter is not used for determining the second parameter when the first parameter does not belong to the first set of parameters.
As an embodiment, the second parameter is indicated by a higher layer of the first node when the first parameter does not belong to the first set of parameters.
As one embodiment, the second parameter is indicated by a non-access stratum of the first node when the first parameter does not belong to the first set of parameters.
As an embodiment, the second parameter is fixed when the first parameter does not belong to the first set of parameters.
As an embodiment, the second parameter is default when the first parameter does not belong to the first set of parameters.
As an embodiment, the second parameter is protocol defined when the first parameter does not belong to the first set of parameters.
As an embodiment, the second parameter is indicated by a higher layer when the first parameter does not belong to the first set of parameters.
As an embodiment, when the first parameter does not belong to the first parameter set, the second parameter is an access category corresponding to mo-Signalling.
As an embodiment, when the first parameter does not belong to the first parameter set, the second parameter is an access category corresponding to the mo-relay.
As an embodiment, when the first parameter does not belong to the first parameter set, the second parameter is an access category corresponding to a relay.
As an embodiment, when the first parameter does not belong to the first set of parameters, the second parameter is an access category '8'.
As an embodiment, when the first parameter belongs to the first parameter set, the larger of the first parameter and the third parameter is determined as a value of the second parameter; wherein the third parameter is an access category indicated by a higher layer.
As a sub-embodiment of the above embodiment, the access category indicated by the third parameter is an access category of the RRC access request of the first node.
Example 10
Embodiment 10 illustrates a block diagram of a processing apparatus for use in a first node according to one embodiment of the present application; as shown in fig. 10. In fig. 10, a processing arrangement 1000 in a first node comprises a first receiver 1001 and a first transmitter 1002. In the case of the embodiment 10, the following description is given,
a first transmitter 1002 that starts an RRC access request, and performs an access barring check according to a second parameter; determining the second parameter according to the trigger reason for starting the RRC access request; the second parameter is used to indicate an access category of the RRC access request of the first node 1000;
wherein the sentence determines the second parameter according to the trigger reason for starting the RRC access request, and the method comprises the following steps:
the second parameter is indicated by a higher layer when the trigger reason for the behavior-initiated RRC access request is an information bit generated at the first node 1000;
when the trigger reason for the behavior-initiated RRC access request is to forward information bits generated at the second node, whether the first parameter belongs to a first set of parameters is used to determine the second parameter; the first parameter is used to indicate an access category of the second node.
As an embodiment, the first receiver 1001 receives a first wireless signal, the first wireless signal including a first message, the first message being used to indicate the first parameter;
wherein the trigger reason for the behavior initiation of the RRC access request is to forward information bits generated at the second node.
As an embodiment, the first receiver 1001 receives a second wireless signal, where the second wireless signal includes a second message, and the second message is used for requesting RRC access of the second node; the second message includes a first cause indicating a cause of the RRC access requested by the second message, the first cause being associated with the first parameter; the first parameter is used to indicate an access category of the RRC access of the second node requested by the second message.
As an embodiment, the first transmitter 1002, as an unblocked response to the action performing an access blocking check, transmits a third message, the third message being used to request RRC access of the first node 1000; the third message comprises a second reason for indicating a reason for the RRC access requested by the third message; whether the second reason is associated with the second parameter, relating to the trigger reason for initiating the RRC access request;
the first receiver 1001 receives a fourth message, which is used to grant the request of the third message.
As an embodiment, the first transmitter 1002, in response to the act performing the access blocking check being blocked, starting a first timer, transmitting a third wireless signal, the third wireless signal comprising a fifth message, the fifth message used to indicate that access is blocked, the fifth message used to indicate an expiration of the first timer; the running status of the first timer is used for access blocking checking.
As an embodiment, whether the fourth message is used to stop the second timer is related to the trigger reason for starting the RRC access request;
wherein the second timer is associated with one access category; when the fourth message is received, the second timer is in a running state; the running status of the second timer is used for access blocking checking.
As an embodiment, the first transmitter 1002, transmits a fourth wireless signal, the fourth wireless signal comprising a sixth message, the sixth message being used to indicate a set of access classes that are not access-blocked; the access category of the RRC connection request of the second node indicated by the first parameter belongs to the set of access reasons indicated by the sixth message which are not blocked by access;
wherein there is at least one timer maintained by the first node 1000 associated with an access category in operation; the running state of the timer associated with one access class maintained by the first node 1000 is used for access blocking checking.
As an embodiment, the first parameter is different from the second parameter, the second parameter does not belong to the first set of parameters, and the first set of parameters includes at least one access category.
As an embodiment, when the action-initiated RRC access request is for information bits generated at the first node 1000 to also be forwarded at the second node, the trigger reason for the action-initiated RRC access request is considered to be for forwarding information bits generated at the second node.
As an embodiment, the first node is a User Equipment (UE).
As an embodiment, the first node is a terminal supporting a large delay difference.
As an embodiment, the first node is a terminal supporting NTN.
As an embodiment, the first node is an aircraft.
As an embodiment, the first node is a vehicle-mounted terminal.
As an embodiment, the first node is a relay.
As an embodiment, the first node is a ship.
As an embodiment, the first node is an internet of things terminal.
As an embodiment, the first node is a terminal of an industrial internet of things.
As an embodiment, the first node is a device supporting low-latency high-reliability transmission.
For one embodiment, the first receiver 1001 includes at least one of the antenna 452, the receiver 454, the receive processor 456, the multiple antenna receive processor 458, the controller/processor 459, the memory 460, or the data source 467 of embodiment 4.
For one embodiment, the first transmitter 1002 includes at least one of the antenna 452, the transmitter 454, the transmit processor 468, the multi-antenna transmit processor 457, the controller/processor 459, the memory 460, or the data source 467 of embodiment 4.
It will be understood by those skilled in the art that all or part of the steps of the above methods may be implemented by instructing relevant hardware through a program, and the program may be stored in a computer readable storage medium, such as a read-only memory, a hard disk or an optical disk. Alternatively, all or part of the steps of the above embodiments may be implemented by using one or more integrated circuits. Accordingly, the module units in the above embodiments may be implemented in a hardware form, or may be implemented in a form of software functional modules, and the present application is not limited to any specific form of combination of software and hardware. User equipment, terminal and UE in this application include but not limited to unmanned aerial vehicle, communication module on the unmanned aerial vehicle, remote control aircraft, the aircraft, small aircraft, the cell-phone, the panel computer, the notebook, vehicle Communication equipment, wireless sensor, network card, thing networking terminal, the RFID terminal, NB-IoT terminal, MTC (Machine Type Communication) terminal, eMTC (enhanced MTC) terminal, the data card, network card, vehicle Communication equipment, low-cost cell-phone, low-cost panel computer, satellite Communication equipment, ship Communication equipment, wireless Communication equipment such as NTN user equipment. The base station or system device in the present application includes, but is not limited to, a macro cell base station, a micro cell base station, a home base station, a relay base station, a gNB (NR node B) NR node B, a TRP (Transmitter Receiver Point), an NTN base station, a satellite device, a flight platform device, and other wireless communication devices.
The above description is only a preferred embodiment of the present application, and is not intended to limit the scope of the present application. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims (10)

1. A first node to be used for wireless communication, comprising:
a first transmitter for starting the RRC access request and executing access blocking check according to the second parameter; determining the second parameter according to the trigger reason for starting the RRC access request; the second parameter is used to indicate an access category of the RRC access request of the first node;
wherein the sentence determining the second parameter according to the trigger reason for starting the RRC access request includes:
the second parameter is indicated by a higher layer when the trigger cause of the behavior-initiated RRC access request is for an information bit generated at the first node;
when the trigger reason for the behavior-initiated RRC access request is to forward information bits generated at the second node, whether the first parameter belongs to the first set of parameters is used to determine the second parameter; the first parameter is used to indicate an access category of the second node.
2. The first node of claim 1, comprising:
a first receiver to receive a first wireless signal, the first wireless signal comprising a first message used to indicate the first parameter;
wherein the trigger reason for the behavior initiation of the RRC access request is to forward information bits generated at the second node.
3. The first node of claim 1, comprising:
the first receiver receives a second wireless signal, wherein the second wireless signal comprises a second message, and the second message is used for requesting RRC access of the second node; the second message includes a first cause indicating a cause of the RRC access requested by the second message, the first cause being associated with the first parameter; the first parameter is used to indicate an access category of the RRC access of the second node requested by the second message.
4. The first node according to any of claims 1 to 3, comprising:
the first transmitter, as a non-blocked response to the behavior performing an access blocking check, transmitting a third message, the third message being used to request RRC access of the first node; the third message comprises a second reason for indicating a reason for the RRC access requested by the third message; whether the second reason is associated with the second parameter, relating to the trigger reason for initiating the RRC access request;
the first receiver receives a fourth message, the fourth message being used to grant the request for the third message.
5. The first node according to any of claims 1 to 4, comprising:
the first transmitter, in response to the act performing the blocked access blocking check, starting a first timer, transmitting a third wireless signal, the third wireless signal comprising a fifth message, the fifth message used to indicate that access is blocked, the fifth message used to indicate an expiration time of the first timer; the running status of the first timer is used for access blocking checking.
6. The first node of claim 4,
whether the fourth message is used to stop a second timer is related to the trigger reason for initiating the RRC access request;
wherein the second timer is associated with one access category; when the fourth message is received, the second timer is in a running state; the running status of the second timer is used for access blocking checking.
7. The first node according to any of claims 1 to 6,
the first transmitter to transmit a fourth wireless signal comprising a sixth message used to indicate a set of access categories that are not access-blocked; the category of the RRC connection request of the second node indicated by the first parameter belongs to the set of access reasons indicated by the sixth message which are not blocked by access;
wherein there is at least one timer maintained by the first node associated with an access category in operation; the running state of a timer maintained by the first node associated with one access class is used for access blocking checking.
8. The first node according to any of claims 1 to 7,
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 at least comprises one access category.
9. The first node according to any of claims 1 to 8,
when the action-initiated RRC access request is for information bits generated at the first node and also for information bits generated at the second node to be forwarded, the trigger cause of the action-initiated RRC access request is considered to be for information bits generated at the second node to be forwarded.
10. A method in a first node used for wireless communication, comprising:
starting an RRC access request, and executing access blocking check according to the second parameter; determining the second parameter according to the trigger reason for starting the RRC access request; the second parameter is used to indicate an access category of the RRC access request of the first node;
wherein the sentence determines the second parameter according to the trigger reason for starting the RRC access request, and the method comprises the following steps:
the second parameter is indicated by a higher layer when a trigger reason for the behavior-initiated RRC access request is an information bit generated at the first node;
when the trigger reason for the behavior-initiated RRC access request is to forward information bits generated at the second node, whether the first parameter belongs to a first set of parameters is used to determine the second parameter; the first parameter is used to indicate an access category of the second node.
CN202110598044.9A 2021-05-31 2021-05-31 Method and equipment used for wireless communication Pending CN115484691A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110598044.9A CN115484691A (en) 2021-05-31 2021-05-31 Method and equipment used for wireless communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110598044.9A CN115484691A (en) 2021-05-31 2021-05-31 Method and equipment used for wireless communication

Publications (1)

Publication Number Publication Date
CN115484691A true CN115484691A (en) 2022-12-16

Family

ID=84419019

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110598044.9A Pending CN115484691A (en) 2021-05-31 2021-05-31 Method and equipment used for wireless communication

Country Status (1)

Country Link
CN (1) CN115484691A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI838136B (en) * 2023-02-23 2024-04-01 中華電信股份有限公司 Fault tolerance system for access and mobility management, method and computer readable medium thereof

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI838136B (en) * 2023-02-23 2024-04-01 中華電信股份有限公司 Fault tolerance system for access and mobility management, method and computer readable medium thereof

Similar Documents

Publication Publication Date Title
CN114726490B (en) Method and apparatus for wireless communication
CN113556687B (en) Method and equipment used for wireless communication
CN114499790A (en) Method and equipment used for wireless communication
CN112437442A (en) Method and equipment used for wireless communication
CN115484691A (en) Method and equipment used for wireless communication
WO2022111404A1 (en) Method used for wireless communication, and device
CN113938841B (en) Method and device used in node of wireless communication
CN115379530A (en) Method and equipment used for wireless communication
CN114916095A (en) Method and equipment used for wireless communication
CN116266918A (en) Method and apparatus for wireless communication
CN116133002A (en) Method and apparatus for wireless communication
CN114867131A (en) Method and equipment used for wireless communication
CN115118400A (en) Method and equipment used for wireless communication
CN113543369A (en) Method and equipment used for wireless communication
CN113115446B (en) Method and equipment used for wireless communication
WO2024032478A1 (en) Method and apparatus used in communication node for wireless communication
WO2024125278A1 (en) Method and device used for wireless communication
US20240179611A1 (en) Method and device for wireless communication
CN116233959A (en) Method and apparatus for wireless communication
CN115413057A (en) Method and equipment used for wireless communication
CN117580187A (en) Method and apparatus in a communication node for wireless communication
CN113873464A (en) Method and equipment used for wireless communication
CN117858277A (en) Method and apparatus for wireless communication
CN116828545A (en) Method and apparatus for wireless communication
CN115396980A (en) Method and equipment used for wireless communication

Legal Events

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