Method and apparatus for use in a communication node for wireless communication

Abstract

This application discloses a method and apparatus for use in a communication node for wireless communication. The method includes a communication node receiving a first message, the first message including a first identifier, the first identifier indicating a first node; transmitting a first preamble in a first random access process after the first message is received; and monitoring a PDCCH identified by a first RNTI within a first time window in response to the operation of transmitting the first preamble, the first message being an RRC message, a logical channel used to carry the first message being a PCCH, the first message including a first information block, air interface resources of the first preamble depending on the first information block, and the air interface resources including at least one of code domain resources, time domain resources, or frequency domain resources. According to the solution provided by this application, contention can be reduced, transmission delay is shortened, and signaling overhead is reduced.

Description

[Technical Field]

[0001] The present application relates to a transmission method and a transmission apparatus in a wireless communication system, and in particular to a transmission method and a transmission apparatus for random access and / or wireless resource control. [Background technology]

[0002] To reduce signaling overhead and latency, New Radio (NR) established the "MT(DL(Downlink))-SDT (Mobile Terminated-Small Data Transmission)" work item in Rel-18 to study MT-SDT procedures for initial DL data reception and subsequent UL / DL data transmission in RRC inactive state.

[0003] To reduce signaling overhead and latency, Rel-18 established the "Further NR Mobility Enhancements" work item, in which L1 (Layer 1) / L2 (Layer 2) triggered mobility (LTM) was studied.

[0004] With the continuous evolution of wireless communication technologies, reducing signaling overhead and latency have become important performance indicators. For example, to reduce signaling overhead and latency, NR (New Radio) established the "MT (DL (Downlink))-SDT (Mobile Terminated-Small Data Transmission)" work item in Rel-18, which investigated the MT-SDT procedure for initial DL (downlink) data reception and subsequent UL / DL data transmission in the RRC (Radio Resource Control) inactive state (RRC_INACTIVE). To reduce signaling overhead and latency, Rel-18 also established the "Further NR Mobility Enhancements" work item, which investigated L1 (Layer 1) / L2 (Layer 2) Triggered Mobility (LTM). Summary of the Invention

[0005] In the prior art, a random access (RA) process is triggered after a user equipment (UE) receives an RRC message instructing the UE via a paging control channel (PCCH). In this random access process, the air interface resource of the transmitted preamble is a contention-based random access (CBRA) resource configured by system information. The inventors have found that a random access collision failure increases transmission delay or signaling overhead. In particular, when a UE is triggered to perform MT-SDT by an RRC (Radio Resource Control) message carried by the PCCH, a random access collision failure increases transmission delay or signaling overhead. Therefore, it is necessary to enhance the random access process triggered by an RRC message carried by the PCCH.

[0006] In the prior art, the air interface resource of the preamble transmitted by the UE does not depend on the MAC (Medium Access Control) CE (Control Element) on which it is received. The inventors have proposed a method for specifying one MAC for L1 / L2 triggered mobility to indicate one candidate cell. It was found that when a UE receives a CE, if the uplink is not synchronized, it needs to acquire uplink synchronization of the candidate cell through a random access process. It is necessary to improve the method for acquiring uplink synchronization of the candidate cell as quickly as possible.

[0007] This application provides a random access solution to the above problem. In describing the above problem, an NR system is used as an example. This application is also applicable to scenarios such as LTE (Long-Term Evolution) systems, achieving technical effects similar to those of NR. Furthermore, although this application provides a specific implementation for MT-SDT, this application can also be used in scenarios such as multicast MBS (Multicast / Broadcast Service) in an RRC inactive state, achieving technical effects similar to those of MT-SDT. Furthermore, although this application is originally intended for the Uu air interface, this application can also be used for the PC5 interface. Furthermore, although this application is originally intended for a scenario involving a terminal and a base station, this application is also applicable to a V2X (Vehicle-to-Everything) scenario, as well as communication scenarios between a terminal and a relay and between a relay and a base station, achieving technical effects similar to those in the scenario involving a terminal and a base station. Furthermore, although the original intention of this application is for a scenario between a terminal and a base station, this application can also be applied to an IAB (Integrated Access and Backhaul) communication scenario, achieving the same technical effects as those in the scenario between a terminal and a base station. Furthermore, although the original intention of this application is for a terrestrial network (TN) scenario, this application can also be applied to a non-terrestrial network (NTN) communication scenario, achieving the same technical effects as those in the TN scenario. In addition, using a unified solution for different scenarios also helps reduce hardware complexity and costs.

[0008] In one embodiment, the interpretation of terms in this application refers to the definitions in the 3GPP specification protocol TS36 series.

[0009] In one embodiment, the interpretation of terms in this application refers to the definitions in the 3GPP specification protocol TS38 series.

[0010] In one embodiment, the interpretation of terms in this application refers to the definitions in the 3GPP specification protocol TS37 series.

[0011] In one embodiment, the interpretation of terms in this application refers to the definitions in the IEEE (Institute of Electrical and Electronics Engineers) specification protocols.

[0012] It should be noted that, where there is no contradiction, the embodiments and features in the embodiments of any node in the present application may be applied to any other node. Where there is no contradiction, the embodiments and features in the embodiments of the present application may be arbitrarily combined with each other.

[0013] The present application discloses a method for use in a first node for wireless communication, the method comprising: receiving a first message, the first message including a first identifier, the first identifier indicating a first node; After the first message is received, sending a first preamble in a first random access process; In response to the operation of transmitting the first preamble, monitoring a Physical Downlink Control Channel (PDCCH) identified by a first Radio Network Temporary Identifier (RNTI) within a first time window; The first message is one RRC message, the logical channel used to carry the first message is a PCCH, the first message includes a first information block, the air interface resources of the first preamble depend on the first information block, and the air interface resources include at least one of code domain resources, time domain resources, or frequency domain resources.

[0014] In one embodiment, the problem solved by this application includes a method for reducing transmission delay or reducing signaling overhead.

[0015] In one embodiment, the problem solved by the present application includes a method for determining air interface resources for a first preamble.

[0016] In one embodiment, the problem solved by the present application includes a method in which a first message indicates air interface resources for a first preamble.

[0017] In one embodiment, the method features include the first message including a first information block, and the air interface resources of the first preamble depend on the first information block.

[0018] In one embodiment, the method features include the air interface resources of the first preamble being dependent on the first information block in the first message.

[0019] In one embodiment, benefits of the above method include preventing the first node from selecting air interface resources for the first preamble from CBRA resources configured by system information, thereby reducing contention.

[0020] In one embodiment, the benefits of the above method include preventing the first node from selecting air interface resources for the first preamble from CBRA resources configured by the system information, thereby avoiding contention.

[0021] In one embodiment, the benefits of the above method include reduced transmission delay.

[0022] In one embodiment, the benefits of the above method include reduced signaling overhead.

[0023] According to one aspect of the present application, the method is characterized in that interpretation of the first information block depends on a second identifier, the second identifier is used by the first node, and the first identifier is different from the second identifier.

[0024] In one embodiment, the method features include the first information block being interpreted by the first node according to the second identifier.

[0025] In one embodiment, the benefits of the above method include preventing other UEs from interpreting the first information block.

[0026] According to one aspect of the present application, the method comprises: a first receiver for receiving a second message before the first message is received, the second message being used to determine to transition to an RRC_INACTIVE state; The second message includes a first identifier, the first message instructs the first node to perform data transmission in an RRC_INACTIVE state, and the first message is characterized in that it is received in the RRC_INACTIVE state.

[0027] In one embodiment, the problem solved by the present application includes a method for performing data transmission in an RRC_INACTIVE state as soon as possible when a first message indicates that the first node should perform data transmission in the RRC_INACTIVE state.

[0028] In one embodiment, the features of the above method include that when the first message indicates that the first node performs data transmission in an RRC_INACTIVE state, the first message includes a first information block.

[0029] In one embodiment, the benefits of the above method include reducing random access collisions and performing data transmission as quickly as possible in the RRC_INACTIVE state.

[0030] In one embodiment, the benefits of the above method include avoiding random access collisions and pre-determining data transmission as early as possible in the RRC_INACTIVE state.

[0031] According to one aspect of the present application, the method is characterized in that the first information block indicates at least one of a preamble sequence used by the first preamble, or an uplink (UL) carrier occupied by the first preamble, or a Reference Signal (RS) resource associated with the first preamble, or a PRACH mask of the first preamble.

[0032] In one embodiment, the method features include the first information block indicating air interface resources dedicated to the first preamble.

[0033] In one embodiment, the benefits of the above method include avoiding conflicts.

[0034] According to one aspect of the present application, the method comprises: a first receiver for receiving a third message, the third message being used to determine at least one PRACH (Physical Random Access Channel) configuration; The method is characterized in that the first information block indicates a first PRACH configuration among the at least one PRACH configuration, and the first PRACH configuration is used to determine air interface resources for the first preamble.

[0035] In one embodiment, the method includes the first information block indicating a first PRACH configuration dedicated to a first preamble in the PRACH configuration configured by the third message.

[0036] In one embodiment, the benefits of the above method include avoiding conflicts.

[0037] In one embodiment, the benefit of the above method is that the signaling authority in the first message This includes reducing the bar head.

[0038] According to one aspect of the present application, the method comprises: a first receiver for receiving a first DCI, the first random access process is deemed to be successfully completed in response to the first DCI being received, the first DCI being identified by the first RNTI; The first RNTI is characterized by being a C-RNTI (Cell RNTI).

[0039] In one embodiment, the method features include monitoring a PDCCH scrambled with the C-RNTI for the first preamble.

[0040] In one embodiment, the features of the above method include that the first DCI is used to determine that the first random access process has been completed successfully.

[0041] In one embodiment, the benefits of the above method include completing the random access process as quickly as possible.

[0042] In one embodiment, benefits of the above method include performing data transmission in the RRC_INACTIVE state as soon as possible when the first message indicates that the first node should perform data transmission in the RRC_INACTIVE state.

[0043] In one embodiment, the benefits of the above method include avoiding scheduling a MAC Random Access Response (RAR).

[0044] According to one aspect of the present application, the method comprises: a first receiver for receiving a first DCI and a first signaling, the first DCI being identified by a first RNTI, the first DCI being used to schedule the first signaling, and in response to the first signaling being received, the first random access process being deemed to have been successfully completed; The first signaling is characterized by including at least a timing advance.

[0045] According to one aspect of the present application, the above method is characterized in that the first RNTI is one C-RNTI, and the first signaling includes one Absolute Timing Advance MAC CE.

[0046] In one embodiment, the method features include monitoring a PDCCH scrambled with the C-RNTI for the first preamble.

[0047] In one embodiment, the method features include that the absolute timing advance MAC CE is used to determine that the first random access process has completed successfully.

[0048] In one embodiment, the benefits of the above method include avoiding scheduling MAC RARs.

[0049] The present application discloses a method for use in a second node for wireless communication, The method is: transmitting a first message, the first message including a first identifier, the first identifier indicating a first node; receiving a first preamble in a first random access process after the first message is sent; transmitting a PDCCH identified by the first RNTI in response to receiving the first preamble; The first preamble is characterized by the following: a sender of the first preamble monitors a PDCCH identified by a first RNTI within a first time window; the first message is one RRC message; a logical channel used to carry the first message is a PCCH; the first message includes a first information block; air interface resources of the first preamble depend on the first information block; and the air interface resources include at least one of code domain resources, time domain resources, or frequency domain resources.

[0050] According to one aspect of the present application, the method is characterized in that interpretation of the first information block depends on a second identifier, the second identifier is used by the first node, and the first identifier is different from the second identifier.

[0051] According to one aspect of the present application, the method comprises: transmitting a second message before the first message is transmitted, the second message being used to determine to transition to an RRC_INACTIVE state; The second message is characterized in that it includes a first identifier, the first message indicates that the sender of the first preamble will perform data transmission in the RRC_INACTIVE state, and the first message is received in the RRC_INACTIVE state.

[0052] According to one aspect of the present application, the above is characterized in that the first information block indicates at least one of a preamble sequence used by the first preamble, or an uplink carrier occupied by the first preamble, or an RS resource associated with the first preamble, or a PRACH mask of the first preamble.

[0053] According to one aspect of the present application, the method comprises: transmitting a third message, wherein the third message is used to determine at least one PRACH configuration; The method is characterized in that the first information block indicates a first PRACH configuration among the at least one PRACH configuration, and the first PRACH configuration is used to determine air interface resources for the first preamble.

[0054] According to one aspect of the present application, the method comprises: transmitting a first DCI, the first DCI being identified by a first RNTI; In response to receiving the first DCI, the sender of the first preamble considers the first random access process to be successfully completed, and the first RNTI is a C-RNTI.

[0055] According to one aspect of the present application, the method comprises: transmitting a first DCI and a first signaling, wherein the first DCI includes: a first DCI identified by an RNTI of In response to receiving the first signaling, the sender of the first preamble considers the first random access process to be successfully completed, and the first signaling is characterized by including at least a timing advance.

[0056] According to one aspect of the present application, the above method is characterized in that the first RNTI is one C-RNTI, and the first signaling includes one absolute timing advance MAC CE.

[0057] The present application discloses a first node for wireless communication, the first node comprising: a first receiver for receiving a first message, the first message including a first identifier, the first identifier indicating a first node; a first transmitter for transmitting a first preamble in a first random access process after the first message is received; In response to the operation of transmitting the first preamble, the first receiver monitors, within a first time window, a PDCCH identified by the first RNTI; The first message is characterized by: the first message is one RRC message; the logical channel used to carry the first message is a PCCH; the first message includes a first information block; the air interface resources of the first preamble depend on the first information block; and the air interface resources include at least one of code domain resources, time domain resources, or frequency domain resources.

[0058] The present application discloses a second node for wireless communication, the second node comprising: a second transmitter for transmitting a first message, the first message including a first identifier, the first identifier indicating the first node; and a second receiver for receiving the first preamble in a first random access process after the first message is transmitted; In response to receiving the first preamble, the second transmitter transmits a PDCCH identified by the first RNTI; The first preamble is characterized by the following: a sender of the first preamble monitors a PDCCH identified by a first RNTI within a first time window; the first message is one RRC message; a logical channel used to carry the first message is a PCCH; the first message includes a first information block; air interface resources of the first preamble depend on the first information block; and the air interface resources include at least one of code domain resources, time domain resources, or frequency domain resources.

[0059] The present application discloses a method for use in a first node for wireless communication, the method comprising: receiving a first message, the first message including a first identifier, the first identifier indicating a first cell; sending a first preamble in a first random access process after the first message is received; In response to the operation of transmitting the first preamble, monitoring a PDCCH identified by the first RNTI within a first time window; The first message is one MAC CE, the first message includes a first information block, and the air interface resource of the first preamble depends on the first information block, and the air interface resource is a code domain resource or a time domain resource. The resource is characterized by including at least one of a main resource or a frequency domain resource.

[0060] In one embodiment, the problem solved by the present application includes a method for determining air interface resources for a first preamble.

[0061] In one embodiment, the problem solved by the present application includes a method in which a first message indicates air interface resources for a first preamble.

[0062] In one embodiment, the features of the above method include that the air interface resource of the first preamble depends on the MAC CE.

[0063] In one embodiment, the benefits of the above method include obtaining uplink synchronization with this candidate cell as quickly as possible.

[0064] The present application discloses a method for use in a second node for wireless communication, the method comprising: transmitting a first message, the first message including a first identifier, the first identifier indicating a first cell; receiving a first preamble in a first random access process after the first message is sent; In response to the operation of transmitting the first preamble, the sender of the first preamble monitors a PDCCH identified by the first RNTI within a first time window, the first message is one MAC CE, the first message includes a first information block, the air interface resources of the first preamble depend on the first information block, and the air interface resources include at least one of code domain resources, time domain resources, or frequency domain resources.

[0065] The present application discloses a first node for wireless communication, the first node comprising: a first receiver for receiving a first message, the first message including a first identifier, the first identifier indicating a first cell; a first transmitter for transmitting a first preamble in a first random access process after the first message is received; In response to the operation of transmitting the first preamble, the first receiver monitors, within a first time window, a PDCCH identified by the first RNTI; The first message is characterized in that: the first message is one MAC CE; the first message includes a first information block; the air interface resources of the first preamble depend on the first information block; and the air interface resources include at least one of code domain resources, time domain resources, or frequency domain resources.

[0066] The present application discloses a second node for wireless communication, the second node comprising: a second transmitter for transmitting a first message, the first message including a first identifier, the first identifier indicating the first cell; a second receiver for receiving the first preamble in a first random access process after the first message is transmitted; In response to the operation of transmitting the first preamble, the sender of the first preamble monitors a PDCCH identified by the first RNTI within a first time window, the first message being one MAC CE, the first message including a first information block. The air interface resource of the first preamble depends on the first information block, and the air interface resource includes at least one of a code domain resource, a time domain resource, or a frequency domain resource.

[0067] In one embodiment, compared to conventional solutions, the present application has at least one of the following advantages: - Reduce competition, - Avoid conflicts, - Reduce transmission delays; - Reduce signaling overhead, - Avoid scheduling .MAC RAR, - Complete the random access process as quickly as possible. - Perform data transmission as quickly as possible in the RRC_INACTIVE state, and -.Acquire uplink synchronization as quickly as possible.

[0068] In the prior art, RRC messages are used for radio resource control. RRC messages dedicated to a UE (User Equipment) are transmitted via a dedicated logical channel. RRC messages not transmitted via a dedicated logical channel are non-UE specific. In particular, when a UE does not establish an RRC connection, the UE cannot receive RRC messages via a dedicated logical channel. The inventors have found that RRC messages not transmitted via a dedicated logical channel cannot set dedicated information for a UE to transmit or receive signals, thereby increasing delay and / or signaling overhead. Therefore, it is necessary to enhance the method for RRC messages not transmitted via a dedicated logical channel to transmit UE-specific information.

[0069] In view of the above-mentioned problems, the present application provides a solution for wireless resource control. In the description of the above-mentioned problems, an NR system is used as an example. The present application is also applicable to scenarios such as an LTE system. Furthermore, while the present application provides a specific implementation for MT-SDT, the present application can also be used in scenarios such as multicast MBS (multicast / broadcast service), achieving technical effects similar to those of MT-SDT. Furthermore, while the original intention of the present application is for the Uu air interface, the present application can also be used for the PC5 interface. Furthermore, while the original intention of the present application is for a scenario between a terminal and a base station, the present application can also be applied to a V2X (vehicle-to-everything) scenario, as well as communication scenarios between a terminal and a relay and between a relay and a base station, achieving technical effects similar to those in the scenario between a terminal and a base station. Furthermore, while the original intention of the present application is for a scenario between a terminal and a base station, the present application can also be applied to an IAB (integrated access and backhaul) communication scenario, achieving technical effects similar to those in the scenario between a terminal and a base station. Furthermore, although the original intention of this application is for a terrestrial network (TN) scenario, this application is also applicable to a non-terrestrial network (NTN) communication scenario, and achieves the same technical effects as those in the TN scenario. In addition, using a unified solution for different scenarios also helps reduce hardware complexity and costs.

[0070] In one embodiment, the interpretation of terms in this application refers to the definitions in the 3GPP specification protocol TS36 series.

[0071] In one embodiment, the interpretation of terms in this application refers to the definitions in the 3GPP specification protocol TS38 series.

[0072] In one embodiment, the interpretation of terms in this application refers to the definitions in the 3GPP specification protocol TS37 series.

[0073] In one embodiment, the interpretation of terms in this application refers to the definitions in the IEEE (Institute of Electrical and Electronics Engineers) specification protocols.

[0074] It should be noted that, where there is no contradiction, the embodiments and features in the embodiments of any node in the present application may be applied to any other node. Where there is no contradiction, the embodiments and features in the embodiments of the present application may be arbitrarily combined with each other.

[0075] The present application discloses a method for use in a first node for wireless communication, the method comprising: receiving a first message, the first message being an RRC message, the first message not being transmitted over a dedicated logical channel, the first message including a first identifier, the first identifier indicating a first node; and processing a first signal after the first message is received; The method is characterized by the fact that the operation of processing the first signal depends on the target information block, at least a former of the first information block and the second identifier is used to determine the target information block, the target information block is dedicated to the first node, the second identifier is used for the first node, the first identifier is different from the second identifier, the first message includes only a former of the first information block and the target information block, and the processing includes one of sending and receiving.

[0076] In one embodiment, the problem solved by this application includes a method for RRC messages that are not transmitted over dedicated logical channels to carry UE-specific information.

[0077] In one embodiment, the problem solved by this application includes how to prevent other UEs from using UE-specific information carried by RRC messages that are not transmitted over a dedicated logical channel.

[0078] In one embodiment, the method features include the first message including a first identifier, and the first identifier indicating the first node.

[0079] In one embodiment, features of the above method include: the first message includes a first information block; and at least the first information block and the second identifier are used to determine a target information block, the target information block being dedicated to the first node.

[0080] In one embodiment, the method includes the first message including only the first information block and the target information block.

[0081] In one embodiment, the method is characterized in that the operation of processing the first signal depends on the latter of the first information block and the target information block.

[0082] In one embodiment, benefits of the above method include the first message not being transmitted over a dedicated logical channel carrying dedicated information to the first node to avoid using a dedicated logical channel to transmit another RRC message, thereby reducing delay.

[0083] In one embodiment, the benefit of the above method is that the first message is a target information block. directly, thereby avoiding other UEs from using the information in the target information block.

[0084] In one embodiment, advantages of the above method include reduced signaling overhead.

[0085] According to one aspect of the present application, the above method is characterized in that the first information block and at least a part of the target identifier are used to determine the target information block, and the second identifier is used to generate the target identifier.

[0086] According to one aspect of the present application, the above method is characterized in that the first information block includes at least one bit, and the second identifier is a bit string.

[0087] According to one aspect of the present application, the method comprises: receiving at least a first sub-message and a second sub-message before the first message is received; The first sub-message is characterized by including a first identifier and the second sub-message includes a second identifier.

[0088] In one embodiment, the features of the above method include that the first identifier is preset, and only the former of the first information block and the second identifier is used to determine the target information block.

[0089] In one embodiment, the features of the above method include that the first identifier and the second identifier are preset, and the first information block and the second identifier are used to determine the target information block.

[0090] In one embodiment, benefits of the above method include ease of implementation.

[0091] In one embodiment, benefits of the above method include facilitating acquisition of the target information block.

[0092] According to one aspect of the present application, the method is characterized in that a first sub-message is used to decide to transition to an RRC_INACTIVE state, the logical channel used to carry the first message is a PCCH (Paging Control Channel), and the first message indicates that the first node implements data transmission in the RRC_INACTIVE state.

[0093] In one embodiment, the method includes the feature that when the first message indicates that the first node performs data transmission in an RRC_INACTIVE state, at least the first of the first information block and the second identifier is used to determine the target information block.

[0094] In one embodiment, the benefits of the above method include achieving the fastest possible transmission of MT-SDT.

[0095] According to one aspect of the present application, the above method is characterized in that the meaning of the phrase "the operation of processing the first signal depends on the target information block" is that the target information block indicates the air interface resources to be used for the first signal, and the air interface resources The resource includes at least one of a code domain resource, a time domain resource, or a frequency domain resource.

[0096] According to one aspect of the present application, the above method is characterized in that the first signal is a preamble.

[0097] According to one aspect of the present application, the above method is characterized in that the first signal is one DCI (Downlink Control Information).

[0098] The present application discloses a method for use in a second node for wireless communication, the method comprising: transmitting a first message, the first message being an RRC message, the first message not being transmitted over a dedicated logical channel, the first message including a first identifier, the first identifier indicating a first node; and processing a first signal after the first message is transmitted; The method is characterized by the fact that the operation of processing the first signal depends on the target information block, at least a former of the first information block and the second identifier is used to determine the target information block, the target information block is dedicated to the first node, the second identifier is used for the first node, the first identifier is different from the second identifier, the first message includes only a former of the first information block and the target information block, and the processing includes one of sending and receiving.

[0099] According to one aspect of the present application, the above method is characterized in that the first information block and at least a part of the target identifier are used to determine the target information block, and the second identifier is used to generate the target identifier.

[0100] According to one aspect of the present application, the above method is characterized in that the first information block includes at least one bit, and the second identifier is a bit string.

[0101] According to one aspect of the present application, the method comprises: transmitting at least a first sub-message and a second sub-message before the first message is transmitted; The first sub-message is characterized by including a first identifier and the second sub-message includes a second identifier.

[0102] According to one aspect of the present application, the method is characterized in that a first sub-message is used to decide to transition to an RRC_INACTIVE state, the logical channel used to carry the first message is a PCCH, and the first message indicates that the first node implements data transmission in the RRC_INACTIVE state.

[0103] According to one aspect of the present application, the above method is characterized in that the meaning of the phrase "the operation of processing the first signal depends on the target information block" includes that the target information block indicates air interface resources used for the first signal, and the air interface resources include at least one of code domain resources, time domain resources, or frequency domain resources.

[0104] According to one aspect of the present application, the above method is characterized in that the first signal is a preamble.

[0105] According to one aspect of the present application, the above method is characterized in that the first signal is one DCI.

[0106] The present application discloses a first node for wireless communication, the first node comprising: a first processing device for receiving a first message, the first message being an RRC message, the first message not being transmitted over a dedicated logical channel, the first message including a first identifier, the first identifier indicating a first node; and processing a first signal after the first message is received; The method is characterized by the fact that the operation of processing the first signal depends on the target information block, at least a former of the first information block and the second identifier is used to determine the target information block, the target information block is dedicated to the first node, the second identifier is used for the first node, the first identifier is different from the second identifier, the first message includes only a former of the first information block and the target information block, and the processing includes one of sending and receiving.

[0107] The present application discloses a second node for wireless communication, the second node comprising: a second processing device for transmitting a first message, the first message being one RRC message, the first message not being transmitted via a dedicated logical channel, the first message including a first identifier, the first identifier indicating a first node, and processing a first signal after the first message is transmitted; The method is characterized by the fact that the operation of processing the first signal depends on the target information block, at least a former of the first information block and the second identifier is used to determine the target information block, the target information block is dedicated to the first node, the second identifier is used for the first node, the first identifier is different from the second identifier, the first message includes only a former of the first information block and the target information block, and the processing includes one of sending and receiving.

[0108] In one embodiment, compared to conventional solutions, the present application has at least one of the following advantages: - Easy to implement, - Prevent other UEs from using the information in the target information block; - Facilitates the acquisition of target information blocks, -.MT-SDT realizes the fastest transmission, - Reduce delays, and - Reduces signaling overhead.

[0109] Other features, objects, and advantages of the present application will become more apparent from reading the detailed description of non-limiting embodiments with reference to the following drawings. [Brief explanation of the drawings]

[0110] [Figure 1A] 1 illustrates a flowchart of transmitting a first message, a first preamble, and a PDCCH identified by a first RNTI according to an embodiment of the present application; [Figure 1B]1 illustrates a flowchart of transmitting a first message and a first signal according to an embodiment of the present application. [Figure 2] 1 shows a schematic diagram of a network architecture according to an embodiment of the present application; [Figure 3] 1 illustrates a schematic diagram of an embodiment of a radio protocol architecture for user and control planes, according to an embodiment of the present application; [Figure 4] 1 shows a schematic diagram of a first communication device and a second communication device according to an embodiment of the present application; [Figure 5A] 1 shows a flowchart of wireless signal transmission according to an embodiment of the present application. [Figure 5B] 1 shows a flowchart of wireless signal transmission according to an embodiment of the present application. [Figure 6A] 1 shows a flowchart of wireless signal transmission according to another embodiment of the present application. [Figure 6B] 1 shows a schematic diagram of at least a portion of a first information block and a target identifier used to determine a target information block according to an embodiment of the present application; [Figure 7A] 10 shows a flowchart of wireless signal transmission according to yet another embodiment of the present application. [Figure 7B] FIG. 10 shows a schematic diagram of the second identifier being a bit string according to an embodiment of the present application; [Figure 8A] 1 shows a schematic diagram of the interpretation of a first information block depending on a second identifier according to an embodiment of the present application; [Figure 8B] FIG. 10 illustrates a schematic diagram of a first message instructing a first node to perform data transmission in an RRC_INACTIVE state according to an embodiment of the present application; [Figure 9A] FIG. 2 illustrates a schematic diagram of the air interface resources of the first preamble depending on the first information block according to an embodiment of the present application; [Figure 9B] FIG. 2 shows a schematic diagram of the processing of the first signal depending on the target information block according to an embodiment of the present application; [Figure 10A] 1 shows a schematic diagram of a first RNTI and a first signaling according to an embodiment of the present application; [Figure 10B] FIG. 1 illustrates a schematic diagram of a first signal being a preamble according to an embodiment of the present application; [Figure 11A] 10 illustrates a flowchart of transmitting a first message, a first preamble, and a PDCCH identified by a first RNTI according to another embodiment of the present application; [Figure 11B] 1 illustrates a schematic diagram of a first signal being one DCI according to an embodiment of the present application; [Figure 12A] FIG. 2 illustrates a structural block diagram of a processing device used in a first node according to an embodiment of the present application. [Figure 12B] 1 illustrates a schematic diagram of at least a portion of bits in a first information block and a target identifier being subjected to a first operation to obtain a target information block according to an embodiment of the present application; [Figure 13A] FIG. 2 illustrates a structural block diagram of a processing device used in a second node according to an embodiment of the present application. [Figure 13B] FIG. 2 illustrates a structural block diagram of a processing device used in a first node according to an embodiment of the present application. [Figure 14] FIG. 2 illustrates a structural block diagram of a processing device used in a second node according to an embodiment of the present application. DETAILED DESCRIPTION OF THE INVENTION

[0111] The technical solutions of the present application are described in further detail below in conjunction with the drawings. It should be noted that, if there is no contradiction, the embodiments and features of the embodiments of the present application can be arbitrarily combined with each other.

[0112] Embodiment 1A. Embodiment 1 illustrates a flowchart of transmitting a first message, a first preamble, and a PDCCH identified by a first RNTI according to an embodiment of the present application, as shown in Figure 1A. In Figure 1A, each block represents a step. It is emphasized that the order of the blocks in the figure does not represent the time relationship between the represented steps.

[0113] In embodiment 1A, a first node in the present application receives a first message in step 101A, the first message including a first identifier, the first identifier indicating the first node; in step 102A, after the first message is received, transmits a first preamble in a first random access process; and in step 103A, in response to the operation of transmitting the first preamble, monitors a PDCCH identified by a first RNTI within a first time window, the first message being an RRC message, the logical channel used to carry the first message being a PCCH, the first message including a first information block, and the air interface resource of the first preamble depends on the first information block, and the air interface resource includes at least one of a code domain resource, a time domain resource, or a frequency domain resource.

[0114] In one embodiment, the first message is received in the RRC_INACTIVE state.

[0115] In one embodiment, the sender of the first message is a maintenance base station for the first cell.

[0116] In one embodiment, the first cell is a PCell (Primary Cell) before the first node transitions to the RRC_INACTIVE state.

[0117] In one embodiment, the first cell is the cell from which the first node receives the last RRCRelease (RRC release) message before the first message is received.

[0118] In one embodiment, the sender of the first message is a maintenance base station of the cell in which the first node resides.

[0119] In one embodiment, the sender of the first message is a maintenance base station of a cell within the RAN-based Notification Area (RNA) of the first node.

[0120] In one embodiment, the RNA of the first node includes at least one cell.

[0121] In one embodiment, the RNA of the first node is preset.

[0122] In one embodiment, the first message is one RRC message, and the logical channel used to carry the first message is the PCCH.

[0123] In one embodiment, the first message is cell-common signaling.

[0124] In one embodiment, the first message is a downlink message.

[0125] In one embodiment, the first message is used for paging.

[0126] In one embodiment, the first message is used for RAN (Radio Access Network) paging.

[0127] In one embodiment, the first message is triggered by a Next Generation (NG)-RAN.

[0128] In one embodiment, the first message is a paging message.

[0129] In one embodiment, the first message includes at least one PagingRecord field.

[0130] In one embodiment, the first message includes at least one field with a name that includes a PagingRecord.

[0131] In one embodiment, the first message includes at least one PagingRecordList.

[0132] In one embodiment, the first message includes at least one field with a name that includes PagingRecordList.

[0133] In one embodiment, the first message includes one PagingRecord field, and the one PagingRecord field includes the first identifier.

[0134] In one embodiment, the first message includes one RRC field with a name containing a PagingRecord, and the one RRC field with a name containing a PagingRecord includes a first identifier.

[0135] In one embodiment, the first identifier matches the full I-RNTI of the first node.

[0136] In one embodiment, a first identifier is assigned to the first node.

[0137] In one embodiment, the first identifier indicates a first node in a first cell.

[0138] In one embodiment, the first identifier indicates the first node within the RNA of the first node.

[0139] In one embodiment, the first identifier is a single bit string.

[0140] In one embodiment, the first identifier comprises a positive integer number of bits.

[0141] In one embodiment, the first identifier is a bit string having a length of 40 bits.

[0142] In one embodiment, the first identifier is a bit string having a length of 24 bits.

[0143] In one embodiment, the first identifier is a PagingUE-Identity.

[0144] In one embodiment, the first identifier is one ng-5G-S-TMSI.

[0145] In one embodiment, the first identifier is a full I-RNTI.

[0146] In one embodiment, the first identifier is one NG-5G-S-TMSI.

[0147] In one embodiment, the first identifier is an I-RNTI-Value.

[0148] In one embodiment, the first identifier is a ShortI-RNTI-Value.

[0149] In one embodiment, the first identifier matches the fullI-RNTI stored by the first node.

[0150] In one embodiment, the first identifier matches a short I-RNTI stored by the first node.

[0151] In one embodiment, the first message includes a first field and a second field, and the first field and the second field indicate that the first node performs data transmission in an RRC_INACTIVE state.

[0152] In one embodiment, the first field and the second field are used together to indicate that the first node performs data transmission in the RRC_INACTIVE state.

[0153] In one embodiment, the value of the first field and the value of the second field indicate that the first node performs data transmission in an RRC_INACTIVE state.

[0154] In one embodiment, the first message includes a first field and a second field, where the first field includes a first identifier and the second field is used to indicate that the data transmission is performed in the RRC_INACTIVE state.

[0155] In one embodiment, the first message includes a first field, and the first field includes a first identifier.

[0156] As one subembodiment of this embodiment, the first message includes one PagingRecord field, which includes a first field, and the first field includes a first identifier.

[0157] As one subembodiment of this embodiment, the first message includes one RRC field having a name containing a PagingRecord, and the one RRC field having a name containing a PagingRecord includes a first field, and the first field includes a first identifier.

[0158] In one subembodiment of this embodiment, the first field is a ue-Identity field.

[0159] As a subembodiment of this embodiment, the first field is a PagingUE-Identity field.

[0160] As a subembodiment of this embodiment, the first field is a full I-RNTI field.

[0161] As a subembodiment of this embodiment, the first field is one I-RNTI-Value field.

[0162] As a subembodiment of this embodiment, the first field is a ShortI-RNTI-Value field.

[0163] In one embodiment, the first message triggers a first preamble.

[0164] In one embodiment, the first message triggers a first random access process, and the first preamble is transmitted in the first random access process.

[0165] In one embodiment, the recipient of the first preamble is different from the sender of the first message.

[0166] In one embodiment, the recipient of the first preamble is the same as the sender of the first message.

[0167] In one embodiment, the recipient of the first preamble is a serving base station of the first cell.

[0168] In one embodiment, the first preamble is an initial preamble in the first random access process.

[0169] In one embodiment, the first preamble is any preamble in the first random access process.

[0170] In one embodiment, the first preamble is a single preamble.

[0171] In one embodiment, the first random access process is performed on a first cell.

[0172] In one embodiment, the first random access process is a four-step random access process.

[0173] In one embodiment, the first random access process is triggered by the RRC sublayer.

[0174] In one embodiment, the first random access process is triggered by a first RRC recovery process.

[0175] In one embodiment, the first preamble is used for contention free random access (CFRA).

[0176] In one embodiment, the air interface resource of the first preamble includes a preamble sequence used by the first preamble.

[0177] In one embodiment, the air interface resource of the first preamble includes an uplink carrier occupied by the first preamble.

[0178] In one embodiment, the air interface resource of the first preamble includes a downlink radio signal associated with the first preamble.

[0179] In one embodiment, the air interface resource of the first preamble is Includes the PRACH mask from Liamble.

[0180] In one embodiment, a first set of conditions is met to trigger a first random access process of the operation, and the first set of conditions includes at least: a measurement result of the first RS resource is better than or not worse than a first threshold; the first RS resource is associated with a first preamble; and the first threshold is configurable.

[0181] In one embodiment, the PDCCH identified by the first RNTI is monitored on a first search space.

[0182] As one subembodiment of this embodiment, the first search space is a common search space (CSS).

[0183] In one subembodiment of this embodiment, the first search space is one USS (UE-specific search space).

[0184] In one embodiment, the act of transmitting the first preamble is used to determine the start of a first time window.

[0185] In one embodiment, a first time window is initiated in response to transmitting the first preamble.

[0186] In one embodiment, the first time window is one ra-ResponseWindow.

[0187] In one embodiment, the first time window is a time window having a name that includes ra-ResponseWindow.

[0188] In one embodiment, the first time window is set by an RRC message.

[0189] In one embodiment, the first time window is set by a System Information Block 1 (SIB1) message.

[0190] In one embodiment, the first time window is set by the second message in this application.

[0191] In one embodiment, the first RNTI is a C-RNTI.

[0192] As one subembodiment of this embodiment, the PDCCH identified by the first RNTI is used to schedule a random access response.

[0193] As one subembodiment of this embodiment, the PDCCH identified by the first RNTI is used to schedule an UL grant for a new transmission.

[0194] As one subembodiment of this embodiment, the PDCCH identified by the first RNTI is used to schedule a DL-SCH (Downlink Shared Channel).

[0195] As one subembodiment of this embodiment, any PDCCH identified by the first RNTI is monitored within a first time window.

[0196] As one subembodiment of this embodiment, any PDCCH of a first cell identified by a first RNTI is monitored within a first time window.

[0197] As one subembodiment of this embodiment, a PDCCH identified by a first RNTI for a random access response is monitored within a first time window.

[0198] As one subembodiment of this embodiment, a PDCCH of a first cell identified by a first RNTI for a random access response is monitored within a first time window.

[0199] As a subembodiment of this embodiment, one C-RNTI is the C-RNTI of a first node in a first cell.

[0200] As one subembodiment of this embodiment, one C-RNTI is the C-RNTI of the first node in a SpCell (Special Cell) of the first node.

[0201] As one subembodiment of this embodiment, one C-RNTI is a C-RNTI of the first node in the PCell of the first node.

[0202] In one embodiment, the first RNTI is an RA-RNTI.

[0203] As one subembodiment of this embodiment, a PDCCH identified by a first RNTI for a random access response is monitored within a first time window.

[0204] As one subembodiment of this embodiment, one RA-RNTI is determined according to the air interface resource of the first preamble.

[0205] As one subembodiment of this embodiment, the PDCCH identified by the first RNTI is used to schedule a random access response.

[0206] As one subembodiment of this embodiment, the PDCCH identified by the first RNTI is used to schedule the MAC RAR.

[0207] In one embodiment, the first RNTI is either one of a C-RNTI or a RA-RNTI.

[0208] In one embodiment, the PDCCH identified by the first RNTI is the PDCCH of the first cell.

[0209] In one embodiment, the first message indicates a first block of information.

[0210] In one embodiment, the first message implicitly indicates the first information block.

[0211] In one embodiment, the first message explicitly indicates the first information block.

[0212] In one embodiment, the first message is used to determine the first information block. Contains information that can be used.

[0213] In one embodiment, the first information block is associated with the first field.

[0214] In one embodiment, the first block of information is for the first field.

[0215] In one embodiment, the first information block depends on the first field.

[0216] In one embodiment, the first information block is valid only for the first field.

[0217] In one embodiment, the first information block is set to a PagingRecord field in the first message that includes the first identifier.

[0218] In one embodiment, the first information block belongs to a PagingRecord field in the first message that includes the first identifier.

[0219] In one embodiment, the first information block is associated with a PagingRecord field in the first message that includes the first identifier.

[0220] In one embodiment, the first information block includes the first identifier and is configured for an RRC field in the first message with a name that includes a PagingRecord.

[0221] In one embodiment, the first information block belongs to an RRC field in the first message that includes the first identifier and has a name that includes PagingRecord.

[0222] In one embodiment, the first information block includes the first identifier and is associated with an RRC field in the first message having a name that includes a PagingRecord.

[0223] In one embodiment, the first information block includes at least one RRC message.

[0224] In one embodiment, the first information block is one RRC field.

[0225] In one embodiment, the first information block is a plurality of RRC fields.

[0226] In one embodiment, the first information block includes one RRC field, and the value of one RRC field is one bit string.

[0227] In one embodiment, the first information block includes a plurality of RRC fields, and the value of each RRC field in the plurality of RRC fields is a bit string.

[0228] In one embodiment, the first information block includes a plurality of RRC fields, and a value of at least one RRC field in the plurality of RRC fields is a bit string.

[0229] In one embodiment, at least a portion of the air interface resources of the first preamble depend on the first information block.

[0230] In one embodiment, the air interface resources of the first preamble are at least also depends on the first information block.

[0231] In one embodiment, the air interface resources of the first preamble depend on all fields in the first information block.

[0232] In one embodiment, the air interface resources of the first preamble depend on some of the fields in the first information block.

[0233] In one embodiment, the first information block indicates air interface resources for the first preamble.

[0234] In one embodiment, the first information block is used to determine the air interface resource of the first preamble.

[0235] In one embodiment, at least one of the code domain resource, the time domain resource, or the frequency domain resource of the first preamble depends on the first information block.

[0236] In one embodiment, the code domain resource includes a preamble sequence.

[0237] In one embodiment, the code domain resource includes an index of a preamble sequence.

[0238] In one embodiment, the code domain resource includes a preamble resource.

[0239] In one embodiment, the time domain resources include resources occupied by PRACH opportunities in the time domain.

[0240] In one embodiment, the time domain resource comprises an Orthogonal Frequency Division Multiplexing (OFDM) symbol occupied by a PRACH opportunity in the time domain.

[0241] In one embodiment, the time domain resource includes the initial OFDM symbol occupied by the PRACH opportunity in the time domain.

[0242] In one embodiment, the time domain resource includes an index of an initial OFDM symbol occupied by a PRACH opportunity in the time domain.

[0243] In one embodiment, the time domain resource comprises a time slot occupied by a PRACH opportunity in the time domain.

[0244] In one embodiment, the time domain resource includes an index of an initial time slot occupied by a PRACH opportunity in the time domain in one system frame.

[0245] In one embodiment, the frequency domain resource comprises a subcarrier spacing.

[0246] In one embodiment, the frequency domain resource comprises a subcarrier spacing used to determine the index of the initial time slot occupied by the PRACH opportunity in the time domain in one system frame.

[0247] In one embodiment, the frequency domain resources include resources occupied by PRACH opportunities in the frequency domain.

[0248] In one embodiment, the frequency domain resource includes an index of a PRACH opportunity in the frequency domain.

[0249] In one embodiment, the frequency domain resource includes an uplink carrier for transmitting the first preamble.

[0250] Embodiment 1B

[0023] Embodiment 1B illustrates a flowchart of transmitting a first message and a first signal according to an embodiment of the present application, as shown in Figure 1B. In Figure 1B, each block represents one step. It is emphasized that the order of the blocks in the figure does not represent the time relationship between the represented steps.

[0251] In embodiment 1B, a first node in the present application receives a first message in step 101B, the first message being an RRC message, the first message not being transmitted via a dedicated logical channel, the first message including a first identifier, the first identifier indicating the first node, and in step 102B, after the first message is received, processes a first signal, the operation of processing the first signal being dependent on a target information block, at least a former of the first information block and a second identifier being used to determine the target information block, the target information block being dedicated to the first node, the second identifier being used for the first node, the first identifier being different from the second identifier, the first message including only a former of the first information block and the target information block, and the processing includes one of sending and receiving.

[0252] In one embodiment, the first message is a downlink message.

[0253] In one embodiment, the first message is a sidelink (SL) message.

[0254] In one embodiment, the first message is used to broadcast system information.

[0255] In one embodiment, the first message is used to configure control information that applies to the MBS broadcast service.

[0256] In one embodiment, the first message is used for paging.

[0257] In one embodiment, the first message is used for RAN (Radio Access Network) paging.

[0258] In one embodiment, the first message is triggered by a NG (Next Generation)-RAN.

[0259] In one embodiment, the first message is not carried by any signaling radio bearer (SRB).

[0260] In one embodiment, the signaling radio bearer of the first message is one default He is a RB.

[0261] In one embodiment, the signaling radio bearer of the first message is one SRB.

[0262] In one embodiment, the signaling radio bearer of the first message is one MRB (MBS Radio Bearer).

[0263] In one embodiment, the signaling radio bearer of the first message is one SRB0 (Signaling Radio Bearer 0).

[0264] In one embodiment, the phrase "the first message is not transmitted over a dedicated logical channel" means that the logical channel used to carry the first message is not a dedicated logical channel of the first node.

[0265] In one embodiment, the phrase "the first message is not transmitted over a dedicated logical channel" means that the first message is transmitted over a common logical channel.

[0266] In one embodiment, the dedicated logical channel refers to a DCCH (Dedicated Control Channel).

[0267] In one embodiment, the dedicated logical channels include at least a DCCH.

[0268] In one embodiment, the dedicated logical channel includes a Dedicated Traffic Channel (DTCH).

[0269] In one embodiment, the phrase "the first message is not transmitted over a dedicated logical channel" means that the first message is transmitted over the PCCH.

[0270] In one embodiment, the phrase "the first message is not transmitted over a dedicated logical channel" means that the first message is transmitted over a BCCH (Broadcast Control Channel).

[0271] In one embodiment, the phrase "the first message is not transmitted over a dedicated logical channel" means that the first message is transmitted over a CCCH (Common Control Channel).

[0272] In one embodiment, the phrase "the first message is not transmitted via a dedicated logical channel" refers to the first message being transmitted via an MCCH (MBS Control Channel).

[0273] In one embodiment, the phrase "the first message is not transmitted over a dedicated logical channel" means that the first message is transmitted over a Sidelink Broadcast Control Channel (SBCCH).

[0274] In one embodiment, one field in the first message includes a first identifier.

[0275] In one embodiment, one field in the first message indicates a first identifier.

[0276] In one embodiment, one field in the first message is set to the first identifier.

[0277] In one embodiment, the first message includes at least one identifier, and the first identifier is an identifier within the at least one identifier.

[0278] In one embodiment, the first identifier indicates a first node in at least one cell.

[0279] In one embodiment, the first identifier indicates a first node in a first cell.

[0280] In one embodiment, the first identifier indicates the first node within the RNA of the first node.

[0281] In one embodiment, the first identifier is assigned by the MAC sublayer.

[0282] In one embodiment, the first identifier is assigned by the RRC sublayer.

[0283] In one embodiment, the first identifier is assigned by a protocol layer above the RRC sublayer.

[0284] In one embodiment, a first identifier is assigned to the first node.

[0285] In one embodiment, the first identifier comprises at least one bit.

[0286] In one embodiment, the first identifier is a single bit string.

[0287] In one embodiment, the first identifier is a bit string having a length of 40 bits.

[0288] In one embodiment, the first identifier is a bit string having a length of 24 bits.

[0289] In one embodiment, the first identifier is an identifier of one of the first nodes.

[0290] In one embodiment, the first identifier is a Radio Network Temporary Identifier (RNTI).

[0291] In one embodiment, the first identifier is a UE_ID.

[0292] In one embodiment, the first identifier is a PagingUE-Identity.

[0293] In one embodiment, the first identifier is one ng-5G-S-TMSI.

[0294] In one embodiment, the first identifier is a full I-RNTI.

[0295] In one embodiment, the first identifier is one NG-5G-S-TMSI.

[0296] In one embodiment, the first identifier is an I-RNTI-Value.

[0297] In one embodiment, the first identifier is a ShortI-RNTI-Value.

[0298] In one embodiment, the first identifier matches the fullI-RNTI stored by the first node.

[0299] In one embodiment, the first identifier matches a short I-RNTI stored by the first node.

[0300] In one embodiment, the first message includes a plurality of fields, which are used to indicate the first information block and the first identifier.

[0301] In one embodiment, the first information block and the first identifier belong to the same RRC field in the first message.

[0302] In one embodiment, after the first message is received, the RRC sublayer instructs the lower layer to process the first signal.

[0303] In one embodiment, in response to receiving the first message, a first signal is processed.

[0304] In one embodiment, after a first information block in a first message is received, the first signal is processed.

[0305] In one embodiment, the first signal is processed after the target information block is determined according to at least the first information block and the second identifier.

[0306] In one embodiment, the first signal is processed after the RRC sublayer instructs the lower layer to process the first signal according to the target information block.

[0307] In one embodiment, "the operation of processing the first signal is dependent on the target information block" includes processing the first signal in accordance with at least the target information block.

[0308] In one embodiment, "the operation of processing the first signal depends on the target information block" includes the target information block being used to determine air interface resources for processing the first signal.

[0309] In one embodiment, "the operation of processing the first signal is dependent on the target information block" includes the target information block being used to determine the power for processing the first signal.

[0310] In one embodiment, "the operation of processing the first signal depends on the target information block" includes the target information block being used to determine an MCS for processing the first signal.

[0311] In one embodiment, the target information block is an air interface block used for the first signal. Specifies a face resource.

[0312] In one embodiment, the target information block indicates configuration information of the air interface resource used for the first signal.

[0313] In one embodiment, the target information block indicates one piece of setting information.

[0314] In one embodiment, the target information block indicates one PRACH (Physical Random Access Channel) resource, and the first signal is one preamble.

[0315] In one embodiment, the target information block indicates one PDCCH (Physical Downlink Control Channel) configuration information, and the first signal is one DCI.

[0316] In one embodiment, the target information block indicates one UL grant and the first signal is one PUSCH (Physical Uplink Shared Channel) transmission.

[0317] In one embodiment, the target information block indicates one CG (Configured Grant) resource, and the first signal is one PUSCH transmission.

[0318] In one embodiment, the target information block is the truth value of the first information block.

[0319] In one embodiment, the target information block is obtained after the value of the first information block is decoded.

[0320] In one embodiment, in response to receiving the first information block, the first processing device determines a target information block according to at least the first information block and the second identifier.

[0321] In one embodiment, in response to receiving the first information block, the RRC sublayer of the first node determines a target information block according to at least the first information block and the second identifier.

[0322] In one embodiment, only the first information block and the second identifier are used to determine the target information block.

[0323] In one subembodiment of this embodiment, the determination of the target information block is independent of the second identifier.

[0324] In one subembodiment of this embodiment, there is no second identifier.

[0325] In one subembodiment of this embodiment, there is a second identifier.

[0326] As one subembodiment of this embodiment, in response to receiving the first information block, the target information block is determined according to only the first information block and the second identifier.

[0327] As one subembodiment of this embodiment, the first information block explicitly indicates one encryption rule.

[0328] As one subembodiment of this embodiment, the first information block explicitly indicates one decoding rule.

[0329] As a subembodiment of this embodiment, the first information block implicitly indicates one encryption rule.

[0330] As a subembodiment of this embodiment, the first information block implicitly indicates one decoding rule.

[0331] In one subembodiment of this embodiment, one encryption rule is determined before the first message.

[0332] In one subembodiment of this embodiment, one decoding rule is determined before the first message.

[0333] As a subembodiment of this embodiment, a message is received before the first message, the message indicating an encryption rule.

[0334] As a subembodiment of this embodiment, a message is received before the first message, the message indicating a decoding rule.

[0335] As a subembodiment of this embodiment, the one message received before the first message is one RRC message.

[0336] As a subembodiment of this embodiment, the one message received before the first message is one RRCRelease message.

[0337] As one subembodiment of this embodiment, the one message received before the first message is one RRCReconfiguration message.

[0338] As a subembodiment of this embodiment, the one message received before the first message is one MAC signaling.

[0339] As a subembodiment of this embodiment, the message received before the first message is a physical layer signaling.

[0340] In one embodiment of this embodiment, the first information block is decrypted according to a decryption rule corresponding to the encryption rule to obtain the target information block.

[0341] In one subembodiment of this embodiment, the first information block is decoded according to one decoding rule to obtain the target information block.

[0342] In one embodiment, the first information block and the second identifier are used to determine the target information block.

[0343] In one subembodiment of this embodiment, the second identifier is calculated by the first node.

[0344] In one subembodiment of this embodiment, the second identifier is selected by the first node. will be done.

[0345] In one subembodiment of this embodiment, the second identifier is determined by the first node.

[0346] In one subembodiment of this embodiment, the second identifier is preset.

[0347] As one subembodiment of this embodiment, the second identifier is assigned by the RRC sublayer.

[0348] In one subembodiment of this embodiment, the second identifier is assigned by the MAC sublayer.

[0349] As one subembodiment of this embodiment, the second identifier is assigned by a layer above the RRC sublayer.

[0350] In one subembodiment of this embodiment, the second identifier is assigned by the second node.

[0351] In one subembodiment of this embodiment, the second identifier is assigned by the first node.

[0352] As one subembodiment of this embodiment, the second identifier is set for the first node.

[0353] In one subembodiment of this embodiment, the second identifier is stored by the first node.

[0354] As a subembodiment of this embodiment, the second identifier is used by the first node for CRC (Cyclic redundancy check) scrambling.

[0355] As one subembodiment of this embodiment, the second identifier is used by the first node to monitor the PDCCH.

[0356] In one subembodiment of this embodiment, the second identifier is used to identify the first node.

[0357] As one subembodiment of this embodiment, the second identifier is used to identify the first node in the first cell.

[0358] In one subembodiment of this embodiment, the second identifier indicates a first node within at least one cell.

[0359] In one subembodiment of this embodiment, the second identifier indicates a first node within a specified cell.

[0360] As a subembodiment of this embodiment, the second identifier points to the first node within the RNA of the first node.

[0361] As a subembodiment of this embodiment, the second identifier indicates a first node within one TAC.

[0362] In one subembodiment of this embodiment, the second identifier is a single bit string.

[0363] As a subembodiment of this embodiment, the second identifier includes at least one bit.

[0364] In one subembodiment of this embodiment, the second identifier indicates the first node.

[0365] In one subembodiment of this embodiment, the second identifier indicates a private key.

[0366] In one subembodiment of this embodiment, the second identifier indicates one encryption rule.

[0367] As a subembodiment of this embodiment, the second identifier indicates one decoding rule.

[0368] As a subembodiment of this embodiment, the number of bits of the second identifier is not equal to the number of bits of the first identifier.

[0369] In one subembodiment of this embodiment, the number of bits of the second identifier is equal to the number of bits of the first identifier.

[0370] As a subembodiment of this embodiment, the second identifier is the RNTI of one of the first nodes.

[0371] As a subembodiment of this embodiment, the second identifier is a short I-RNTI of one of the first nodes.

[0372] As a subembodiment of this embodiment, the second identifier is a short I-RNTI stored by the first node.

[0373] As one subembodiment of this embodiment, the second identifier is a C-RNTI (Cell RNTI) of one of the first nodes.

[0374] As one subembodiment of this embodiment, the second identifier is a C-RNTI (Cell RNTI) stored by the first node.

[0375] As one subembodiment of this embodiment, the second identifier is a C-RNTI of the first node in the first cell.

[0376] In one subembodiment of this embodiment, the second identifier is not the first identifier.

[0377] In one embodiment, the name of the second information is different from the name of the first identifier.

[0378] As a subembodiment of this embodiment, the second identifier and the first identifier are set by different fields.

[0379] In one subembodiment of this embodiment, the second identifier and the first identifier are different. Set by signaling.

[0380] As one subembodiment of this embodiment, in response to receiving the first information block, the target information block is determined according to the first information block and the second identifier.

[0381] In one subembodiment of this embodiment, the truth value of the first information block depends on the second identifier.

[0382] As a subembodiment of this embodiment, the meaning of the first information block depends on the second identifier.

[0383] As a subembodiment of this embodiment, the information indicated by the first information block depends on the second identifier.

[0384] In one subembodiment of this embodiment, the decoding of the first information block depends on the second identifier.

[0385] As a subembodiment of this embodiment, the first information block is decoded according to the second identifier to obtain the target information block.

[0386] In one embodiment of this embodiment, the first information block is decrypted according to a decryption rule corresponding to the encryption rule to obtain the target information block.

[0387] In one subembodiment of this embodiment, the first information block is decoded according to one decoding rule to obtain the target information block.

[0388] In one embodiment, an encryption rule is an encryption algorithm.

[0389] In one embodiment, one encryption rule is used to determine the target information block according to only the first information block and the second identifier.

[0390] In one embodiment, a decoding rule is a decoding algorithm.

[0391] In one embodiment, one decoding rule is used to determine the target information block according to only the first information block and the second identifier.

[0392] In one embodiment, encryption means encoding.

[0393] In one embodiment, encryption means scrambling.

[0394] In one embodiment, the meaning of decryption includes deciphering.

[0395] In one embodiment, the meaning of decryption includes decoding.

[0396] In one embodiment, the meaning of decoding includes a decision.

[0397] In one embodiment, the meaning of decryption includes recovery.

[0398] In one embodiment, the meaning of decryption includes detection.

[0399] In one embodiment, the meaning of decryption includes verification.

[0400] In one embodiment, the target information block is used only for the first node.

[0401] In one embodiment, the target information block is configured for the first node.

[0402] In one embodiment, the target information block is not used by other nodes.

[0403] In one embodiment, the recipient of the first message includes at least one node, the first node is a node within the at least one node, and the target information block is dedicated to the first node of the at least one node.

[0404] In one embodiment, the first message indicates at least one node, the first node is a node within the at least one node, and the target information block is dedicated to the first node of the at least one node.

[0405] In one embodiment, the target information block is set for a first node of the at least one node.

[0406] In one embodiment, the target information block is used only for the first node of the at least one node.

[0407] In one embodiment, the first message includes a first block of information.

[0408] In one embodiment, the first message includes the first information block, and the first message does not include the target information block.

[0409] In one embodiment, any field other than the first information block in the first message does not include the target information block.

[0410] In one embodiment, at least one field in the first message is set in the first information block, and the first message does not include any fields set in the target information block.

[0411] In one embodiment, the first information block is at least one field in the first message.

[0412] In one embodiment, the first information block is a field in the first message.

[0413] In one embodiment, the first information block is a number of fields within the first message.

[0414] In one embodiment, the first message does not include the second identifier.

[0415] In one embodiment, the first message does not carry the second identifier.

[0416] In one embodiment, the act of processing the first signal includes transmitting the first signal.

[0417] In one embodiment, the act of processing the first signal includes receiving the first signal.

[0418] In one subembodiment of this embodiment, the processing includes monitoring.

[0419] In one subembodiment of this embodiment, the processing includes detecting.

[0420] Embodiment 2 Embodiment 2 illustrates a schematic diagram of a network architecture according to an embodiment of the present application, as shown in Figure 2. Figure 2 illustrates a network architecture 200 of a 5G NR (New Radio) / LTE (Long Term Evolution) / LTE-A (Long Term Evolution-Advanced) system. The 5G NR / LTE / LTE-A network architecture 200 may be referred to as a 5G System (5GS) / Evolved Packet System (EPS) 200 or some other suitable terminology. The 5GS / EPS 200 includes at least one of a User Equipment (UE) 201, a Radio Access Network (RAN) 202, a 5G Core Network (5GC) / Evolved Packet Core (EPC) 210, a Home Subscriber Server (HSS) / Unified Data Management (UDM) 220, and an Internet service 230. The 5GS / EPS may be interconnected with other access networks, although these entities / interfaces are not shown for simplicity. As shown in the figure, the 5GS / EPS provides packet-switched services, but those skilled in the art will readily understand that the various concepts presented throughout this application may be extended to networks providing circuit-switched services or other cellular networks. The RAN includes node 203 and other nodes 204. Node 203 provides user plane and control plane protocol termination for the UE 201. Node 203 may be connected to the other nodes 204 via an Xn interface (e.g., backhaul) / X2 interface.The node 203 may be referred to as a base station, base transceiver station, radio base station, radio transceiver device, transceiver device function, basic service set (BSS), extended service set (ESS), TRP (Transmitter Receiver Point), or some other suitable terminology. The node 203 provides an access point to the 5GC / EPC 210 for the UE 201. Examples of the UE 201 include a mobile phone, a smartphone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), satellite radio, non-terrestrial base station communications, satellite mobile communications, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a drone, an aircraft, a narrowband Internet of Things device, a machine-type communications device, a land transportation vehicle, an automobile, a wearable device, or any other device with similar functionality. Those skilled in the art may also refer to the UE 201 as a mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology. The node 203 is connected to the 5GC / EPC 210 via an S1 / NG interface. The 5GC / EPC 210 is a Mobility Management Entity (MME) / Authentication Management Field (AMF) / Session Management Function (SMF). Session Management Function) 211, other MME / AMF / SMF 214, S-GW (Service Gateway) / UPF (User Plane The UE 201 includes a User Plane Function (MME / AMF / SMF) 212 and a Packet Data Network Gateway (P-GW) / UPF 213. The MME / AMF / SMF 211 is a control node that handles signaling between the UE 201 and the 5GC / EPC 210. Generally, the MME / AMF / SMF 211 provides bearer management and connection management. All user Internet Protocol (IP) packets are transmitted through the S-GW / UPF 212, which is itself connected to the P-GW / UPF 213. The P-GW provides IP address allocation for the UE and other functions. The P-GW / UPF 213 is connected to Internet services 230. The Internet services 230 include Internet protocol services corresponding to the operator, and may specifically include the Internet, intranet, IMS (IP Multimedia Subsystem), and packet-switched streaming services.

[0421] In one embodiment, the UE 201 corresponds to the first node in this application.

[0422] In one embodiment, UE 201 is a piece of user equipment (UE).

[0423] In one embodiment, the UE 201 is a base station (BS) device.

[0424] In one embodiment, the UE 201 is an intermediate device.

[0425] In one embodiment, node 203 corresponds to the second node in this application.

[0426] In one embodiment, node 203 is a base station device.

[0427] In one embodiment, node 203 is user equipment.

[0428] In one embodiment, node 203 is an intermediate device.

[0429] In one embodiment, node 203 is a gateway.

[0430] In one embodiment, the user equipment supports transmission in a terrestrial network (TN).

[0431] In one embodiment, the user equipment supports transmission over non-terrestrial networks.

[0432] In one embodiment, the user equipment supports transmission in a network with large differential delay.

[0433] In one embodiment, the user equipment supports dual connection (DC) transmission.

[0434] In one embodiment, the user equipment comprises a handheld terminal.

[0435] In one embodiment, the user equipment includes a wearable device.

[0436] In one embodiment, the user equipment comprises an aircraft.

[0437] In one embodiment, the user equipment comprises a vehicle terminal.

[0438] In one embodiment, the user equipment comprises a watercraft.

[0439] In one embodiment, the user equipment includes an Internet of Things terminal.

[0440] In one embodiment, the user equipment includes an industrial internet of things terminal.

[0441] In one embodiment, the user equipment includes devices that support low latency and reliable transmission.

[0442] In one embodiment, the user equipment includes a test device.

[0443] In one embodiment, the user equipment includes a signaling tester.

[0444] In one embodiment, the base station device is a base transceiver station (BTS).

[0445] In one embodiment, the base station device includes a Node B (NB).

[0446] In one embodiment, the base station device includes a gNB.

[0447] In one embodiment, the base station device includes an eNB.

[0448] In one embodiment, the base station device includes an ng-eNB.

[0449] In one embodiment, the base station device includes an en-gNB.

[0450] In one embodiment, the base station device supports transmissions in a non-terrestrial network.

[0451] In one embodiment, the base station device supports a network with large differential delay.

[0452] In one embodiment, the base station device supports transmissions in a terrestrial network.

[0453] In one embodiment, the base station device comprises a macrocellular base station.

[0454] In one embodiment, the base station device comprises a microcell base station.

[0455] In one embodiment, the base station device comprises a picocell base station.

[0456] In one embodiment, the base station device comprises a femtocell.

[0457] In one embodiment, the base station device includes a base station device that supports large differential delays.

[0458] In one embodiment, the base station device comprises an airborne platform device.

[0459] In one embodiment, the base station device comprises a satellite device.

[0460] In one embodiment, the base station device includes a TRP (Transmit Receiving Point).

[0461] In one embodiment, the base station device includes a centralized unit (CU).

[0462] In one embodiment, the base station device includes a Distributed Unit (DU).

[0463] In one embodiment, the base station device includes a test device.

[0464] In one embodiment, the base station device includes a signaling tester.

[0465] In one embodiment, the base station device is an Integrated Access Broadcast (IAB) and Backhaul, Integrated Access and Backhaul nodes.

[0466] In one embodiment, the base station device includes an IAB donor.

[0467] In one embodiment, the base station device includes an IAB donor CU.

[0468] In one embodiment, the base station device comprises an IAB donor DU.

[0469] In one embodiment, the base station device includes an IAB-DU.

[0470] In one embodiment, the base station device comprises an IAB-MT.

[0471] In one embodiment, the relay device includes a relay apparatus.

[0472] In one embodiment, the relay device includes an L3 relay device.

[0473] In one embodiment, the relay device includes an L2 relay device.

[0474] In one embodiment, the intermediate device includes a router.

[0475] In one embodiment, the intermediate device includes a switch.

[0476] In one embodiment, the relay device comprises user equipment.

[0477] In one embodiment, the relay device comprises a base station device.

[0478] Embodiment 3 Embodiment 3 illustrates a schematic diagram of one embodiment of a user plane and control plane radio protocol architecture according to the present application, as shown in Figure 3. Figure 3 is a schematic diagram illustrating one embodiment of a user plane 350 and control plane 300 radio protocol architecture. Figure 3 illustrates the control plane 300 radio protocol architecture using 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 is referred to herein as PHY 301. Layer 2 (L2 layer) 305 is located above PHY 301 and includes a MAC (Media Access Control) sublayer 302, an RLC (Radio Link Control) sublayer 303, and a PDCP (Packet Data Convergence Protocol) sublayer 304. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by encrypting data packets and handover support. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to HARQ (Hybrid Automatic Repeat Request). The MAC sublayer 302 provides multiplexing between logical channels and transport channels. The MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) within a cell. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in Layer 3 (L3 layer) in the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring lower layers using RRC signaling. 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 is substantially the same as the radio protocol architecture of the corresponding layers and sublayers in the control plane 300 for the physical layer 351, the PDCP sublayer 354 in the L2 layer 355, the RLC sublayer 353 in the L2 layer 355, and the MAC sublayer 352 in the L2 layer 355, except that the PDCP sublayer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead.The L2 layer 355 in the user plane 350 also includes a Service Data Adaptation Protocol (SDAP) sublayer 356, which is responsible for mapping between QoS streams and data radio bearers (DRBs) to support service diversity.

[0479] As an embodiment, the radio protocol architecture in FIG. 3 is applicable to the first node in this application.

[0480] As an embodiment, the radio protocol architecture in FIG. 3 is applicable to the second node in this application.

[0481] In one embodiment, the first preamble in this application is generated in PHY301 or PHY351.

[0482] In one embodiment, the PDCCH identified by the first RNTI in this application is generated in PHY 301 or PHY 351 .

[0483] In one embodiment, the first DCI in this application is generated in PHY301 or PHY351.

[0484] In one embodiment, the first message in this application is generated in the RRC 306 .

[0485] In one embodiment, the first signaling in this application is generated in the RRC 306 .

[0486] In one embodiment, the first signaling in this application is generated in MAC 302 or MAC 352.

[0487] In one embodiment, the first signaling in this application is generated in PHY301 or PHY351.

[0488] In one embodiment, the second message in this application is generated in the RRC 306 .

[0489] In one embodiment, the second message in this application is generated in MAC 302 or MAC 352.

[0490] In one embodiment, the second message in this application is generated in PHY 301 or PHY 351.

[0491] In one embodiment, the third message in this application is generated in the RRC 306 .

[0492] In one embodiment, the third message in this application is generated in MAC 302 or MAC 352.

[0493] In one embodiment, the third message in this application is generated in PHY 301 or PHY 351.

[0494] In one embodiment, the first signal in this application is generated in the RRC 306 .

[0495] In one embodiment, the first signal in this application is generated in MAC 302 or MAC 352.

[0496] In one embodiment, the first signal in this application is generated in PHY301 or PHY351.

[0497] In one embodiment, the first sub-message in this application is generated in the RRC 306 .

[0498] In one embodiment, the first sub-message in this application is generated in MAC 302 or MAC 352.

[0499] In one embodiment, the first sub-message in this application is generated in PHY 301 or PHY 351.

[0500] In one embodiment, the second sub-message in this application is generated in the RRC 306 .

[0501] In one embodiment, the second sub-message in this application is generated in MAC 302 or MAC 352.

[0502] In one embodiment, the second sub-message in this application is generated in PHY 301 or PHY 351.

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

[0504] The first communication device 450 comprises 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 transmit device / receive device 454, and an antenna 452.

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

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

[0507] In a transmission from the second communication device 410 to the first communication device 450, each receiving device 454 in the first communication device 450 receives the signal via its corresponding antenna 452. Each receiving device 454 receives a signal transformed onto a radio frequency carrier. The receiver processor 456 recovers the modulated information and converts the radio frequency stream into a baseband multi-carrier symbol stream, which is then provided to the receive processor 456. The receive processor 456 and the multi-antenna receive processor 458 perform various signal processing functions of the L1 layer. The multi-antenna receive processor 458 performs receive analog precoding / beamforming operations on the baseband multi-carrier symbol stream from the receiving device 454. The receive processor 456 converts the baseband multi-carrier symbol stream that has undergone receive analog precoding / beamforming operations from the time domain to the frequency domain using a fast Fourier transform (FFT). In the frequency domain, the physical layer data signal and reference signal are demultiplexed by the receive processor 456, the reference signal is used for channel estimation, and the data signal undergoes 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 in the 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 the controller / processor 459. The controller / processor 459 implements the functionality of the L2 layer. The controller / processor 459 may be associated with a memory 460 that stores program code and data. The memory 460 may be referred to as a computer-readable medium. For transmissions from the second communication device 410 to the first communication device 450, the controller / processor 459 provides demultiplexing between transport and logical channels, packet reassembly, decoding, header decompression, and control signal processing to recover the upper layer data packets from the core network. The upper layer data packets are then provided to all protocol layers above the L2 layer. Various control signals may also be provided to L3 for L3 processing.

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

[0509] In the case of transmission from the first communication device 450 to the second communication device 410, the function in the second communication device 410 is similar to the receiving function in the first communication device 450 described in the case of transmission from the second communication device 410 to the first communication device 450. The controller / processor 475 may be associated with a memory 476 that stores program code and data. The memory 476 may be referred to as a computer-readable medium. For transmissions from the first communication device 450 to the second communication device 410, the controller / processor 475 provides demultiplexing between transport and logical channels, packet reassembly, decoding, header decompression, and control signal processing to recover upper layer data packets from the UE 450. The upper layer data packets from the controller / processor 475 may be provided to a core network.

[0510] In one embodiment, the first communication device 450 comprises at least one processor and at least one memory, wherein the at least one memory comprises computer program code, the at least one memory and the computer program code being configured to be used with the at least one processor, wherein the first communication device 450 at least receives a first message, the first message including a first identifier, the first identifier indicating a first node, and after the first message is received, transmits a first preamble in a first random access process, and in response to transmitting the first preamble, monitors a PDCCH identified by a first RNTI within a first time window, the first message being an RRC message, the logical channel used to carry the first message being a PCCH, the first message including a first information block, and air interface resources of the first preamble depending on the first information block, the air interface resources including at least one of code domain resources, time domain resources, or frequency domain resources.

[0511] In one embodiment, the first communication device 450 comprises a memory having stored thereon a computer-readable program of instructions, which, when executed by at least one processor, generates actions, the actions including: receiving a first message, the first message including a first identifier, the first identifier indicating a first node; transmitting a first preamble in a first random access process after the first message is received; and monitoring a PDCCH identified by a first RNTI within a first time window in response to transmitting the first preamble, the first message being an RRC message, the logical channel used to carry the first message being a PCCH, the first message including a first information block, air interface resources of the first preamble depending on the first information block, the air interface resources including at least one of code domain resources, time domain resources, or frequency domain resources.

[0512] In one embodiment, the second communication device 410 includes at least one processor and at least one memory, the at least one memory including computer program code, the at least one memory and the computer program code configured for use with the at least one processor. The second communication device 410 at least transmits a first message, the first message including a first identifier, the first identifier indicating a first node, receives a first preamble in a first random access process after the first message is transmitted, and transmits a PDCCH identified by a first RNTI in response to receiving the first preamble. a sender of the preamble of the first channel monitors a PDCCH identified by a first RNTI within a first time window, the first message is one RRC message, the logical channel used to carry the first message is a PCCH, the first message includes a first information block, and the air interface resources of the first preamble depend on the first information block, and the air interface resources include at least one of code domain resources, time domain resources, or frequency domain resources.

[0513] In one embodiment, the second communication device 410 comprises a memory having stored thereon a computer-readable program of instructions, which, when executed by at least one processor, generates an action, the action including transmitting a first message, the first message including a first identifier, the first identifier indicating a first node; receiving a first preamble in a first random access process after the first message is transmitted; and receiving a first preamble in response to receiving the first preamble, the first preamble indicating a first node identified by the first RNTI. and transmitting a PDCCH identified by the first RNTI, wherein a sender of the first preamble monitors a PDCCH identified by the first RNTI within a first time window, the first message is one RRC message, the logical channel used to carry the first message is a PCCH, the first message includes a first information block, air interface resources of the first preamble depend on the first information block, and the air interface resources include at least one of code domain resources, time domain resources, or frequency domain resources.

[0514] In one embodiment, the first communication device 450 comprises at least one processor and at least one memory, the at least one memory comprising computer program code, the at least one memory and the computer program code being configured for use with the at least one processor, the first communication device 450 receiving at least a first message, the first message being an RRC message, the first message not being transmitted via a dedicated logical channel, the first message including a first identifier, the first identifier indicating a first node, processing a first signal after the first message is received, the operation of processing the first signal being dependent on a target information block, at least a former of the first information block and a second identifier being used to determine the target information block, the target information block being dedicated to the first node, the second identifier being used for the first node, the first identifier being different from the second identifier, the first message including only a former of the first information block and the target information block, and the processing including one of sending and receiving.

[0515] In one embodiment, the first communication device 450 includes a memory having stored thereon a computer-readable program of instructions, which, when executed by at least one processor, generates actions, the actions including receiving a first message, the first message being an RRC message, the first message not being transmitted via a dedicated logical channel, the first message including a first identifier, the first identifier indicating a first node; and processing a first signal after the first message is received, the operation of processing the first signal being dependent on a target information block, wherein at least a former of the first information block and a second identifier is used to determine the target information block, the target information block being dedicated to the first node, the second identifier being used for the first node, the first identifier being different from the second identifier, the first message including only a former of the first information block and the target information block, and the processing including one of sending and receiving.

[0516] In one embodiment, the second communication device 410 includes at least one processor and at least one memory, the at least one memory including computer program code, the at least one memory and the computer program code configured for use with the at least one processor. The second communication device 410 transmits at least a first message, the first message being an RRC message, the first message not being transmitted over a dedicated logical channel, the first message including a first identifier, the first identifier indicating a first node, and after the first message is received, processing a first signal, the operation of processing the first signal being dependent on a target information block, at least a former of the first information block and a second identifier being used to determine the target information block, the target information block being dedicated to the first node, the second identifier being used for the first node, the first identifier being different from the second identifier, the first message including only a former of the first information block and the target information block, and the processing including one of sending and receiving.

[0517] In one embodiment, the second communication device 410 includes a memory having stored thereon a computer-readable program of instructions, which, when executed by at least one processor, generates actions, the actions including: transmitting a first message, the first message being an RRC message, the first message not being transmitted over a dedicated logical channel, the first message including a first identifier, the first identifier indicating a first node; and processing a first signal after the first message is received, the operation of processing the first signal being dependent on a target information block, wherein at least a former of the first information block and a second identifier is used to determine the target information block, the target information block being dedicated to the first node, the second identifier being used for the first node, the first identifier being different from the second identifier; the first message including only a former of the first information block and the target information block; and the processing including one of sending and receiving.

[0518] In one embodiment, at least one of the antenna 452, the receiving device 454, the receiving processor 456, and the controller / processor 459 is used to receive the first message.

[0519] In one embodiment, at least one of the antenna 420, the transmitting device 418, the transmitting processor 416, and the controller / processor 475 is used to transmit the first message.

[0520] In one embodiment, at least one of the antenna 452, the receiving device 454, the receiving processor 456, and the controller / processor 459 is used to monitor a PDCCH identified by the first RNTI.

[0521] In one embodiment, at least one of the antenna 420, the transmitting device 418, the transmit processor 416, and the controller / processor 475 is used to monitor a PDCCH identified by the first RNTI.

[0522] In one embodiment, at least one of the antenna 452, the receiving device 454, the receiving processor 456, and the controller / processor 459 is used to receive the second message.

[0523] In one embodiment, the antenna 420, the transmitting device 418, the transmitting processor 416, and and at least one of controller / processor 475 is used to transmit the second message.

[0524] In one embodiment, at least one of the antenna 452, the receiving device 454, the receiving processor 456, and the controller / processor 459 is used to receive the third message.

[0525] In one embodiment, at least one of the antenna 420, the transmitting device 418, the transmitting processor 416, and the controller / processor 475 is used to transmit the third message.

[0526] In one embodiment, at least one of the antenna 452, the receiving device 454, the receiving processor 456, and the controller / processor 459 is used to receive the first DCI.

[0527] In one embodiment, at least one of the antenna 420, the transmitting device 418, the transmit processor 416, and the controller / processor 475 is used to transmit the first DCI.

[0528] In one embodiment, at least one of the antenna 452, the receiving device 454, the receiving processor 456, and the controller / processor 459 is used to receive the first signaling.

[0529] In one embodiment, at least one of the antenna 420, the transmitting device 418, the transmit processor 416, and the controller / processor 475 is used to transmit the first signaling.

[0530] In one embodiment, at least one of the antenna 452, the transmitting device 454, the transmit processor 468, and the controller / processor 459 is used to transmit the first preamble.

[0531] In one embodiment, at least one of the antenna 420, the receiving device 418, the receiving processor 470, and the controller / processor 475 is used to receive the first preamble.

[0532] In one embodiment, at least one of the antenna 452, the receiver 454, the receiver processor 456, and the controller / processor 459 is used to receive the first sub-message.

[0533] In one embodiment, at least one of antenna 420, transmitter 418, transmit processor 416, and controller / processor 475 is used to transmit the first sub-message.

[0534] In one embodiment, at least one of the antenna 452, the receiving device 454, the receiving processor 456, and the controller / processor 459 is used to receive the second sub-message.

[0535] In one embodiment, at least one of antenna 420, transmitter 418, transmit processor 416, and controller / processor 475 is used to transmit the second sub-message.

[0536] In one embodiment, at least one of the antenna 452, the receiving device 454, the receiving processor 456, and the controller / processor 459 is used to receive the first signal.

[0537] In one embodiment, at least one of the antenna 420, the transmitting device 418, the transmitting processor 416, and the controller / processor 475 is used to transmit the first signal.

[0538] In one embodiment, at least one of the antenna 452, the transmitting device 454, the transmitting processor 468, and the controller / processor 459 is used to transmit a first signal.

[0539] In one embodiment, at least one of the antenna 420, the receiving device 418, the receiving processor 470, and the controller / processor 475 is used to receive the first signal.

[0540] In one embodiment, the first communication device 450 corresponds to the first node in this application.

[0541] In one embodiment, the second communication device 410 corresponds to a second node in this application.

[0542] In one embodiment, the first communication device 450 corresponds to the first node in this application.

[0543] In one embodiment, the second communication device 410 corresponds to a second node in this application.

[0544] In one embodiment, the first communication device 450 is a piece of user equipment.

[0545] In one embodiment, the first communication device 450 is a base station device.

[0546] In one embodiment, the second communication device 410 is a piece of user equipment.

[0547] In one embodiment, the second communication device 410 is a base station device.

[0548] Embodiment 5A 5A illustrates a flowchart of wireless signal transmission according to an embodiment of the present application, as shown in FIG. 5A. It should be noted that the order in this example does not limit the order of signal transmission and implementation in the present application.

[0549] For a first node U01A, in step S5101A, a first message is received, the first message including a first identifier; in step S5102A, after the first message is received, a first preamble is transmitted in a first random access process; in step S5103A, in response to the operation of transmitting the first preamble, a PDCCH identified by a first RNTI is monitored within a first time window; in step S5104A, a first DCI is received, the first DCI is identified by a first RNTI, the first RNTI is one C-RNTI; and in step S5105A, in response to receiving the first DCI, a first random access is performed. In step S5106A, a first DCI and first signaling are received, the first DCI is identified by a first RNTI, the first DCI is used to schedule the first signaling, and the first signaling includes at least a timing advance, and in step S5107A, in response to the first signaling being received, the first random access process is deemed to have been completed successfully.

[0550] For the second node N02A, in step S5201A, a first message is transmitted, in step S5202A, a first preamble is received, in step S5203A, a first DCI is transmitted, and in step S5204A, the first DCI and first signaling are transmitted.

[0551] In embodiment 5A, the first message includes a first information block, and the air interface resources of the first preamble depend on the first information block, and the air interface resources include at least one of code domain resources, time domain resources, or frequency domain resources.

[0552] In one embodiment, the first message is one RRC message, the logical channel used to carry the first message is PCCH, and the first identifier indicates the first node U01A.

[0553] In one embodiment, the first message is a piece of MAC signaling, and the first identifier indicates the first cell.

[0554] As an embodiment, this example does not limit whether the sender of the first message is the same as the recipient of the first preamble in this application.

[0555] In one embodiment, the phrase "first DCI identified by first RNTI" means that the CRC (Cyclic Redundancy Check) of the first DCI is scrambled by the first RNTI.

[0556] In one embodiment, the phrase "the first DCI is identified by the first RNTI" means that the first DCI is addressed by the first RNTI.

[0557] In one embodiment, the phrase "the first DCI is identified by the first RNTI" means that the first DCI is received on a PDCCH identified by the first RNTI.

[0558] In one embodiment, the phrase "a first DCI identified by a first RNTI" means that the first DCI is one PDCCH transmission.

[0559] In one embodiment, the phrase "the first DCI is identified by the first RNTI" means that the first DCI is one DCI identified by the first RNTI.

[0560] In one embodiment, the phrase "the first DCI is identified by the first RNTI" means that the first DCI is one PDCCH transmission identified by the first RNTI.

[0561] In one embodiment, the random access process is considered to have been completed successfully. The phrase indicates that this random access process is considered to have completed successfully.

[0562] In one embodiment, the dotted box F5.1A is optional.

[0563] In one embodiment, the dotted box F5.1A is present.

[0564] In one embodiment, the dotted box F5.1A is not present.

[0565] In one embodiment, the dotted box F5.2A is optional.

[0566] In one embodiment, the dotted box F5.2A is present.

[0567] In one embodiment, the dotted box F5.2A is not present.

[0568] In one embodiment, dotted box F5.1A and dotted box F5.2A do not exist simultaneously.

[0569] In one embodiment, dotted box F5.1A and dotted box F5.2A are not present.

[0570] In one embodiment, dotted box F5.1A is present and dotted box F5.2A is not present.

[0571] In one subembodiment of this embodiment, the first time window is active when the first DCI is received.

[0572] As one subembodiment of this embodiment, the first random access process is considered to have completed successfully in response to receiving the first DCI only when the first node U01A is uplink synchronized.

[0573] As one subembodiment of this subembodiment, the phrase "the first node U01A is uplink synchronized" includes one timer having a name including a time alignment timer (timeAlignmentTimer) being running.

[0574] As one subembodiment of this subembodiment, the phrase "the first node U01A is uplink synchronized" includes that the time alignment timer of the TAG to which the first cell belongs is running.

[0575] As one subembodiment of this subembodiment, the phrase "the first node U01A is uplink synchronized" includes that the cg-SDT-TimeAlignmentTimer is running.

[0576] As one subembodiment of this embodiment, the operation of "deeming the first random access process to be completed successfully in response to receiving the first DCI" is independent of whether the first node U01A is uplink synchronized or not.

[0577] As one subembodiment of this embodiment, the first DCI is received on a first search space.

[0578] In one subembodiment of this embodiment, the first search space is a single search space dedicated to the SDT. It is one search space.

[0579] As one subembodiment of this embodiment, one RRC message is used to configure the first search space.

[0580] As one subembodiment of this embodiment, the second message is used to set the first search space.

[0581] As one subembodiment of this embodiment, the third message is used to set the first search space.

[0582] As a subembodiment of this embodiment, the first DCI is not used to schedule either the PDSCH or the PUSCH.

[0583] In one subembodiment of this embodiment, the first DCI is used to indicate a timing advance.

[0584] As one subembodiment of this embodiment, the first DCI includes one Timing Advance Command field, and the one Timing Advance Command field indicates a timing advance.

[0585] As a subembodiment of this embodiment, the first DCI is used to schedule the PDSCH.

[0586] As a subembodiment of this embodiment, the first DCI is used to schedule the DL-SCH.

[0587] As a subembodiment of this subembodiment, in response to receiving the first DCI, the DCI is considered to be toggled.

[0588] As a subembodiment of this embodiment, the first DCI is used to schedule the PUSCH.

[0589] As a subembodiment of this embodiment, the first DCI is used to schedule the UL-SCH.

[0590] As a subembodiment of this subembodiment, in response to receiving the first DCI, the DCI is considered to be toggled.

[0591] As a subembodiment of this subembodiment, the first DCI is used to schedule one UL grant for the new transmission.

[0592] As one subembodiment of this embodiment, the first DCI is used to schedule either a PDSCH or a PUSCH.

[0593] As one subembodiment of this embodiment, the first DCI is used to schedule the PDSCH and the PUSCH.

[0594] In one subembodiment of this embodiment, the first DCI includes at least a timing address. Used to schedule events.

[0595] As one subembodiment of this embodiment, the first DCI is used to determine whether the random access process to which the first preamble belongs has been successfully completed.

[0596] As one subembodiment of this embodiment, when the first DCI is received, the first random access process is considered to be completed successfully.

[0597] As one subembodiment of this embodiment, the first RNTI is the C-RNTI of the first node U01A.

[0598] As one subembodiment of this embodiment, the first RNTI is the C-RNTI of the first node U01A in the first cell.

[0599] As one subembodiment of this embodiment, the first RNTI is a C-RNTI stored in a UE Inactive AS context of the first node U01A.

[0600] In one embodiment, dotted box F5.1A is not present and dotted box F5.2A is present.

[0601] In one subembodiment of this embodiment, the first time window is active when the first DCI is received.

[0602] In one subembodiment of this embodiment, the first time window is active when the first signaling is received.

[0603] As one subembodiment of this embodiment, when the first node U01A is not uplink synchronized, in response to receiving the first signaling, the first random access process is considered to have been completed successfully, and the first DCI is used to schedule the first signaling.

[0604] As one auxiliary embodiment of this subembodiment, the phrase "the first node U01A is not uplink synchronized" includes one timer having a name including a time alignment timer (timeAlignmentTimer) not running.

[0605] As one subembodiment of this subembodiment, the phrase "the first node U01A is not uplink synchronized" includes the time alignment timer (timeAlignmentTimer) of the TAG to which the first cell belongs not being running.

[0606] As one subembodiment of this subembodiment, the phrase "the first node U01A is not uplink synchronized" includes the cg-SDT-TimeAlignmentTimer not running.

[0607] As one subembodiment of this embodiment, the operation of "deeming the first random access process to be completed successfully in response to receiving the first DCI" is independent of whether the first node U01A is uplink synchronized or not.

[0608] As a subembodiment of this embodiment, any RRC Resume Request (RRCResumeRequest) message may be transmitted from the first signal to the first preamble. It is not sent within the time interval by which nulling is received.

[0609] As a subembodiment of this embodiment, no CCCH messages are transmitted within the time interval from when the first preamble is transmitted to when the first signaling is received.

[0610] As one subembodiment of this embodiment, the first preamble is used to indicate a request to perform data transmission in the RRC_INACTIVE state.

[0611] In one embodiment of this embodiment, the first RNTI is one C-RNTI, and the first signaling includes one absolute timing advance MAC CE.

[0612] As an embodiment of this embodiment, the first RNTI is one C-RNTI, and the first signaling includes one MAC RAR.

[0613] In one embodiment of this embodiment, the first RNTI is one C-RNTI, and the first signaling includes one DTCH (Dedicated Traffic Channel) SDU (Service Data Unit).

[0614] As an embodiment of this embodiment, the first RNTI is one RA-RNTI, and the first signaling includes one MAC RAR.

[0615] As one subembodiment of this embodiment, the first signaling is a random access response to the first preamble.

[0616] As a subembodiment of this embodiment, the first signaling is a random access response.

[0617] As one subembodiment of this embodiment, the first signaling is a random access response, the random access response includes a MAC sub-PDU, and the MAC sub-PDU includes a random access preamble identifier of the transmitted first preamble.

[0618] In one subembodiment of this embodiment, the first signaling is one MAC sub-PDU.

[0619] As a subembodiment of this embodiment, the first signaling is a random access response, and the random access response includes a MAC CE.

[0620] As one subembodiment of this embodiment, the meaning of "the first DCI is used to schedule the first signaling" is that the PDSCH scheduled by the first DCI is used to carry at least the first signaling.

[0621] As one subembodiment of this embodiment, the meaning of "the first DCI is used to schedule the first signaling" is that the first DCI indicates scheduling information of a PDSCH that carries at least the first signaling.

[0622] As one subembodiment of this embodiment, "the first DCI is "Used to schedule" means that the first DCI indicates a downlink allocation of at least a first signaling.

[0623] As one subembodiment of this embodiment, the format of the first DCI is used to schedule one DL-SCH.

[0624] As one subembodiment of this embodiment, the format of the first DCI is used to schedule one PDSCH.

[0625] As one subembodiment of this embodiment, the format of the first DCI is used to schedule the PDSCH and the PUSCH.

[0626] As one subembodiment of this embodiment, the format of the first DCI is used to schedule multiple PDSCHs.

[0627] As one subembodiment of this embodiment, the format of the first DCI is DCI Format1_0.

[0628] As one subembodiment of this embodiment, the format of the first DCI is DCI Format1_1.

[0629] As one subembodiment of this embodiment, the format of the first DCI is DCI Format1_x, where x is an integer greater than 1.

[0630] As a subembodiment of this embodiment, the first DCI is used to schedule only the first signaling.

[0631] As one subembodiment of this embodiment, the first DCI is used to schedule the first signaling and at least one MAC SDU.

[0632] As one subembodiment of this embodiment, the first DCI is used to schedule the first signaling and at least one DTCH SDU.

[0633] As one subembodiment of this embodiment, the first signaling is used to determine that the random access process to which the first preamble belongs has been successfully completed.

[0634] As one subembodiment of this embodiment, when the first signaling is received, the first random access process is considered to be completed successfully.

[0635] As one subembodiment of this embodiment, the first signaling includes one MAC field, and the one MAC field indicates a timing advance.

[0636] As one subembodiment of this embodiment, the first signaling includes one Timing Advance Command field, and the one Timing Advance Command field indicates a timing advance.

[0637] In one subembodiment of this embodiment, the MAC field indicating the timing advance in the first signaling occupies 12 bits.

[0638] As a subembodiment of this embodiment, the first signaling indicates only the timing advance.

[0639] As an additional embodiment of this subembodiment, the first signaling includes one MAC CE.

[0640] As one subembodiment of this subembodiment, the first signaling includes one MAC subheader, which includes one eLCID field, and the eLCID field indicates an absolute timing advance MAC CE.

[0641] In one subembodiment of this subembodiment, one eLCID field is set to 252.

[0642] As a subembodiment of this subembodiment, the first signaling includes one absolute timing advance MAC CE.

[0643] As one subembodiment of this embodiment, the first signaling indicates at least a timing advance and an uplink grant.

[0644] As one subembodiment of this subembodiment, the first signaling includes an UL grant field, and the one UL grant field indicates an uplink grant.

[0645] As an additional embodiment of this subembodiment, the first signaling includes one MAC RAR.

[0646] As a subembodiment of this subembodiment, the first signaling includes one fallback RAR.

[0647] As one auxiliary embodiment of this subembodiment, the first signaling includes one MAC subheader, the one MAC subheader includes one RAPID field, and the random access preamble identifier included in the one RAPID field matches the PREAMBLE_INDEX (preamble index) of the first preamble.

[0648] Embodiment 5B 5B illustrates a flowchart of wireless signal transmission according to an embodiment of the present application, as shown in FIG. 5B. It should be noted that the order in this example does not limit the order of signal transmission and implementation in the present application.

[0649] For the first node U01B, in step S5101B, a first sub-message is received, in step S5102B, a second sub-message is received, in step S5103B, a first message is received, the first message is one RRC message, the first message is not transmitted via a dedicated logical channel, the first message includes a first identifier, the first identifier is a first identifier indicating the first node U01B, in step S5104B, after the first message is received, a first signal is transmitted, and in step S5105B, after the first message is received, a first signal is received.

[0650] For the second node N02B, in step S5201B, a first sub-message is sent, in step S5202B, a second sub-message is sent, in step S5203B, a first message is sent, in step S5204B, a first signal is received, and in step S5205B, a first signal is sent.

[0651] In embodiment 5B, the operation of processing the first signal depends on the target information block, at least the former of the first information block and the second identifier is used to determine the target information block, the target information block is dedicated to the first node U01B and the second identifier is used for the first node U01B, the first identifier is different from the second identifier, the first message includes only the former of the first information block and the target information block, the processing includes one of sending and receiving, the first sub-message includes the first identifier and the second sub-message includes the second identifier.

[0652] In one embodiment, the first node U01B is a piece of user equipment.

[0653] In one embodiment, the first node U01B is a base station device.

[0654] In one embodiment, the first node U01B is an intermediate device.

[0655] In one embodiment, the second node N02B is a base station device.

[0656] In one embodiment, the second node N02B is a piece of user equipment.

[0657] In one embodiment, the second node N02B is a relay device.

[0658] In one embodiment, the first node U01B is a part of a user equipment and the second node N02B is a base station device.

[0659] In one embodiment, the first node U01B is part of a user equipment and the second node N02B is part of a user equipment.

[0660] In one embodiment, the first node U01B is a base station device and the second node N02B is a base station device.

[0661] In one embodiment, the dotted box F5.1B is optional.

[0662] In one embodiment, the dotted box F5.1B is present.

[0663] In one embodiment, the dotted box F5.1B is not present.

[0664] In one embodiment, the dotted box F5.2B is optional.

[0665] In one embodiment, the dotted box F5.2B is present.

[0666] In one embodiment, the dotted box F5.2B is not present.

[0667] In one embodiment, dotted box F5.1B and dotted box F5.2B are not present.

[0668] In one embodiment, dotted box F5.1B is present and dotted box F5.2B does not exist.

[0669] In one embodiment, dotted box F5.1B and dotted box F5.2B are not present.

[0670] As an embodiment, this example does not limit whether the sender of the first sub-message is the same as the sender of the second sub-message in this application.

[0671] As an embodiment, this example does not limit whether the sender of the first sub-message is the same as the sender of the first message in this application.

[0672] In one embodiment, the first sub-message is received before the first message is received.

[0673] In one embodiment, the second sub-message is received before the first message is received.

[0674] In one embodiment, the first sub-message is received before the second sub-message.

[0675] In one embodiment, the first sub-message is received after the second sub-message.

[0676] In one embodiment, the first sub-message is an RRC message, and the second sub-message is a MAC signaling.

[0677] In one embodiment, the first sub-message and the second sub-message belong to the same RRC message.

[0678] In one embodiment, the first sub-message and the second sub-message belong to two different RRC messages.

[0679] In one embodiment, the first sub-message is a downlink message.

[0680] In one embodiment, the first sub-message is a sidelink message.

[0681] In one embodiment, the first sub-message assigns a first identifier to the first node U01B.

[0682] In one embodiment, the first sub-message is one MAC CE.

[0683] In one embodiment, the first sub-message includes at least one MAC signaling.

[0684] In one embodiment, the first sub-message is an RRC message.

[0685] In one embodiment, the first sub-message is transmitted over the DCCH.

[0686] In one embodiment, the first sub-message is transmitted over SRB1 (Signaling Radio Bearer 1).

[0687] In one embodiment, the first sub-message is transmitted via SRB3 (Signaling Radio Bearer 3).

[0688] In one embodiment, the first sub-message is one RRCRelease message.

[0689] In one embodiment, the first sub-message is an RRCRelease message that includes a SuspendConfig field, where the suspendConfig field includes a first identifier.

[0690] In one embodiment, the second sub-message assigns a first identifier to the first node U01B.

[0691] In one embodiment, the second sub-message is a downlink message.

[0692] In one embodiment, the second sub-message is a sidelink message.

[0693] In one embodiment, the second sub-message is a piece of MAC signaling.

[0694] In one embodiment, the second sub-message is one MAC signaling, the second sub-message includes one Timing Advance Command field, and the first identifier is set to the value of the one Timing Advance Command field.

[0695] In one embodiment, the second sub-message is one MAC signaling, the second sub-message includes one C-RNTI field, and the first identifier is the value of the one C-RNTI field.

[0696] In one embodiment, one MAC signaling is one MAC CE (Control Element).

[0697] In one embodiment, one MAC signaling is one MAC RAR (Random Access Response).

[0698] In one embodiment, one MAC signaling is one fallback RAR.

[0699] In one embodiment, one MAC signaling is one successful RAR.

[0700] In one embodiment, the second sub-message is an RRC message.

[0701] In one embodiment, the second sub-message is an RRC message, the second sub-message includes a new UE-Identity field, and the first identifier is a value of the new UE-Identity field.

[0702] In one embodiment, the second sub-message is transmitted over the DCCH.

[0703] In one embodiment, the second sub-message is transmitted over SRB1.

[0704] In one embodiment, the second sub-message is transmitted via SRB3.

[0705] In one embodiment, the second sub-message is one RRCRelease message.

[0706] In one embodiment, the second sub-message is a single RRCRelease message that includes a suspendConfig field.

[0707] In one embodiment, the second sub-message is an RRCReconfiguration message.

[0708] In one embodiment, the second sub-message is an RRCReestablishment message.

[0709] In one embodiment, the second sub-message is an RRC Setup message.

[0710] In one embodiment, the first identifier is a full I-RNTI, and the second identifier is a short I-RNTI.

[0711] In one embodiment, the first identifier is a full I-RNTI, and the second identifier is a C-RNTI.

[0712] In one embodiment, the dotted box F5.3B is optional.

[0713] In one embodiment, the dotted box F5.4B is optional.

[0714] In one embodiment, only one of the dotted box F5.3B and the dotted box F5.4B is present.

[0715] Embodiment 6A 6A illustrates a flowchart of wireless signal transmission according to another embodiment of the present application, as shown in FIG. 6A. It should be noted that the order in this example does not limit the order of signal transmission and implementation in the present application.

[0716] For the first node U01A, in step S6101, before the first message is received, the second message is received, and the second message is used to determine to transition to the RRC_INACTIVE state.

[0717] For the second node N02A, in step S6201, a second message is sent.

[0718] In embodiment 6A, the second message includes a first identifier, the first message instructs the first node U01A to perform data transmission in an RRC_INACTIVE state, and the first message is received in the RRC_INACTIVE state.

[0719] In one embodiment, the first message includes a first identifier, the first identifier indicates the first node U01A, the first message is an RRC message, and the first The logical channel used to carry this message is the PCCH.

[0720] In one embodiment, no CCCH (Common Control Channel) SDUs are transmitted in the first random access process.

[0721] In one embodiment, in the first RRC recovery process, no CCCH SDUs are transmitted.

[0722] In one embodiment, one CCCH SDU is transmitted in the first RRC recovery process.

[0723] As a subembodiment of this embodiment, one CCCH SDU includes an RRC Resume Request (RRCResumeRequest) message.

[0724] As a subembodiment of this embodiment, one CCCH SDU includes an RRC Resume Request 1 (RRCResumeRequest1) message.

[0725] In one subembodiment of this embodiment, one CCCH SDU is a MAC SDU corresponding to an RRC Resume Request (RRCResumeRequest) message.

[0726] In one subembodiment of this embodiment, one CCCH SDU is a MAC SDU corresponding to an RRC Resume Request 1 (RRCResumeRequest1) message.

[0727] As one subembodiment of this embodiment, the first DCI is used to schedule one UL grant, and the one UL grant is used to transmit a CCCH SDU.

[0728] In one embodiment, the first node U01A does not transmit any CCCH SDUs within the time interval between when the second message is received and when the first message is received.

[0729] In one embodiment, the second message is received in the RRC_CONNECTED state.

[0730] In one embodiment, the second message is received in the RRC_INACTIVE state.

[0731] In one embodiment, the second message is received on the first cell.

[0732] In one embodiment, the second message is received on a cell other than the first cell.

[0733] In one embodiment, the second message is a single RRCRelease message.

[0734] In one embodiment, the second message is a single RRCRelease message that includes a suspendConfig field.

[0735] In one embodiment, the second message is received before the first message is received. This is the last RRC message received.

[0736] In one embodiment, the second message is the last RRC message received before the first message is received and carried by SRB1.

[0737] In one embodiment, the second message is the last RRCRelease message received before the first message was received.

[0738] In one embodiment, the second message is the last RRCRelease message received before the first message is received and includes a SuspendConfig field.

[0739] In one embodiment, the act of transitioning to the RRC_INACTIVE state includes remaining in the RRC_INACTIVE state.

[0740] In one embodiment, the act of transitioning to the RRC_INACTIVE state includes performing an action to transition to the RRC_INACTIVE state.

[0741] In one embodiment, the second message indicates that the first node U01A should transition to an RRC_INACTIVE state.

[0742] In one embodiment, the suspendConfig field in the second message is used to decide to transition to the RRC_INACTIVE state.

[0743] In one embodiment, the suspendConfig field in the second message indicates a transition to the RRC_INACTIVE state.

[0744] In one embodiment, in response to receiving the second message, the first node U01A transitions to an RRC_INACTIVE state.

[0745] In one embodiment, the first node U01A is always in the RRC_INACTIVE state within the time interval between the act of transitioning to the RRC_INACTIVE state and the reception of the first message.

[0746] In one embodiment, the second message includes one RRC field with a name containing sdt-Config.

[0747] In one embodiment, the second message does not include any RRC fields with names that include sdt-Config.

[0748] In one embodiment, the second message includes a ran-PagingCycle field.

[0749] In one embodiment, the second message includes t380.

[0750] In one embodiment, the second message is used to set the RNA of the first node U01.

[0751] In one embodiment, the second message includes a ran-NotificationAreaInfo field.

[0752] In one embodiment, the ran-NotificationAreaInfo field in the second message is used to configure the RNA of the first node U01A.

[0753] In one embodiment, the second message is used to decide to store the first identifier.

[0754] In one embodiment, in response to the second message being received, the first identifier is stored.

[0755] In one embodiment, the first identifier is a single bit string.

[0756] In one embodiment, the first identifier is a full I-RNTI.

[0757] In one embodiment, the first identifier is a short I-RNTI.

[0758] In one embodiment, the second message indicates the first identifier.

[0759] In one embodiment, one field in the second message includes the first identifier.

[0760] In one embodiment, one RRC field other than the suspendConfig field in the second message includes the first identifier.

[0761] In one embodiment, the suspendConfig field in the second message includes the first identifier.

[0762] In one embodiment, the fullI-RNTI field in the second message includes the first identifier.

[0763] In one embodiment, a short I-RNTI field in the second message includes the first identifier.

[0764] In one embodiment, the fullI-RNTI field in the suspendConfig field in the second message includes the first identifier.

[0765] In one embodiment, a short I-RNTI field in a suspendConfig field in the second message includes the first identifier.

[0766] In one embodiment, the first message includes a second field, which is used to indicate that the data transmission is performed in the RRC_INACTIVE state.

[0767] As a subembodiment of this embodiment, the second field is used to indicate that data transmission is performed via a DRB ((user) Data Radio Bearer) in the RRC_INACTIVE state.

[0768] In one subembodiment of this embodiment, the second field is used to indicate the SDT. Used for.

[0769] As a subembodiment of this embodiment, the second field has a name that includes at least one of sdt, or mt, or ul, or inactive.

[0770] In one subembodiment of this embodiment, the name of the second field is mt-sdt.

[0771] In one subembodiment of this embodiment, the second field has a name that includes the paging cause.

[0772] In one subembodiment of this embodiment, the name of the second field is pagingCause-r18.

[0773] As one subembodiment of this embodiment, the second field is set to a first value to indicate that the data transmission is performed in the RRC_INACTIVE state.

[0774] In one subembodiment of this embodiment, the name of the first value is a string.

[0775] In one subembodiment of this embodiment, the name of the first value is mt-sdt.

[0776] In one subembodiment of this embodiment, the name of the first value is ul-sdt.

[0777] In one subembodiment of this embodiment, the name of the first value is sdt.

[0778] In one subembodiment of this embodiment, the name of the first value is true.

[0779] In one embodiment, the second field is associated with the first field.

[0780] In one embodiment, the second field is relative to the first field.

[0781] In one embodiment, the second field is dependent on the first field.

[0782] In one embodiment, the second field is valid only for the first field.

[0783] In one embodiment, the second field is set to a PagingRecord field that includes the first field in the first message.

[0784] In one embodiment, the second field belongs to a PagingRecord field that includes the first field in the first message.

[0785] In one embodiment, the second field is associated with a PagingRecord field that includes the first field in the first message.

[0786] In one embodiment, the second field is set to an RRC field in the first message that includes the first field and has a name that includes PagingRecord.

[0787] In one embodiment, the second field belongs to an RRC field in the first message that contains the first field and has a name that includes PagingRecord.

[0788] In one embodiment, the second field is associated with an RRC field in the first message that includes the first field and has a name that includes PagingRecord.

[0789] In one embodiment, the first field and the second field belong to the same RRC field.

[0790] As one subembodiment of this embodiment, the first field and the second field are two fields within the same RRC field.

[0791] As a subembodiment of this embodiment, the same RRC field is one PagingRecord field.

[0792] As a subembodiment of this embodiment, the same RRC field is a PagingRecord-v1800 field.

[0793] As a subembodiment of this embodiment, the same RRC field is a PagingRecord-r18 field.

[0794] As one subembodiment of this embodiment, the same RRC field has a name that includes PagingRecord, and the same RRC field has a name that does not include List.

[0795] In one embodiment, the first message includes one PagingRecordList, the one PagingRecordList includes a first field, the first message includes one Paging Record List-v1800 (PagingRecordList-v1800), the one Paging Record List-v1800 (PagingRecordList-v1800) includes a second field, and the entry number of the second field in the one PagingRecordList-v1800 (PagingRecordList-v1800) is the same as the entry number of the first field in the one PagingRecordList.

[0796] In one subembodiment of this embodiment, the first field belongs to one entry in one PagingRecordList.

[0797] As a subembodiment of this embodiment, the first field belongs to one PagingRecord in one PagingRecordList.

[0798] As one subembodiment of this embodiment, the second field belongs to one entry in one PagingRecordList-v1800.

[0799] As one subembodiment of this embodiment, the second field belongs to one paging record-v1800 (PagingRecord-v1800) in one paging record list-v1800 (PagingRecordList-v1800).

[0800] In one embodiment, the first message includes one PagingRecordList, the one PagingRecordList includes a first field, the first message includes one Paging Record List-v1700 (PagingRecordList-v1700), the one Paging Record List-v1700 (PagingRecordList-v1700) includes a second field, and the entry number of the second field in the one PagingRecordList-v1700 (PagingRecordList-v1700) is the same as the entry number of the first field in the one PagingRecordList.

[0801] In one subembodiment of this embodiment, the first field belongs to one entry in one PagingRecordList.

[0802] As a subembodiment of this embodiment, the first field belongs to one PagingRecord in one PagingRecordList.

[0803] As one subembodiment of this embodiment, the second field belongs to one entry in one PagingRecordList-v1700.

[0804] As one subembodiment of this embodiment, the second field belongs to one paging record-v1700 (PagingRecord-v1700) in one paging record list-v1700 (PagingRecordList-v1700).

[0805] In one embodiment, the first message is a paging message.

[0806] In one embodiment, the first message includes one PagingRecord, and the one PagingRecord includes the first identifier.

[0807] In one embodiment, the first message includes one RRC field with a name containing a PagingRecord, and the one RRC field with a name containing a PagingRecord includes a first identifier.

[0808] In one embodiment, the phrase "data transmission is performed in the RRC_INACTIVE state" means that data transmission is performed at least via a DRB in the RRC_INACTIVE state.

[0809] In one embodiment, the phrase "data transmission is performed in the RRC_INACTIVE state" means that data transmission is performed via at least DRB and SRB2 in the RRC_INACTIVE state.

[0810] In one embodiment, the phrase "data transmission is performed in the RRC_INACTIVE state" means performing an SDT procedure.

[0811] In one embodiment, the first RRC recovery process includes performing data transmission in an RRC_INACTIVE state.

[0812] In one embodiment, the first RRC recovery process is to perform data transmission in the RRC_INACTIVE state.

[0813] In one embodiment, the first RRC recovery process is to perform data transmission in the RRC_INACTIVE state.

[0814] In one embodiment, the first message is used to trigger a first RRC recovery process, and the first random access process is initiated in the first RRC recovery process.

[0815] In one embodiment, the first RRC recovery process is used for SDT.

[0816] In one embodiment, the first RRC recovery process is one RRC recovery process for SDT.

[0817] In one embodiment, the first RRC recovery process is an SDT procedure.

[0818] In one embodiment, the SDT is a MT-SDT.

[0819] In one embodiment, the SDT is an MO-SDT.

[0820] In one embodiment, the SDT includes at least one of an MO-SDT or an MT-SDT.

[0821] In one embodiment, the first message is received when the first node U01A is in an RRC_INACTIVE state.

[0822] In one embodiment, the first node U01A is in the RRC_INACTIVE state when the first message is received.

[0823] In one embodiment, either the latter or the former of the third message and the second message is received.

[0824] Embodiment 6B Embodiment 6B illustrates a schematic diagram of at least a portion of a first information block and a target identifier used to determine a target information block according to an embodiment of the present application.

[0825] In embodiment 6B, the first information block and at least a portion of the target identifier are used to determine the target information block, and the second identifier is used to generate the target identifier.

[0826] In one embodiment, the first information block and a portion of the target identifier are used to determine the target information block.

[0827] In one embodiment, the first information block and the target identifier are all used to determine the target information block.

[0828] In one embodiment, at least a portion of the first information block is decoded with a target identifier to determine the target information block.

[0829] In one embodiment, at least a portion of the first information block is processed with a target identifier to obtain a target information block.

[0830] In one embodiment, the second identifier is used to determine the target identifier.

[0831] In one embodiment, the second identifier is used to obtain the target identifier.

[0832] In one embodiment, a portion of the second identifier is used to generate the target identifier.

[0833] In one embodiment, all of the second identifiers are used to generate the target identifier.

[0834] In one embodiment, the target identifier is the second identifier.

[0835] In one embodiment, the target identifier is not the second identifier.

[0836] In one embodiment, the length of the target identifier is not equal to the length of the target information block.

[0837] In one embodiment, the length of the target identifier is equal to the length of the target information block.

[0838] In one embodiment, the target identifier is part of the second identifier.

[0839] In one embodiment, the target identifier consists of all K1 second identifiers, where K1 is a positive integer.

[0840] In one embodiment, the target identifier is made up of a portion of K1 second identifiers, where K1 is a positive integer.

[0841] In one embodiment, K1 is configurable.

[0842] In one embodiment, K1 can be preset.

[0843] In one embodiment, K1 is equal to one.

[0844] In one embodiment, K1 is 2 or greater.

[0845] Embodiment 7A 7A illustrates a flowchart of wireless signal transmission according to another embodiment of the present application, as shown in FIG. 7A. It should be noted that the order in this example does not limit the order of signal transmission and implementation in the present application.

[0846] For the first node U01A, in step S7101, a third message is received, and the third message is used to determine at least one PRACH configuration.

[0847] For the second node N02A, in step S7201, a third message is sent.

[0848] In embodiment 7, the first information block includes a first PRACH in at least one PRACH configuration. Indicate a PRACH configuration, and the first PRACH configuration is used to determine the air interface resource of the first preamble.

[0849] In one embodiment, the third message is received before the first message is received.

[0850] In one embodiment, the third message is a piece of MAC signaling.

[0851] In one embodiment, the third message is one MAC CE.

[0852] In one embodiment, the third message is a MAC subheader.

[0853] In one embodiment, the third message is an RRC message.

[0854] In one embodiment, the third message indicates at least one PRACH configuration.

[0855] In one embodiment, the third message includes at least one PRACH configuration.

[0856] In one embodiment, the third message is the second message.

[0857] As a subembodiment of this embodiment, at least one field in the second message is used to determine at least one PRACH configuration.

[0858] As a subembodiment of this embodiment, the suspendConfig field in the second message is used to determine at least one PRACH configuration.

[0859] In one embodiment, the third message is not the second message.

[0860] As one subembodiment of this embodiment, the third message and the second message belong to the same RRC message.

[0861] As a subembodiment of this embodiment, the third message and the second message do not belong to the same RRC message.

[0862] In one subembodiment of this embodiment, the third message is a public signaling.

[0863] In one subembodiment of this embodiment, the third message is one SIB1 message.

[0864] As a subembodiment of this embodiment, the third message is a System Information message.

[0865] As a subembodiment of this embodiment, the third message is one System Information Block (SIB).

[0866] As one subembodiment of this embodiment, the logical channel used to carry the third message is a BCCH (Broadcast Control Channel).

[0867] As a subembodiment of this embodiment, the third message is a dedicated signaling.

[0868] As one subembodiment of this embodiment, the third message is one RRCReconfiguration message.

[0869] As one subembodiment of this embodiment, the logical channel used to carry the third message is a DCCH (Dedicated Control Channel).

[0870] In one embodiment, the third message includes at least one RACH-ConfigDedicated IE.

[0871] In one embodiment, the third message includes at least one RACH-ConfigGeneric IE.

[0872] In one embodiment, at least one PRACH configuration is configured for SDT.

[0873] In one embodiment, at least one PRACH configuration is configured for CFRA.

[0874] In one embodiment, at least one PRACH configuration is used for conditional CFRA.

[0875] In one embodiment, at least one PRACH configuration is used for CFRA, which is triggered by downlink signaling.

[0876] In one embodiment, the at least one PRACH configuration is used for CFRA, and the CFRA is triggered by downlink signaling, and the downlink signaling includes a first message.

[0877] In one embodiment, the at least one PRACH configuration is used for CFRA, and the CFRA is triggered by downlink signaling, and the downlink signaling includes a second field in the first message.

[0878] In one embodiment, each of the at least one PRACH configuration includes one ra-PreambleIndex field, and one ra-PreambleIndex field indicates one preamble.

[0879] In one embodiment, each of the at least one PRACH configuration includes one ssb field, and one ssb field includes one SSB (Synchronization Bitmap). Signal Block, synchronous signal block).

[0880] In one embodiment, each of the at least one PRACH configuration includes one ssb field, and the one ssb field indicates one SSB (Synchronization Signal Block).

[0881] In one embodiment, the SSB is a synchronization signal block.

[0882] In one embodiment, an SSB is a synchronization signal / physical broadcast channel block.

[0883] In one embodiment, each of the at least one PRACH configuration includes one csi-RS field, and the one csi-RS field indicates one CSI (Channel State Information)-RS (Reference Signal).

[0884] In one embodiment, each of the at least one PRACH configuration includes one of an ssb field or a csi-RS field, where the one ssb field indicates one SSB and the one csi-RS field indicates one CSI-RS.

[0885] In one embodiment, if one PRACH configuration includes one csi-RS field, the PRACH configuration includes one ra-OccasionList field.

[0886] In one embodiment, one field in the first information block indicates a first index.

[0887] In one embodiment, the value of one field in the first information block is set to the first index.

[0888] In one embodiment, the first information block indicates a first index, and the first index indicates a first PRACH configuration within the at least one PRACH configuration.

[0889] As one subembodiment of this embodiment, the first index is an identifier of a first PRACH configuration within the at least one PRACH configuration.

[0890] As one subembodiment of this embodiment, the first index is the order of the first PRACH configuration within the at least one PRACH configuration.

[0891] As one subembodiment of this embodiment, the first index indicates a position of the first PRACH configuration within the at least one PRACH configuration.

[0892] As an embodiment of this embodiment, each of the at least one PRACH configuration is configured with one index, and the first index is the index of the first PRACH configuration.

[0893] In one subembodiment of this embodiment, the first index is a positive integer.

[0894] In one subembodiment of this embodiment, the first index is a non-negative integer.

[0895] In one subembodiment of this embodiment, the maximum value of the first index candidates is predefined.

[0896] As one subembodiment of this embodiment, the maximum value of the first index candidates is configurable.

[0897] In one embodiment, the air interface resource of the first preamble is Determined according to RACH configuration.

[0898] In one embodiment, the air interface resources of the first preamble are dictated by the first PRACH configuration.

[0899] In one embodiment, the third message is received before the second message.

[0900] In one embodiment, the third message is received after the second message.

[0901] In one embodiment, both the third message and the second message are received.

[0902] In one embodiment, only the former of the third message and the second message is received.

[0903] Embodiment 7B Embodiment 7B illustrates a schematic diagram of the second identifier being a bit string according to one embodiment of the present application.

[0904] In embodiment 7B, the first information block includes at least one bit, and the second identifier is a bit string.

[0905] In one embodiment, the first information block comprises at least one bit string.

[0906] In one embodiment, each field in the first information block comprises at least one bit.

[0907] In one embodiment, each field in the first information block is set to one bit string.

[0908] In one embodiment, the first information block is identified by a target identifier.

[0909] In one embodiment, the first information block is scrambled with a target identifier.

[0910] In one embodiment, the first information block is encrypted with a target identifier.

[0911] In one embodiment, the first information block is encoded with a target identifier.

[0912] In one embodiment, at least some of the bits in the first information block and the target identifier are used to determine the target information block, and the second identifier is used to generate the target identifier.

[0913] In one embodiment, at least some of the bits in the first information block and the target identifier are input into a function to obtain the target information block.

[0914] In one embodiment, "at least a portion of the bits in the target information block" refers to all of the bits in the target information block.

[0915] In one embodiment, "at least a portion of the bits in the target information block" refers to a portion of the bits in the target information block.

[0916] In one embodiment, the length of the target identifier is not equal to the length of the target information block.

[0917] In one embodiment, the length of the target identifier is equal to the length of the target information block.

[0918] In one embodiment, the target identifier is the second identifier.

[0919] In one embodiment, the target identifier is a portion of the bits in the second identifier.

[0920] In one embodiment, the target identifier is not the second identifier, but rather the second identifier is used to generate the target identifier.

[0921] In one embodiment, the target identifier includes K1 second identifiers, where K1 is a positive integer.

[0922] In one embodiment, the target identifier consists of all bits in K1 second identifiers, where K1 is a positive integer.

[0923] In one embodiment, the target identifier consists of a portion of the bits in K1 second identifiers, where K1 is a positive integer.

[0924] In one embodiment, K1 is equal to one.

[0925] In one embodiment, K1 is 2 or greater.

[0926] In one embodiment, the length of the second identifier is constant.

[0927] In one embodiment, the length of the second identifier is variable.

[0928] In one embodiment, the number of bits in the second identifier is not equal to the number of bits in the first identifier.

[0929] In one embodiment, the number of bits in the second identifier is equal to the number of bits in the first identifier.

[0930] Embodiment 8A Embodiment 8A illustrates a schematic diagram of the interpretation of the first information block depending on the second identifier according to one embodiment of the present application.

[0931] In embodiment 8A, the interpretation of the first information block depends on the second identifier, the second identifier is used for the first node, and the first identifier is different from the second identifier.

[0932] In one embodiment, the first message does not include the second identifier.

[0933] In one embodiment, the first message includes a first identifier, the first identifier indicates a first node, the first message is an RRC message, and the logical channel used to carry the first message is a PCCH.

[0934] In one embodiment, the phrase "the interpretation of the first information block depends on the second identifier" means that the interpretation of the first information block depends only on the second identifier.

[0935] In one embodiment, the phrase "the interpretation of the first information block depends on the second identifier" means that the interpretation of the first information block depends on at least the second identifier.

[0936] In one embodiment, the phrase "the interpretation of the first information block depends on the second identifier" means that the first information block includes multiple fields, and the interpretation of each of the multiple fields depends on the second identifier.

[0937] In one embodiment, the phrase "the interpretation of the first information block depends on the second identifier" means that the first information block includes multiple fields and the interpretation of only some of the multiple fields depends on the second identifier.

[0938] In one embodiment, the phrase "the interpretation of the first information block depends on the second identifier" means that the first information block contains only one field, and the interpretation of the only one field depends on the second identifier.

[0939] In one embodiment, the phrase "the interpretation of the first information block depends on the second identifier" means that the truth value of the first information block depends on the second identifier.

[0940] In one embodiment, the phrase "the interpretation of the first information block depends on the second identifier" means that the meaning of the first information block depends on the second identifier.

[0941] In one embodiment, the phrase "the interpretation of the first information block depends on the second identifier" means that the information indicated by the first information block depends on the second identifier.

[0942] In one embodiment, the meaning of interpretation includes decoding.

[0943] In one embodiment, the meaning of interpretation includes decoding.

[0944] In one embodiment, the meaning of interpretation includes decoding.

[0945] In one embodiment, the meaning of the interpretation includes a judgment.

[0946] In one embodiment, the meaning of the interpretation includes recovery.

[0947] In one embodiment, the meaning of interpretation includes detection.

[0948] In one embodiment, the first information block is identified by a target bit sequence.

[0949] In one embodiment, the first information block is scrambled with a target bit sequence.

[0950] In one embodiment, the first information block is encrypted with a target bit string.

[0951] In one embodiment, the first information block is encoded by a target bit sequence. .

[0952] In one embodiment, at least a portion of the bits in the first information block and the target bit string are used to determine the target information block.

[0953] In one embodiment, at least some of the bits in the first information block and the second identifier are processed to obtain the target information block.

[0954] In one embodiment, the first information block and at least a portion of the target bit string are input to a function to obtain the target information block.

[0955] In one embodiment, the first information block and at least some of the bits in the target bit sequence are subjected to a first operation to obtain the target information block, and the air interface resources of the first preamble depend on the target information block.

[0956] In one embodiment, the first operation is performed by a first node.

[0957] In one embodiment, the target information block and at least some of the bits in the target bit string are subjected to a second operation to obtain the first information block, the second operation being the inverse of the first operation.

[0958] In one embodiment, the second operation is performed by a second node.

[0959] In one embodiment, "at least a portion of the bits in the target information block" refers to all of the bits in the target information block.

[0960] In one embodiment, "at least a portion of the bits in the target information block" refers to a portion of the bits in the target information block.

[0961] In one embodiment, the first operation includes a linear operation.

[0962] In one embodiment, the first operation includes a non-linear operation.

[0963] In one embodiment, the first operation includes a logical operation.

[0964] In one embodiment, the first operation comprises a Boolean operation.

[0965] In one embodiment, the first operation includes a bit operation.

[0966] In one embodiment, the first operation comprises an XOR.

[0967] In one embodiment, the first operation includes AND-OR.

[0968] In one embodiment, the first operation includes XNOR.

[0969] In one embodiment, the first operation includes AND.

[0970] In one embodiment, the first operation includes an OR.

[0971] In one embodiment, the first operation comprises NOT.

[0972] In one embodiment, the first operation comprises an AND-NOT.

[0973] In one embodiment, the first operation includes a CRC.

[0974] In one embodiment, the first operation is a linear operation.

[0975] In one embodiment, the first operation is a non-linear operation.

[0976] In one embodiment, the first operation is a logical operation.

[0977] In one embodiment, the first operation is a Boolean operation.

[0978] In one embodiment, the first operation is a bitwise operation.

[0979] In one embodiment, the first operation is an XOR.

[0980] In one embodiment, the first operation is AND-OR.

[0981] In one embodiment, the first operation is XNOR.

[0982] In one embodiment, the first operation is an AND.

[0983] In one embodiment, the first operation is an OR.

[0984] In one embodiment, the first operation is NOT.

[0985] In one embodiment, the first operation is AND-NOT.

[0986] In one embodiment, the first operation is a CRC.

[0987] In one embodiment, the length of the target bit string is not equal to the length of the target information block.

[0988] In one embodiment, the length of the target bit string is equal to the length of the target information block.

[0989] In one embodiment, the target bit string is a second identifier.

[0990] In one embodiment, the target bit string is a portion of the bits in the second identifier.

[0991] In one embodiment, the target bit string is not the second identifier, but rather the second identifier is used to generate the target bit string.

[0992] In one embodiment, the target bit string includes K1 second identifiers, where K1 is a positive integer.

[0993] In one embodiment, the target bit string consists of all bits in K1 second identifiers, where K1 is a positive integer.

[0994] In one embodiment, the target bit string comprises a portion of the bits in K1 second identifiers, where K1 is a positive integer.

[0995] In one embodiment, K1 is equal to one.

[0996] In one embodiment, K1 is 2 or greater.

[0997] In one embodiment, the second identifier is preset.

[0998] In one embodiment, the second identifier is assigned by the second node.

[0999] In one embodiment, the second identifier is set by the second message in this application.

[1000] In one embodiment, the second identifier is stored by the first node.

[1001] In one embodiment, the second identifier is calculated by the first node.

[1002] In one embodiment, the length of the second identifier is constant.

[1003] In one embodiment, the length of the second identifier is variable.

[1004] In one embodiment, the second identifier is a bit string.

[1005] In one embodiment, the second identifier is assigned to the first node.

[1006] In one embodiment, the second identifier is configured for the first node by an RRC message.

[1007] In one embodiment, the second identifier indicates a second node.

[1008] In one embodiment, the second identifier indicates a first node in a first cell.

[1009] In one embodiment, the second identifier indicates a first node within at least one cell.

[1010] In one embodiment, the second identifier indicates a first node within a specified cell.

[1011] In one embodiment, the second identifier points to the first node within the RNA of the first node.

[1012] In one embodiment, the second identifier is a short I-RNTI of one of the first nodes.

[1013] In one embodiment, the second identifier is a short I-RNTI stored by the first node.

[1014] In one embodiment, the second identifier is a C-RNTI of one of the first nodes.

[1015] In one embodiment, the second identifier is a C-RNTI stored by the first node. be.

[1016] In one embodiment, the second identifier is the C-RNTI of the first node in the first cell.

[1017] In one embodiment, the second identifier is not the first identifier.

[1018] In one embodiment, the name of the second identifier is different from the name of the first identifier.

[1019] In one embodiment, the number of bits in the second identifier is not equal to the number of bits in the first identifier.

[1020] In one embodiment, the number of bits in the second identifier is equal to the number of bits in the first identifier.

[1021] In one embodiment, it is assumed that the first information block is (101110)(0)(011111)(1111), the target bit string is (001010)(1)(011011)(0010), the target information block obtained after all bits in the first information block and the target bit string are subjected to the first operation is (100100)(1)(000100)(1101), the first information block includes a first target field (101110), a second target field (0), a third target field (011111), and a fourth target field (1111), the first operation is XOR, the target bit string is a portion of the bits in the second identifier, and the second identifier is a short I-RNTI of one of the first nodes.

[1022] In one embodiment, it is assumed that the first information block is (101110)(011111)(1111)0, the target bit string is (001010)(011011)(0010), the target information block obtained after a first operation is performed on a portion of the bits in the first information block (101110)(011111)(1111) and the target bit string is (100100)(000100)(1101)0, the first information block includes a first target field (101110), a second target field (0), a third target field (011111), and a fourth target field (1111), the first operation is XOR, the target bit string is a second identifier, and the second identifier is a C-RNTI of one of the first nodes.

[1023] Embodiment 8B Embodiment 8B illustrates a schematic diagram of the first message instructing the first node to perform data transmission in an RRC_INACTIVE state according to one embodiment of the present application.

[1024] In embodiment 8B, the first sub-message is used to decide to transition to the RRC_INACTIVE state, the logical channel used to carry the first message is the PCCH, and the first message instructs the first node to implement data transmission in the RRC_INACTIVE state.

[1025] In one embodiment, the first sub-message is used to determine to store the first identifier.

[1026] In one embodiment, in response to receiving the first sub-message, the first identifier is stored.

[1027] In one embodiment, the first sub-message is received in the RRC_CONNECTED state.

[1028] In one embodiment, the first sub-message is received in the RRC_INACTIVE state.

[1029] In one embodiment, the first sub-message is received on a first cell.

[1030] In one embodiment, the first sub-message is received on a cell other than the first cell.

[1031] In one embodiment, the first sub-message is an RRC message.

[1032] In one embodiment, the first sub-message is one RRCRelease message.

[1033] In one embodiment, the first sub-message is a single RRCRelease message that includes a suspendConfig field.

[1034] In one embodiment, the first sub-message is the last RRCRelease message received before the first message is received.

[1035] In one embodiment, the first sub-message is the last RRCRelease message received before the first message is received and includes a suspendConfig field.

[1036] In one embodiment, the first sub-message includes one RRC field with a name containing sdt-Config.

[1037] In one embodiment, the first sub-message does not include any RRC fields with names containing sdt-Config.

[1038] In one embodiment, the first sub-message includes a ran-PagingCycle field.

[1039] In one embodiment, the first sub-message includes t380.

[1040] In one embodiment, the first sub-message is used to set the RNA of the first node U01.

[1041] In one embodiment, the first sub-message includes a ran-NotificationAreaInfo field.

[1042] In one embodiment, the ran-NotificationAreaInfo field in the first sub-message is used to configure the RNA of the first node U01.

[1043] In one embodiment, the first sub-message indicates a first identifier.

[1044] In one embodiment, one field in the first sub-message includes a first identifier.

[1045] In one embodiment, one RRC field other than the suspendConfig field in the first sub-message includes the first identifier.

[1046] In one embodiment, the suspendConfig field in the first sub-message includes the first identifier.

[1047] In one embodiment, the fullI-RNTI field in the first sub-message includes the first identifier.

[1048] In one embodiment, a short I-RNTI field in the first sub-message includes the first identifier.

[1049] In one embodiment, the fullI-RNTI field in the suspendConfig field in the first message includes the first identifier.

[1050] In one embodiment, a short I-RNTI field in the suspendConfig field in the first sub-message includes the first identifier.

[1051] In one embodiment, the first identifier is a single bit string.

[1052] In one embodiment, the first identifier is a full I-RNTI.

[1053] In one embodiment, the first identifier is a short I-RNTI.

[1054] In one embodiment, the act of transitioning to the RRC_INACTIVE state includes remaining in the RRC_INACTIVE state.

[1055] In one embodiment, the "operation of transitioning to the RRC_INACTIVE state" includes performing an action to transition to the RRC_INACTIVE state.

[1056] In one embodiment, the first sub-message indicates that the first node U01 transitions to an RRC_INACTIVE state.

[1057] In one embodiment, the suspendConfig field in the first sub-message is used to decide to transition to the RRC_INACTIVE state.

[1058] In one embodiment, the suspendConfig field in the first sub-message indicates a transition to the RRC_INACTIVE state.

[1059] In one embodiment, in response to receiving the first sub-message, the first node transitions to an RRC_INACTIVE state.

[1060] In one embodiment, the first node U01 transitions to the RRC_INACTIVE state. It is always in RRC_INACTIVE state within the time interval from operation until the first message is received.

[1061] In one embodiment, the first message is a paging message.

[1062] In one embodiment, the first message includes at least one PagingRecord field.

[1063] In one embodiment, the first message includes at least one field with a name that includes a PagingRecord.

[1064] In one embodiment, the first message includes at least one PagingRecordList.

[1065] In one embodiment, the first message includes at least one field with a name that includes PagingRecordList.

[1066] In one embodiment, the first message includes one PagingRecord field, and the one PagingRecord field includes the first identifier.

[1067] In one embodiment, the first message includes one RRC field with a name containing a PagingRecord, and the one RRC field with a name containing a PagingRecord includes a first identifier.

[1068] In one embodiment, the phrase "performing data transmission in the RRC_INACTIVE state" means performing data transmission in the RRC_INACTIVE state via at least a DRB ((User) Data Radio Bearer).

[1069] In one embodiment, the phrase "performing data transmission in the RRC_INACTIVE state" means performing data transmission in the RRC_INACTIVE state via at least the DRB and SRB2 (Signaling Radio Bearer 2).

[1070] In one embodiment, the phrase "performing data transmission in RRC_INACTIVE state" means performing an SDT procedure.

[1071] In one embodiment, the first message includes a first field and a second field, and the first field and the second field indicate that the first node performs data transmission in an RRC_INACTIVE state.

[1072] In one embodiment, the first message includes a first field and a second field, and the first field and the second field are used together to indicate that the first node performs data transmission in an RRC_INACTIVE state.

[1073] In one embodiment, the first message includes a first field and a second field, and the value of the first field and the value of the second field indicate that the first node performs data transmission in an RRC_INACTIVE state.

[1074] In one embodiment, the first message includes a first field and a second field, where the first field includes a first identifier and the second field is used to indicate that the data transmission is performed in the RRC_INACTIVE state.

[1075] As one subembodiment of this embodiment, the first message includes one PagingRecord field, which includes a first field, and the first field includes a first identifier.

[1076] As one subembodiment of this embodiment, the first message includes one RRC field having a name containing a PagingRecord, and the one RRC field having a name containing a PagingRecord includes a first field, and the first field includes a first identifier.

[1077] In one embodiment, the first message includes a first field, and the first field includes a first identifier.

[1078] In one subembodiment of this embodiment, the first field is a ue-Identity field.

[1079] As a subembodiment of this embodiment, the first field is a PagingUE-Identity field.

[1080] As a subembodiment of this embodiment, the first field is a full I-RNTI field.

[1081] As a subembodiment of this embodiment, the first field is one I-RNTI-Value field.

[1082] In one embodiment, the first message includes a second field, which is used to indicate that the data transmission is performed in the RRC_INACTIVE state.

[1083] In one subembodiment of this embodiment, the second field is used to indicate the SDT.

[1084] As one subembodiment of this embodiment, the second field has a name that includes at least one of sdt, or mt, or ul, or inactive.

[1085] In one subembodiment of this embodiment, the name of the second field is mt-sdt.

[1086] In one subembodiment of this embodiment, the second field has a name that includes the paging cause.

[1087] In one subembodiment of this embodiment, the name of the second field is pagingCause-r18.

[1088] As one subembodiment of this embodiment, the second field is set to a first value to indicate that the data transmission is performed in the RRC_INACTIVE state.

[1089] In one subembodiment of this embodiment, the name of the first value is a string.

[1090] In one subembodiment of this embodiment, the name of the first value is mt-sdt.

[1091] In one subembodiment of this embodiment, the name of the first value is ul-sdt.

[1092] In one subembodiment of this embodiment, the name of the first value is sdt.

[1093] In one subembodiment of this embodiment, the name of the first value is true.

[1094] In one embodiment, the second field is associated with the first field.

[1095] In one embodiment, the second field is for the first node.

[1096] In one embodiment, the second field is dependent on the first field.

[1097] In one embodiment, the second field is valid only for the first field.

[1098] In one embodiment, the second field is set to a PagingRecord field that includes the first field in the first message.

[1099] In one embodiment, the second field belongs to a PagingRecord field that includes the first field in the first message.

[1100] In one embodiment, the second field is associated with a PagingRecord field that includes the first field in the first message.

[1101] In one embodiment, the second field is set to an RRC field in the first message that includes the first field and has a name that includes PagingRecord.

[1102] In one embodiment, the second field belongs to an RRC field in the first message that contains the first field and has a name that includes PagingRecord.

[1103] In one embodiment, the second field is associated with an RRC field in the first message that includes the first field and has a name that includes PagingRecord.

[1104] In one embodiment, the first field and the second field belong to the same RRC field.

[1105] As one subembodiment of this embodiment, the first field and the second field are two fields within the same RRC field.

[1106] As a subembodiment of this embodiment, the same RRC field is one PagingRecord field.

[1107] In one embodiment of this embodiment, the same RRC field is one PagingRecord-v1800 field.

[1108] In one subembodiment of this embodiment, the same RRC field may be used for one paging This is the Record-r18 (PagingRecord-r18) field.

[1109] As one subembodiment of this embodiment, the same RRC field has a name that includes PagingRecord, and the same RRC field has a name that does not include List.

[1110] In one embodiment, the first message includes one PagingRecordList, the one PagingRecordList includes a first field, the first message includes one Paging Record List-v1800 (PagingRecordList-v1800), the one Paging Record List-v1800 (PagingRecordList-v1800) includes a second field, and the entry number of the second field in the one PagingRecordList-v1800 (PagingRecordList-v1800) is the same as the entry number of the first field in the one PagingRecordList.

[1111] In one subembodiment of this embodiment, the first field belongs to one entry in one PagingRecordList.

[1112] As a subembodiment of this embodiment, the first field belongs to one PagingRecord in one PagingRecordList.

[1113] As one subembodiment of this embodiment, the second field belongs to one entry in one PagingRecordList-v1800.

[1114] As one subembodiment of this embodiment, the second field belongs to one paging record-v1800 (PagingRecord-v1800) in one paging record list-v1800 (PagingRecordList-v1800).

[1115] In one embodiment, the first message includes one PagingRecordList, the one PagingRecordList includes a first field, the first message includes one Paging Record List-v1700 (PagingRecordList-v1700), the one Paging Record List-v1700 (PagingRecordList-v1700) includes a second field, and the entry number of the second field in the one PagingRecordList-v1700 (PagingRecordList-v1700) is the same as the entry number of the first field in the one PagingRecordList.

[1116] In one subembodiment of this embodiment, the first field belongs to one entry in one PagingRecordList.

[1117] As a subembodiment of this embodiment, the first field belongs to one PagingRecord in one PagingRecordList.

[1118] As one subembodiment of this embodiment, the second field belongs to one entry in one PagingRecordList-v1700.

[1119] As a subembodiment of this embodiment, the second field is one Paging Record List-v1700 in one PagingRecordList-v1700. Belongs to PagingRecord-v1700.

[1120] Embodiment 9A Embodiment 9A, as shown in FIG. 9A, illustrates a schematic diagram of the air interface resource of the first preamble depending on the first information block according to one embodiment of the present application.

[1121] In embodiment 9A, the first information block indicates at least one of a preamble sequence used by the first preamble, an uplink carrier occupied by the first preamble, an RS resource associated with the first preamble, or a PRACH mask of the first preamble.

[1122] In one embodiment, the first information block includes a first target field, which indicates a preamble sequence used by the first preamble.

[1123] As a subembodiment of this embodiment, the first target field indicates the index of the first preamble.

[1124] As one subembodiment of this embodiment, the first target field indicates the index of the preamble sequence used by the first preamble.

[1125] In one subembodiment of this embodiment, the value of the first target field is a string.

[1126] In one subembodiment of this embodiment, the value of the first target field is a single bit string.

[1127] In one subembodiment of this embodiment, the first target field includes at least one bit.

[1128] In one subembodiment of this embodiment, the length of the first target field is 6 bits.

[1129] In one subembodiment of this embodiment, the length of the first target field is 5 bits.

[1130] In one subembodiment of this embodiment, the first target field is a Random Access Preamble index field.

[1131] As a subembodiment of this embodiment, the first target field is an ra-PreambleIndex field.

[1132] As one subembodiment of this embodiment, the interpretation of the first target field refers to the Random Access Preamble Index field of DCI Format 1_0 in Section 7.3.1.2.1 of 3GPP TS38.212.

[1133] In one embodiment, the first information block includes a second target field, and the second The target field of indicates the uplink carrier occupied by the first preamble.

[1134] As one subembodiment of this embodiment, the candidates for the second target field include UL and SUL (Supplementary Uplink).

[1135] As one subembodiment of this embodiment, the candidates for the second target field include NUL (Normal Uplink) and SUL.

[1136] As one subembodiment of this embodiment, the uplink carrier candidates indicated by the second target field include NUL and SUL.

[1137] In one subembodiment of this embodiment, the second target field indicates one of NUL and SUL.

[1138] In one subembodiment of this embodiment, the length of the second target field is 1 bit.

[1139] In one subembodiment of this embodiment, the value of the second target field is a string.

[1140] In one subembodiment of this embodiment, the value of the second target field is a single bit string.

[1141] In one subembodiment of this embodiment, the value of the second target field is a Boolean value.

[1142] In one subembodiment of this embodiment, the second target field is a single UL / SUL indicator field.

[1143] As one subembodiment of this embodiment, the interpretation of the second target field refers to the UL / SUL indicator field of DCI Format1_0 in Section 7.3.1.2.1 of 3GPP TS38.212.

[1144] In one embodiment, the uplink carrier occupied by the first preamble is the default.

[1145] As one subembodiment of this embodiment, the first information block does not include a field for indicating the uplink carrier occupied by the first preamble.

[1146] As a subembodiment of this embodiment, the uplink carrier occupied by the first preamble is NUL.

[1147] As one subembodiment of this embodiment, the uplink carrier occupied by the first preamble is the SUL.

[1148] In one embodiment, the first information block includes a third target field, where the third target field indicates an RS resource associated with the first preamble.

[1149] In one subembodiment of this embodiment, the value of the third target field is a string.

[1150] In one subembodiment of this embodiment, the value of the third target field is a single bit string.

[1151] In one subembodiment of this embodiment, the third target field includes at least one bit.

[1152] In one subembodiment of this embodiment, the length of the third target field is 6 bits.

[1153] In one subembodiment of this embodiment, the third target field is 5 bits long.

[1154] As one subembodiment of this embodiment, the third target field is one ssb field, and the third target field indicates an SSB-Index.

[1155] As one subembodiment of this embodiment, the third target field is one csi-RS field, and the third target field indicates a CSI-RS-index.

[1156] In one subembodiment of this embodiment, the third target field is an SS / PBCH index field.

[1157] As one subembodiment of this embodiment, the interpretation of the third target field refers to the SS / PBCH field of DCI Format1_0 in Section 7.3.1.2.1 of 3GPP TS38.212.

[1158] In one embodiment, the first information block includes a fourth target field, which indicates a PRACH mask of the first preamble.

[1159] As a subembodiment of this embodiment, the fourth target field includes the index of the PRACH mask used by the first preamble.

[1160] In one subembodiment of this embodiment, the fourth target field includes an index in a table.

[1161] As a subembodiment of this embodiment, the fourth target field includes an index in Table 7.4.1 in 3GPP TS38.321.

[1162] In one subembodiment of this embodiment, the value of the fourth target field is a string.

[1163] In one subembodiment of this embodiment, the value of the fourth target field is a single bit string.

[1164] In one subembodiment of this embodiment, the fourth target field comprises at least Contains one bit.

[1165] In one subembodiment of the embodiment, the fourth target field is 5 bits in length.

[1166] In one subembodiment of this embodiment, the fourth target field is 4 bits in length.

[1167] In one subembodiment of this embodiment, the fourth target field is a PRACH Mask index field.

[1168] As one subembodiment of this embodiment, the interpretation of the fourth target field refers to the PRACH Mask index field of DCI Format1_0 in Section 7.3.1.2.1 of 3GPP TS38.212.

[1169] In one embodiment, the first information block includes at least one of a first target field, a second target field, a third target field, or a fourth target field.

[1170] Embodiment 9B Embodiment 9B illustrates a schematic diagram of the processing of the first signal depending on the target information block according to one embodiment of the present application, as shown in FIG. 9B.

[1171] In embodiment 9B, the meaning of the phrase "the operation of processing the first signal depends on the target information block" includes that the target information block indicates the air interface resources used for the first signal, and the air interface resources include at least one of code domain resources, or time domain resources, or frequency domain resources.

[1172] In one embodiment, the target information block indicates air interface resources dedicated to the first node, and the air interface resources dedicated to the first node are used to process the first signal.

[1173] In one embodiment, the air interface resources dedicated to the first node indicated by the target information block are one-shot.

[1174] In one embodiment, the air interface resources dedicated to the first node indicated by the target information block are not one-shot.

[1175] In one embodiment, the target information block indicates configuration information of the air interface resource used for the first signal.

[1176] In one embodiment, the target information block explicitly indicates the air interface resources to be used for the first signal.

[1177] In one embodiment, the target information block implicitly indicates the air interface resources to be used for the first signal.

[1178] In one embodiment, the target information block indicates an index of the air interface resource to be used for the first signal.

[1179] In one embodiment, the target information block indicates the index of the air interface resource used for the first signal.

[1180] In one embodiment, the target information block indicates an air interface resource to be used for the first signal from among the at least one air interface resource.

[1181] In one embodiment, the air interface resources of the first signal include a CORESET (Control Resource Set) used for the first signal.

[1182] In one embodiment, the air interface resources of the first signal include a Transmission Configuration Indicator (TCI) used for the first signal.

[1183] In one embodiment, the air interface resources of the first signal include a QCL relationship used for the first signal.

[1184] In one embodiment, the air interface resources for the first signal include the power used for the first signal.

[1185] In one embodiment, the air interface resources of the first signal include a search space used for the first signal.

[1186] In one embodiment, the air interface resource includes at least one of a code domain resource, or a time domain resource, or a frequency domain resource, or a power resource, or a spatial domain resource.

[1187] In one embodiment, the code domain resource of the first signal includes one sequence used by the first signal.

[1188] In one embodiment, the code domain resource of the first signal includes one PRACH sequence used by the first signal.

[1189] In one embodiment, the code domain resource of the first signal includes one ZC sequence used by the first signal.

[1190] In one embodiment, the code domain resource of the first signal includes one NZC sequence used by the first signal.

[1191] In one embodiment, the code domain resource of the first signal includes one root sequence used by the first signal.

[1192] In one embodiment, the code domain resource of the first signal comprises one bit sequence used by the first signal.

[1193] In one embodiment, the time domain resource of the first signal comprises a time slot occupied by the first signal.

[1194] In one embodiment, the time domain resource of the first signal is occupied by the first signal. Includes subframes in which

[1195] In one embodiment, the time domain resource of the first signal comprises the symbols occupied by the first signal.

[1196] In one embodiment, the time domain resource of the first signal comprises a system frame occupied by the first signal.

[1197] In one embodiment, the frequency domain resource of the first signal includes a bandwidth part (BWP) occupied by the first signal.

[1198] In one embodiment, the frequency domain resource of the first signal includes a carrier occupied by the first signal.

[1199] In one embodiment, the frequency domain resource of the first signal includes a frequency occupied by the first signal.

[1200] In one embodiment, the frequency domain resource of the first signal includes a subcarrier spacing used by the first signal.

[1201] In one embodiment, the spatial domain resource of the first signal includes a Quasi co-location (QCL) relationship of the first signal.

[1202] In one embodiment, the spatial domain resource of the first signal includes a TRP (Transmit Receiving Point) used for the first signal.

[1203] In one embodiment, the spatial domain resource for the first signal includes a beam used for the first signal.

[1204] In one embodiment, the spatial domain resource of the first signal includes an SSB used for the first signal.

[1205] In one embodiment, SSB refers to Synchronization Signal Block.

[1206] In one embodiment, SSB refers to a Synchronization Signal (SS) / Physical broadcast channel (PBCH) block.

[1207] In one embodiment, the air interface resources include physical layer resources.

[1208] In one embodiment, air interface resources refer to physical layer resources.

[1209] In one embodiment, the air interface resources are wireless resources of the Uu port.

[1210] In one embodiment, the air interface resources include resources occupied by one physical layer signal.

[1211] In one embodiment, the air interface resource is provided by one physical layer channel. This includes resources occupied by

[1212] In one embodiment, the air interface resource includes a PUSCH resource, and the first signal is one PUSCH transmission.

[1213] In one embodiment, the air interface resource includes a PUCCH resource, and the first signal is one PUCCH signal.

[1214] In one embodiment, the air interface resource includes a PDCCH resource, and the first signal is one PDCCH signal.

[1215] In one embodiment, the air interface resource includes a PRACH resource, and the first signal is one PRACH signal.

[1216] In one embodiment, the air interface resource includes SSBs, and the first signal is one SSB.

[1217] In one embodiment, the air interface resources include CSI-RS (Channel State Information Reference Signal) resources, and the first signal is one CSI-RS.

[1218] In one embodiment, the air interface resource includes a sounding reference signal (SRS) resource, and the first signal is one SRS.

[1219] Embodiment 10A Embodiment 10A illustrates a schematic diagram of a first RNTI and a first signaling according to one embodiment of the present application, as shown in FIG. 10A.

[1220] In embodiment 10A, the first RNTI is one C-RNTI, and the first signaling includes one absolute timing advance MAC CE.

[1221] In one embodiment, the first RNTI is the C-RNTI of the first node.

[1222] In one embodiment, the first RNTI is the C-RNTI of the first node in the first cell.

[1223] In one embodiment, the first RNTI is the C-RNTI in the cell from which the first node receives the last RRCRelease message before transitioning to the RRC_INACTIVE state.

[1224] In one embodiment, the first RNTI is the C-RNTI of the first node in the cell in which the second message is received.

[1225] In one embodiment, the first RNTI is a C-RNTI stored in a UE Inactive AS context of the first node.

[1226] In one embodiment, the first signaling includes one absolute timing advance MAC CE.

[1227] In one embodiment, the first signaling comprises one MAC sub-PDU. PDU), one MAC sub-PDU contains one absolute timing advance MAC CE and one MAC subheader, the MAC subheader contains one extended Logical Channel ID (eLCID) field, the eLCID field is set to 252.

[1228] Embodiment 10B Embodiment 10B, as shown in FIG. 10B, illustrates a schematic diagram of the first signal being a preamble according to one embodiment of the present application.

[1229] In embodiment 10B, the first signal is a preamble.

[1230] In one embodiment, the target information block indicates at least one of the preamble sequence used by the first signal, or the uplink carrier occupied by the first signal, or the RS resources associated with the first signal, or the PRACH mask of the first signal.

[1231] In one embodiment, the target information block indicates the preamble sequence used by the first signal.

[1232] As a subembodiment of this embodiment, at least one bit in the target information block indicates an index of a preamble sequence used by the first signal.

[1233] As one subembodiment of this embodiment, the target information block includes a first target field, which indicates a preamble sequence used by the first signal.

[1234] In one subembodiment of this embodiment, the value of the first target field is a string.

[1235] In one subembodiment of this embodiment, the value of the first target field is a single bit string.

[1236] In one subembodiment of this embodiment, the first target field includes at least one bit.

[1237] In one subembodiment of this embodiment, the length of the first target field is 6 bits.

[1238] In one subembodiment of this embodiment, the length of the first target field is 5 bits.

[1239] In one subembodiment of this embodiment, the first target field is a Random Access Preamble index field.

[1240] As a subembodiment of this embodiment, the first target field is an ra-PreambleIndex field.

[1241] As one subembodiment of this embodiment, the interpretation of the first target field refers to the Random Access Preamble Index field of DCI Format1_0 in Section 7.3.1.2.1 of 3GPP TS38.212.

[1242] In one embodiment, the target information block indicates the uplink carrier occupied by the first signal.

[1243] As a subembodiment of this embodiment, at least one bit in the target information block indicates an uplink carrier occupied by the first signal.

[1244] As one subembodiment of this embodiment, the target information block includes a second target field, and the second target field indicates an uplink carrier occupied by the first signal.

[1245] As one subembodiment of this embodiment, the candidates for the second target field include UL and SUL (Supplementary Uplink).

[1246] As one subembodiment of this embodiment, the candidates for the second target field include NUL (Normal Uplink) and SUL.

[1247] As one subembodiment of this embodiment, the uplink carrier candidates indicated by the second target field include NUL and SUL.

[1248] In one subembodiment of this embodiment, the second target field indicates one of NUL and SUL.

[1249] In one subembodiment of this embodiment, the length of the second target field is 1 bit.

[1250] In one subembodiment of this embodiment, the value of the second target field is a string.

[1251] In one subembodiment of this embodiment, the value of the second target field is a single bit string.

[1252] In one subembodiment of this embodiment, the value of the second target field is a Boolean value.

[1253] In one subembodiment of this embodiment, the second target field is a single UL / SUL indicator field.

[1254] As one subembodiment of this embodiment, the interpretation of the second target field refers to the UL / SUL indicator field of DCI Format1_0 in Section 7.3.1.2.1 of 3GPP TS38.212.

[1255] In one embodiment, the uplink carrier occupied by the first preamble is the default.

[1256] As one subembodiment of this embodiment, the target information block does not include a field for indicating the uplink carrier occupied by the first preamble.

[1257] As a subembodiment of this embodiment, the uplink carrier occupied by the first preamble is NUL.

[1258] As one subembodiment of this embodiment, the uplink carrier occupied by the first preamble is the SUL.

[1259] In one embodiment, the target information block indicates a reference signal (RS) resource associated with the first signal.

[1260] In one embodiment, at least one bit in the target information block indicates an RS resource associated with the first signal.

[1261] In one embodiment, the target information block includes a third target field, where the third target field indicates an RS resource associated with the first preamble.

[1262] In one subembodiment of this embodiment, the value of the third target field is a string.

[1263] In one subembodiment of this embodiment, the value of the third target field is a single bit string.

[1264] In one subembodiment of this embodiment, the third target field includes at least one bit.

[1265] In one subembodiment of this embodiment, the length of the third target field is 6 bits.

[1266] In one subembodiment of this embodiment, the third target field is 5 bits long.

[1267] As one subembodiment of this embodiment, the third target field is one ssb field, and the third target field indicates an SSB-Index.

[1268] As one subembodiment of this embodiment, the third target field is one csi-RS field, and the third target field indicates a CSI-RS-index.

[1269] In one subembodiment of this embodiment, the third target field is an SS / PBCH index field.

[1270] As one subembodiment of this embodiment, the interpretation of the third target field refers to the SS / PBCH field of DCI Format1_0 in Section 7.3.1.2.1 of 3GPP TS38.212.

[1271] In one embodiment, the target information block indicates the PRACH mask of the first signal. do.

[1272] In one embodiment, at least one bit in the target information block indicates a PRACH mask of the first signal.

[1273] In one embodiment, the target information block includes a fourth target field, which indicates the PRACH mask of the first preamble.

[1274] As a subembodiment of this embodiment, the fourth target field includes the index of the PRACH mask used by the first preamble.

[1275] In one subembodiment of this embodiment, the fourth target field includes an index in a table.

[1276] As a subembodiment of this embodiment, the fourth target field includes an index in Table 7.4.1 in 3GPP TS38.321.

[1277] In one subembodiment of this embodiment, the value of the fourth target field is a string.

[1278] In one subembodiment of this embodiment, the value of the fourth target field is a single bit string.

[1279] In one subembodiment of this embodiment, the fourth target field includes at least one bit.

[1280] In one subembodiment of this embodiment, the fourth target field is 5 bits in length.

[1281] In one subembodiment of this embodiment, the fourth target field is 4 bits in length.

[1282] In one subembodiment of this embodiment, the fourth target field is a PRACH Mask index field.

[1283] As one subembodiment of this embodiment, the interpretation of the fourth target field refers to the PRACH Mask index field of DCI Format1_0 in Section 7.3.1.2.1 of 3GPP TS38.212.

[1284] In one embodiment, the target information block includes at least one of a first target field, a second target field, a third target field, or a fourth target field.

[1285] Embodiment 11A Embodiment 11A illustrates a flowchart of transmitting a first message, a first preamble, and a PDCCH identified by a first RNTI according to another embodiment of the present application, as shown in Figure 11A. In Figure 11A, each block represents a step. It is emphasized that the order of the blocks in the figure does not represent the time relationship between the represented steps.

[1286] In embodiment 11A, in step 1101, a first node in the present application receives a first message, the first message including a first identifier, the first identifier indicating a first cell; in step 1102, after the first message is received, transmits a first preamble in a first random access process; in step 1103, in response to the operation of transmitting the first preamble, monitors a PDCCH identified by a first RNTI within a first time window, the first message being one MAC CE, the first message including a first information block, and the air interface resource of the first preamble depends on the first information block, and the air interface resource includes at least one of a code domain resource, a time domain resource, or a frequency domain resource.

[1287] In one embodiment, the first message is received on one serving cell of the first node.

[1288] In one embodiment, the first message is received on a PCell of the first node.

[1289] In one embodiment, the first message is received in the RRC_CONNECTED state.

[1290] In one embodiment, the first message is used for L1 / L2 triggered mobility.

[1291] In one embodiment, the first message is used for mobility.

[1292] In one embodiment, the first message is used for handover.

[1293] In one embodiment, the first message is UE-specific signaling.

[1294] In one embodiment, the first message is used to instruct the first node to move the PCell to the first cell.

[1295] In one embodiment, the movement refers to a handover.

[1296] In one embodiment, the above movement refers to switching.

[1297] In one embodiment, the above movement refers to a change.

[1298] In one embodiment, the first information block is a MAC field.

[1299] In one embodiment, the first information block is a plurality of MAC fields.

[1300] In one embodiment, the first cell is a candidate cell for L1 / L2 triggered mobility.

[1301] In one embodiment, the first cell is configured with at least one CellGroupConfig IE.

[1302] In one embodiment, the first cell is configured with at least one ServingCellConfig IE.

[1303] In one embodiment, the first cell is configured with a first identifier.

[1304] In one embodiment, the first identifier is an index of the first cell.

[1305] In one embodiment, the first identifier is an index of the candidate configuration of the first cell.

[1306] In one embodiment, the first identifier is an index of a candidate configuration of the first cell within the at least one candidate configuration.

[1307] In one embodiment, the first identifier is an index of the first cell among the at least one candidate cell.

[1308] In one embodiment, before the first message, at least one RRC Reconfiguration message is received, and the at least one RRC Reconfiguration message includes an index and configuration information of each candidate cell among the at least one candidate cell.

[1309] In one embodiment, at least one RRCReconfiguration message includes a CellGroupConfig IE configured for each candidate cell.

[1310] In one embodiment, at least one RRCReconfiguration message includes a ServingCellConfig IE configured for each candidate cell.

[1311] In one embodiment, the air interface resource of the first preamble belongs to the first cell.

[1312] In one embodiment, the first random access process is performed on a first cell.

[1313] Embodiment 11B Embodiment 11B illustrates a schematic diagram of the first signal being one DCI according to one embodiment of the present application, as shown in FIG. 11B.

[1314] In embodiment 11B, the first signal is one DCI.

[1315] In one embodiment, the first signaling is used to schedule a PUSCH.

[1316] In one embodiment, the first signaling is used to schedule a PDSCH (Physical Downlink Shared Channel).

[1317] In one embodiment, the format of the first signal is DCI Format0_0.

[1318] In one embodiment, the format of the first signal is DCI Format0_1.

[1319] In one embodiment, the format of the first signal is DCI Format0_2.

[1320] In one embodiment, the format of the first signal is DCI Format1_0.

[1321] In one embodiment, the format of the first signal is DCI Format1_1.

[1322] In one embodiment, the format of the first signal is DCI Format1_2.

[1323] In one embodiment, the first signaling is identified by a second identifier, and the second identifier is a C-RNTI of the first node.

[1324] In one embodiment, the first signaling is identified by a C-RNTI of one of the first nodes.

[1325] In one embodiment, the first signaling is identified by a C-RNTI of a first node in a first cell.

[1326] In one embodiment, the target information block indicates the air interface resources to be used for the first signal.

[1327] In one embodiment, the target information block indicates a search space to be used to receive the first signal.

[1328] In one embodiment, the target information block indicates the CORESET to be used to receive the first signal.

[1329] In one embodiment, the target information block indicates the TCI to be used to receive the first signal.

[1330] In one embodiment, the target information block indicates the PDCCH to be used to receive the first signal.

[1331] In one embodiment, the target information block indicates configuration information of a PDCCH used to receive the first signal.

[1332] In one embodiment, the target information block indicates PDCCH parameters dedicated to the first node that is to be used to receive the first signal.

[1333] In one embodiment, the target information block includes an index.

[1334] In one embodiment, the target information block contains one TCI-StateId.

[1335] In one embodiment, the target information block includes one ControlResourceSetId.

[1336] In one embodiment, the target information block includes one ControlResourceSetZero.

[1337] In one embodiment, the target information block includes one BWP-Id.

[1338] In one embodiment, the target information block includes one SearchSpaceId.

[1339] Embodiment 12A Embodiment 12A illustrates a structural block diagram of a processing device used in a first node according to an embodiment of the present application, as shown in Figure 12A. In Figure 12A, a processing device 1200A in the first node includes a first receiver 1201A and a first transmitter 1202A.

[1340] a first receiver 1201A receives a first message, the first message including a first identifier, the first identifier indicating a first node; After the first message is received, the first transmitter 1202A sends a first preamble in a first random access process; In response to the operation of transmitting the first preamble, the first receiver 1201A monitors, within a first time window, a PDCCH identified by the first RNTI; In embodiment 12A, the first message is one RRC message, the logical channel used to carry the first message is a PCCH, the first message includes a first information block, the air interface resources of the first preamble depend on the first information block, and the air interface resources include at least one of code domain resources, time domain resources, or frequency domain resources.

[1341] In one embodiment, interpretation of the first information block depends on a second identifier, the second identifier being used by the first node, and the first identifier being different from the second identifier.

[1342] In one embodiment, before the first message is received, the first receiver 1201A receives a second message, which is used to decide to transition to an RRC_INACTIVE state, the second message includes a first identifier, the first message instructs the first node to perform data transmission in the RRC_INACTIVE state, and the first message is received in the RRC_INACTIVE state.

[1343] In one embodiment, the first information block indicates at least one of a preamble sequence used by the first preamble, or an uplink carrier occupied by the first preamble, or an RS resource associated with the first preamble, or a PRACH mask of the first preamble.

[1344] In one embodiment, the first receiver 1201A receives a third message, the third message is used to determine at least one PRACH configuration, the first information block indicates a first PRACH configuration among the at least one PRACH configuration, and the first PRACH configuration is used to determine air interface resources for the first preamble.

[1345] In one embodiment, the first receiver 1201A receives a first DCI, the first DCI is identified by a first RNTI, and in response to receiving the first DCI, the first random access process is deemed to have been completed successfully, and the first RNTI is one C-RNTI.

[1346] In one embodiment, the first receiver 1201A receives a first DCI and a first signaling, the first DCI is identified by a first RNTI, the first DCI is used to schedule the first signaling, and in response to receiving the first signaling, the first random access process is deemed to have been successfully completed, and the first signaling includes at least a timing advance.

[1347] In one embodiment, the first RNTI is one C-RNTI, and the first signaling includes one absolute timing advance MAC CE.

[1348] In one embodiment, the first receiver 1201A comprises the antenna 452, the receiving device 454, the multi-antenna receiving processor 458, the receiving processor 456, the controller / processor 459, the memory 460, and the data source 467 in FIG. 4 of the present application.

[1349] In one embodiment, the first receiver 1201A comprises the antenna 452, the receiving device 454, the multi-antenna receive processor 458, and the receive processor 456 in FIG. 4 of the present application.

[1350] In one embodiment, the first receiver 1201A comprises the antenna 452, the receiving device 454, and the receiving processor 456 in FIG. 4 of the present application.

[1351] In one embodiment, the first transmitter 1202A comprises the antenna 452, the transmitting device 454, the multi-antenna transmit processor 457, the transmit processor 468, the controller / processor 459, the memory 460, and the data source 467 in FIG. 4 of the present application.

[1352] In one embodiment, the first transmitter 1202A comprises the antenna 452, the transmitting device 454, the multi-antenna transmit processor 457, and the transmit processor 468 in FIG. 4 of the present application.

[1353] In one embodiment, the first transmitter 1202A comprises the antenna 452, the transmitting device 454, and the transmitting processor 468 in FIG. 4 of the present application.

[1354] Embodiment 12B Embodiment 12B illustrates a schematic diagram of at least some of the bits in the first information block and the target identifier being subjected to a first operation to obtain a target information block according to an embodiment of the present application, as shown in Figure 12B. Block 1201B includes the first information block, block 1202B includes the target identifier, block 1203B includes the first operation, and block 1204B includes the target information block.

[1355] In embodiment 12B, at least some of the bits in the first information block and the target identifier are subjected to a first operation to obtain the target information block.

[1356] In one embodiment, the first processing device performs the first operation.

[1357] In one embodiment, the first node performs the first operation.

[1358] In one embodiment, the input of the first operation comprises at least a portion of the bits in the first block of information.

[1359] In one embodiment, the input of the first operation includes a target identifier.

[1360] In one embodiment, the output of the first operation comprises a target information block.

[1361] In one embodiment, the first operation comprises the inverse of the second operation.

[1362] In one embodiment, the first operation includes a linear operation.

[1363] In one embodiment, the first operation includes a non-linear operation.

[1364] In one embodiment, the first operation includes a logical operation.

[1365] In one embodiment, the first operation comprises a Boolean operation.

[1366] In one embodiment, the first operation includes a bit operation.

[1367] In one embodiment, the first operation comprises an XOR.

[1368] In one embodiment, the first operation includes AND-OR.

[1369] In one embodiment, the first operation includes XNOR.

[1370] In one embodiment, the first operation includes AND.

[1371] In one embodiment, the first operation includes an OR.

[1372] In one embodiment, the first operation comprises NOT.

[1373] In one embodiment, the first operation comprises an AND-NOT.

[1374] In one embodiment, the first operation includes a CRC.

[1375] In one embodiment, the first operation is a linear operation.

[1376] In one embodiment, the first operation is a non-linear operation.

[1377] In one embodiment, the first operation is a logical operation.

[1378] In one embodiment, the first operation is a Boolean operation.

[1379] In one embodiment, the first operation is a bitwise operation.

[1380] In one embodiment, the first operation is an XOR.

[1381] In one embodiment, the first operation is AND-OR.

[1382] In one embodiment, the first operation is XNOR.

[1383] In one embodiment, the first operation is an AND.

[1384] In one embodiment, the first operation is an OR.

[1385] In one embodiment, the first operation is NOT.

[1386] In one embodiment, the first operation is AND-NOT.

[1387] In one embodiment, the first operation is a CRC.

[1388] In one embodiment, it is assumed that the first information block is 10111000111111111, the target identifier is 00101010110110010, the first information block and the target identifier are subjected to a first operation to obtain the target information block 10010000010011010, the second identifier is 0010101101100101001110, the target identifier is the first 14 bits in the second identifier, and the first operation is XOR.

[1389] In one embodiment, it is assumed that the first information block is 10111001111111110, the target identifier is 0010100110110010, the first 16 bits in the first information block and the target identifier are subjected to a first operation to obtain the target information block 10010000010011010, the second identifier is 0010100110110010, the target identifier is the second identifier, and the first operation is XOR.

[1390] In one embodiment, at least some of the bits in the target information block and the target identifier are subjected to a second operation to obtain the first information block, the second operation being performed by a second node.

[1391] In one embodiment, at least some of the bits in the target information block are subjected to a second operation to obtain the first information block, the second operation being performed by a second node.

[1392] Embodiment 13A Embodiment 13A illustrates a structural block diagram of a processing device in a second node according to an embodiment of the present application, as shown in Figure 13A. In Figure 13A, the processing device 1300A in the second node includes a second transmitter 1301A and a second receiver 1302A.

[1393] a second transmitter 1301A transmits a first message, the first message including a first identifier, the first identifier indicating a first node; The second receiver 1302A receives a first preamble in a first random access process after the first message is transmitted; In response to receiving the first preamble, the second transmitter 1301A transmits a PDCCH identified by the first RNTI; In embodiment 13A, a sender of a first preamble monitors a PDCCH identified by a first RNTI within a first time window, the first message is one RRC message, the logical channel used to carry the first message is a PCCH, the first message includes a first information block, and the air interface resources of the first preamble depend on the first information block, and the air interface resources include at least one of code domain resources, time domain resources, or frequency domain resources.

[1394] In one embodiment, the interpretation of the first information block depends on the second identifier. The child is used for the first node, and the first identifier is different from the second identifier.

[1395] In one embodiment, before the first message is transmitted, the second transmitter 1301A transmits a second message, the second message is used to determine to transition to the RRC_INACTIVE state, the second message includes a first identifier, the first message indicates that the sender of the first preamble will perform data transmission in the RRC_INACTIVE state, and the first message is received in the RRC_INACTIVE state.

[1396] In one embodiment, the first information block indicates at least one of a preamble sequence used by the first preamble, or an uplink carrier occupied by the first preamble, or an RS resource associated with the first preamble, or a PRACH mask of the first preamble.

[1397] In one embodiment, the second transmitter 1301A transmits a third message, the third message is used to determine at least one PRACH configuration, the first information block indicates a first PRACH configuration among the at least one PRACH configuration, and the first PRACH configuration is used to determine an air interface resource of the first preamble.

[1398] In one embodiment, the second transmitter 1301A transmits a first DCI, where the first DCI is identified by a first RNTI, and in response to receiving the first DCI, the sender of the first preamble considers that the first random access process has been successfully completed, where the first RNTI is a C-RNTI.

[1399] In one embodiment, the second transmitter 1301A transmits a first DCI and a first signaling, the first DCI is identified by a first RNTI, the first DCI is used to schedule the first signaling, and in response to receiving the first signaling, the sender of the first preamble considers the first random access process to be successfully completed, and the first signaling includes at least a timing advance.

[1400] In one embodiment, the first RNTI is one C-RNTI, and the first signaling includes one absolute timing advance MAC CE.

[1401] In one embodiment, the second transmitter 1301A comprises the antenna 420, the transmitting device 418, the multi-antenna transmit processor 471, the transmit processor 416, the controller / processor 475, and the memory 476 in FIG. 4 of the present application.

[1402] In one embodiment, the second transmitter 1301A comprises the antenna 420, the transmitting device 418, the multi-antenna transmit processor 471, and the transmit processor 416 in FIG. 4 of the present application.

[1403] In one embodiment, the second transmitter 1301A comprises the antenna 420, the transmitting device 418, and the transmitting processor 416 in FIG. 4 of the present application.

[1404] In one embodiment, the second receiver 1302A comprises the antenna 420, the receiving device 418, the multi-antenna receive processor 472, the receive processor 470, the controller / processor 475, and the memory 476 in FIG. 4 of the present application.

[1405] In one embodiment, the second receiver 1302A comprises the antenna 420, the receiving device 418, the multi-antenna receive processor 472, and the receive processor 470 in FIG. 4 of the present application.

[1406] In one embodiment, the second receiver 1302A comprises the antenna 420, the receiving device 418, and the receiving processor 470 in FIG. 4 of the present application.

[1407] Embodiment 13B Embodiment 13B illustrates a structural block diagram of a processing device used in a first node according to an embodiment of the present application, as shown in Figure 13B. In Figure 13B, the processing device 1300B in the first node includes a first processing device 1301B.

[1408] The first processing device 1301B receives a first message, the first message being one RRC message, the first message not being transmitted via a dedicated logical channel, the first message including a first identifier, the first identifier indicating a first node, and processes the first signal after the first message is received.

[1409] In embodiment 13B, the operation of processing the first signal depends on the target information block, at least the former of the first information block and the second identifier is used to determine the target information block, the target information block is dedicated to the first node, the second identifier is used for the first node, the first identifier is different from the second identifier, the first message includes only the former of the first information block and the target information block, and the processing includes one of sending and receiving.

[1410] In one embodiment, the first information block and at least a portion of the target identifier are used to determine the target information block, and the second identifier is used to generate the target identifier.

[1411] In one embodiment, the first information block includes at least one bit, and the second identifier is a bit string.

[1412] In one embodiment, before the first message is received, the first processing device 1301B receives at least the first of a first sub-message and a second sub-message, the first sub-message including a first identifier and the second sub-message including a second identifier.

[1413] In one embodiment, the first sub-message is used to decide to transition to the RRC_INACTIVE state, the logical channel used to carry the first message is the PCCH, and the first message indicates that the first node implements data transmission in the RRC_INACTIVE state.

[1414] In one embodiment, the meaning of the phrase "the operation of processing the first signal depends on the target information block" includes that the target information block indicates the air interface resources used for the first signal, and the air interface resources include at least one of code domain resources, or time domain resources, or frequency domain resources.

[1415] In one embodiment, the first signal is a preamble.

[1416] In one embodiment, the first signal is one DCI.

[1417] In one embodiment, the first processing device 1301B comprises the antenna 452, the receiving device 454, the multi-antenna receiving processor 458, the receiving processor 456, the controller / processor 459, the memory 460, and the data source 467 in FIG. 4 of the present application.

[1418] In one embodiment, the first processing device 1301B comprises the antenna 452, the receiving device 454, the multi-antenna receiving processor 458, and the receiving processor 456 in FIG. 4 of the present application.

[1419] In one embodiment, the first processing device 1301B comprises the antenna 452, the receiving device 454, and the receiving processor 456 in FIG. 4 of the present application.

[1420] In one embodiment, the first processing device 1301B comprises the antenna 452, the transmitting device 454, the multi-antenna transmit processor 457, the transmit processor 468, the controller / processor 459, the memory 460, and the data source 467 in FIG. 4 of the present application.

[1421] In one embodiment, the first processing device 1301B comprises the antenna 452, the transmitting device 454, the multi-antenna transmitting processor 457, and the transmitting processor 468 in FIG. 4 of the present application.

[1422] In one embodiment, the first processing device 1301B comprises the antenna 452, the transmitting device 454, and the transmitting processor 468 in FIG. 4 of the present application.

[1423] Embodiment 14 Embodiment 14 illustrates a structural block diagram of a processing device used in a second node according to an embodiment of the present application, as shown in Figure 14. In Figure 14, the processing device 1400 in the second node includes a second processing device 1401.

[1424] The second processing device 1401 transmits a first message, the first message being one RRC message, the first message not being transmitted via a dedicated logical channel, the first message including a first identifier, the first identifier indicating a first node, and processes the first signal after the first message is transmitted.

[1425] In embodiment 14, the operation of processing the first signal depends on the target information block, at least the former of the first information block and the second identifier is used to determine the target information block, the target information block is dedicated to the first node, the second identifier is used for the first node, the first identifier is different from the second identifier, the first message includes only the former of the first information block and the target information block, and the processing includes one of sending and receiving.

[1426] In one embodiment, the first information block and at least a portion of the target identifier are used to determine the target information block, and the second identifier is used to generate the target identifier.

[1427] In one embodiment, the first information block includes at least one bit, and the second identifier is a bit string.

[1428] In one embodiment, before the first message is transmitted, the second processing device 1401 transmits at least a first sub-message and a second sub-message, the first sub-message including a first identifier, and the second sub-message including a second identifier.

[1429] In one embodiment, the first sub-message is used to decide to transition to the RRC_INACTIVE state, the logical channel used to carry the first message is the PCCH, and the first message indicates that the first node implements data transmission in the RRC_INACTIVE state.

[1430] In one embodiment, the meaning of the phrase "the operation of processing the first signal depends on the target information block" includes that the target information block indicates the air interface resources used for the first signal, and the air interface resources include at least one of code domain resources, or time domain resources, or frequency domain resources.

[1431] In one embodiment, the first signal is a preamble.

[1432] In one embodiment, the first signal is one DCI.

[1433] In one embodiment, the second processing device 1401 comprises the antenna 420, the transmitting device 418, the multi-antenna transmit processor 471, the transmit processor 416, the controller / processor 475, and the memory 476 in FIG. 4 of the present application.

[1434] In one embodiment, the second processing device 1401 comprises the antenna 420, the transmitting device 418, the multi-antenna transmitting processor 471, and the transmitting processor 416 in FIG. 4 of the present application.

[1435] In one embodiment, the second processing device 1401 comprises the antenna 420, the transmitting device 418, and the transmitting processor 416 in FIG. 4 of the present application.

[1436] In one embodiment, the second processing device 1401 comprises the antenna 420, the receiving device 418, the multi-antenna receiving processor 472, the receiving processor 470, the controller / processor 475, and the memory 476 in FIG. 4 of the present application.

[1437] In one embodiment, the second processing device 1401 comprises the antenna 420, the receiving device 418, the multi-antenna receiving processor 472, and the receiving processor 470 in FIG. 4 of the present application.

[1438] In one embodiment, the second processing device 1401 comprises the antenna 420, the receiving device 418, and the receiving processor 470 in FIG. 4 of the present application.

[1439] Those skilled in the art can understand that all or part of the steps in the above method can be completed by instructing relevant hardware through a program, and the above program can be stored in a computer-readable storage medium such as a read-only memory, a hard disk, or an optical disk. Optionally, all or part of the steps in the above embodiments can also be implemented using one or more integrated circuits. Therefore, each module unit in the above embodiments can be implemented in the form of hardware or a software function module, and the present application is not limited to any particular form of software and hardware combination. The user equipment, terminal, and UE in the present application include, but are not limited to, drones, communication modules on drones, remote control devices, and the like. The term "base station" or "system device" refers to a wireless communication device, such as a mobile phone, a mobile telephone, a tablet computer, a notebook computer, a vehicle-mounted communication device, a wireless sensor, an internet card, an internet of things terminal, an RFID terminal, an NB-IoT terminal, an MTC (Machine Type Communication) terminal, an eMTC (enhanced MTC) terminal, a data card, an internet card, a vehicle-mounted communication device, a low-cost mobile phone, a low-cost tablet computer, and other wireless communication devices. The term "base station" or "system device" in this application refers to a macrocellular base station, a microcellular base station, a femtocell, a relay base station, a gNB (NR Node B), a TRP (Transmit Receiving Point), and other wireless communication devices.

[1440] The above is only a preferred embodiment of the present application and is not used to limit the protection scope of the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present application shall fall within the protection scope of the present application.

Claims

1. A first node for wireless communication, comprising: a first receiver for receiving a first message, the first message including a first identifier, the first identifier indicating the first node; a first transmitter for transmitting a first preamble in a first random access process after the first message is received; In response to transmitting the first preamble, the first receiver monitors a PDCCH identified by a first RNTI within a first time window; 1. A first node, wherein the first message is one RRC message, a logical channel used to carry the first message is a PCCH, the first message includes a first information block, air interface resources of the first preamble depend on the first information block, and the air interface resources include at least one of code domain resources, time domain resources, or frequency domain resources.

2. 2. The first node of claim 1, wherein interpretation of the first information block depends on a second identifier, the second identifier being used by the first node, and the first identifier being different from the second identifier.

3. a first receiver for receiving a second message before the first message is received, the second message being used to determine to transition to an RRC_INACTIVE state; 3. The first node according to claim 1, wherein the second message includes the first identifier, the first message indicates that the first node is to perform data transmission in the RRC_INACTIVE state, and the first message is received in the RRC_INACTIVE state.

4. 4. The first node according to claim 1, wherein the first information block indicates at least one of a preamble sequence used by the first preamble, or an uplink carrier occupied by the first preamble, or an RS resource associated with the first preamble, or a PRACH mask of the first preamble.

5. a first receiver for receiving a third message, the third message being used to determine at least one PRACH configuration; 4. The first node according to claim 1, wherein the first information block indicates a first PRACH configuration within the at least one PRACH configuration, and the first PRACH configuration is used to determine the air interface resources of the first preamble.

6. the first receiver for receiving a first DCI, the first DCI being identified by the first RNTI, and in response to the first DCI being received, the first random access process being deemed to have been successfully completed; The first node according to any one of claims 1 to 5, wherein the first RNTI is one C-RNTI.

7. a first receiver for receiving a first DCI and a first signaling, the first DCI being identified by the first RNTI, and the first DCI being the first random access process is considered to be completed successfully in response to receiving the first signaling; The first node according to any one of claims 1 to 5, wherein the first signaling includes at least a timing advance.

8. The first node according to any one of claims 1 to 7, wherein the first RNTI is one C-RNTI and the first signaling includes one Absolute Timing Advance MAC CE.

9. A second node for wireless communication, comprising: a second transmitter for transmitting a first message, the first message including a first identifier, the first identifier indicating a first node; and a second receiver for receiving a first preamble in a first random access process after the first message is transmitted; In response to receiving the first preamble, the second transmitter transmits a PDCCH identified by a first RNTI; a second node, wherein a sender of the first preamble monitors a PDCCH identified by the first RNTI within a first time window, the first message is one RRC message, a logical channel used to carry the first message is a PCCH, the first message includes a first information block, air interface resources of the first preamble depend on the first information block, and the air interface resources include at least one of code domain resources, time domain resources, or frequency domain resources.

10. 1. A method for use in a first node for wireless communication, comprising: receiving a first message, the first message including a first identifier, the first identifier indicating the first node; After the first message is received, transmitting a first preamble in a first random access process; monitoring a PDCCH identified by a first RNTI within a first time window in response to transmitting the first preamble; the first message is an RRC message, a logical channel used to carry the first message is a PCCH, the first message includes a first information block, air interface resources of the first preamble depend on the first information block, and the air interface resources include at least one of code domain resources, time domain resources, or frequency domain resources.

11. 1. A method for use in a second node for wireless communication, comprising: transmitting a first message, the first message including a first identifier, the first identifier indicating a first node; receiving a first preamble in a first random access process after the first message is transmitted; transmitting a PDCCH identified by a first RNTI in response to receiving the first preamble; a sender of the first preamble monitors a PDCCH identified by the first RNTI within a first time window, the first message is an RRC message, a logical channel used to carry the first message is a PCCH, the first message includes a first information block, and the first preamble wherein air interface resources of a channel depend on the first information block, and the air interface resources include at least one of code domain resources, time domain resources, or frequency domain resources.

Images