Method and apparatus for power control in random access procedure

Abstract

Embodiments of the present disclosure provide methods and apparatuses for power control in random access procedure. A method implemented at a terminal device includes obtaining at least one power control parameter to be used for a request message for contention-free random access, CFRA. The method further includes transmitting the request message for CFRA to a network node. Power of the request message for CFRA is controlled based on the at least one power control parameter. The request message includes a random access channel, RACH, preamble and a physical uplink shared channel, PUSCH.

Description

Technical Field

[0001] This invention relates to wireless communication technology, and more particularly to a power control method and apparatus for random access procedures. Background Technology

[0002] This section introduces several aspects that can help in a better understanding of this disclosure. Therefore, the statements in this section should be read in this light and should not be construed as an admission of what is in or not in the prior art.

[0003] Figure 1 This diagram illustrates the four-step random access procedure, also known as the Type-1 random access procedure. In wireless communication systems such as New Radio (NR) systems, such as... Figure 1 The illustrated four-step / 4-step method can be used for random access procedures. In this method, a terminal equipment, such as a User Equipment (UE), detects the synchronization signal (SS) in the Physical Broadcast Channel (PBCH), which includes the Primary Synchronization Signal (PSS) and the Secondary Synchronization Signal (SSS), and decodes the system information broadcast in the Radio Resource Control (RRC) message, which includes the Remaining Minimal System Information (RMSI) and Other System Information (OSI). It then transmits the Physical Random Access Channel (PRACH) preamble (Message 1) in the uplink. A base station, such as a Next Generation Node B (gNB), responds with a Random Access Response (RAR, Message 2). The UE then transmits its UE identifier on the Physical Uplink Shared Channel (PUSCH) (Message 3).

[0004] After receiving the timing advance command in the RAR, the UE sends a PUSCH (message 3), allowing the PUSCH to be received with timing precision within the cyclic prefix (CP). Without this timing advance, a very large CP would be required to demodulate and detect the PUSCH, unless the system is used in a cell where the distance between the UE and gNB is very small. Since NR will also support larger cells that require timing advance to the UE, a four-step approach is necessary for the random access procedure.

[0005] During the four-step random access channel (RACH) process, power control needs to be performed on message 3PUSCH. See Section 7.1 of 3GPP Technical Specification (TS) 38.213 V16.0.0, the entire contents of which are hereby incorporated by reference. Summary of the Invention

[0006] The present invention is provided in a simplified form to introduce a chosen concept, which will be further described in the following detailed description. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to limit the scope of the claimed subject matter.

[0007] Certain aspects of this disclosure and its embodiments may provide solutions to these or other challenges. Various embodiments are presented herein to address one or more of the problems disclosed herein.

[0008] A first aspect of this disclosure provides a method implemented at a terminal device. The method includes obtaining at least one power control parameter, which will be used in a request message for Contention-Free Random Access Request (CFRA). The method further includes sending the CFRA request message to a network node. The power of the CFRA request message is controlled based on the at least one power control parameter. The request message includes a Random Access Channel (RACH) preamble and a Physical Uplink Shared Channel (PUSCH).

[0009] In embodiments of this disclosure, the at least one power control parameter can be used to calculate the power of the PUSCH of the request message.

[0010] In embodiments of this disclosure, the at least one power control parameter may include at least one of the following: one or more power control parameters configured in dedicated signaling; one or more power control parameter configurations for the PUSCH in a two-step contention-based random access (CBRA); and one or more power control parameter configurations for the PUSCH in a four-step random access (CBRA).

[0011] In embodiments of this disclosure, one or more power control parameters configured in the dedicated signaling include at least one of the following: a power offset of the PUSCH relative to the preamble receive target power; a dedicated alpha value for the PUSCH, where alpha is a scaling factor for path loss; a power ramping step for the PUSCH; an indication of whether a delta modulation and coding scheme (MCS) is applied; an indication of whether transmit power control (TPC) with cumulative output is enabled; and a TPC command for the PUSCH.

[0012] In embodiments of this disclosure, when the power offset of the PUSCH relative to the preamble receive target power is configured in dedicated signaling, the power offset of the PUSCH relative to the preamble receive target power configured in dedicated signaling is used to calculate the power of the PUSCH of the request message.

[0013] In embodiments of this disclosure, when the power offset of the PUSCH relative to the preamble receive target power is not present in the dedicated signaling, and the power offset of the PUSCH relative to the preamble receive target power in the two-step CBRA is configured, the power offset of the PUSCH relative to the preamble receive target power in the two-step CBRA is used to calculate the power of the PUSCH of the request message.

[0014] In embodiments of this disclosure, when the power offset of the PUSCH relative to the preamble receive target power is absent in dedicated signaling, and the power offset of the PUSCH relative to the preamble receive target power is absent in two-step CBRA, and the power offset of the PUSCH relative to the preamble receive target power is configured in four-step random access, the power offset of the PUSCH relative to the preamble receive target power in four-step random access is used to calculate the power of the PUSCH of the request message.

[0015] In embodiments of this disclosure, the range of values ​​for the power offset of the PUSCH relative to the preamble receive target power configured in dedicated signaling includes -1dB, 0dB, 1dB, 2dB, 3dB, 4dB, 5dB, and 6dB.

[0016] In embodiments of this disclosure, the power offset of the PUSCH relative to the preamble receive target power in the two-step CBRA is used to calculate the power of the PUSCH of the request message.

[0017] In embodiments of this disclosure, the power offset of the PUSCH relative to the preamble reception target power in four-step random access is used to calculate the power of the PUSCH of the request message.

[0018] In embodiments of this disclosure, when a dedicated alpha value for PUSCH is configured in dedicated signaling, the dedicated alpha value for PUSCH configured in the dedicated signaling is used to calculate the power of the PUSCH in the request message.

[0019] In embodiments of this disclosure, when a dedicated alpha value for PUSCH is not present in dedicated signaling and an alpha value is configured in a two-step CBRA, the alpha value in the two-step CBRA is used to calculate the power of the PUSCH for the request message.

[0020] In embodiments of this disclosure, when the dedicated alpha value for PUSCH is not present in dedicated signaling, the alpha value is not present in two-step CBRA, and the alpha value is configured in four-step random access, the alpha value in four-step random access is used to calculate the PUSCH power of the request message.

[0021] In embodiments of this disclosure, when the dedicated alpha value for PUSCH is absent in dedicated signaling, absent in two-step CBRA, and absent in four-step random access, the dedicated alpha value for PUSCH is set to 1.

[0022] In the embodiments of this disclosure, the range of dedicated alpha values ​​configured in the dedicated signaling for PUSCH is {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1}, where alpha0 corresponds to 0, alpha04 corresponds to 0.4, alpha05 corresponds to 0.5, alpha06 corresponds to 0.6, alpha07 corresponds to 0.7, alpha08 corresponds to 0.8, alpha09 corresponds to 0.9, and alpha1 corresponds to 1.

[0023] In embodiments of this disclosure, the alpha value in the two-step CBRA is used to calculate the power of the PUSCH of the request message.

[0024] In embodiments of this disclosure, the alpha value in the four-step random access is used to calculate the power of the PUSCH of the request message.

[0025] In the embodiments of this disclosure, the range of the power increment step size configured in the dedicated signaling for PUSCH is {dB0,dB2,dB4,dB6}, where dB0 corresponds to a power increment step size of 0dB, dB2 corresponds to a power increment step size of 0dB, dB4 corresponds to a power increment step size of 0dB, and dB6 corresponds to a power increment step size of 0dB.

[0026] In embodiments of this disclosure, when the power increment step size for PUSCH in a two-step CBRA is configured, the power increment step size for PUSCH in the two-step CBRA is used to calculate the power of the PUSCH of the request message.

[0027] In embodiments of this disclosure, when the indication of whether delta MCS is applied is not present, Ks = 0 is used to calculate the power of the PUSCH of the request message, wherein Ks is provided by the indication of whether delta MCS is applied.

[0028] In embodiments of this disclosure, the delta MCS in four-step random access indicates the power used to calculate the PUSCH of the request message.

[0029] In embodiments of this disclosure, when a TPC with accumulation is enabled, a TPC with accumulation command is applied; when a TPC with accumulation is not enabled, a TPC without accumulation command is applied; when there is no indication in the dedicated signaling whether to enable a TPC with accumulation, a TPC with accumulation is enabled.

[0030] In embodiments of this disclosure, the TPC cumulative indication in four-step random access is used to calculate the power of the PUSCH in the request message. The TPC cumulative indication is an indication of whether the sum of the TPC command values ​​in the set of TPC command values ​​should be used for PUSCH power control.

[0031] In embodiments of this disclosure, the dedicated signaling transmits the field of the TPC command for PUSCH.

[0032] In the dedicated signaling, the signaling transmits the 3-bit field of the TPC command used for PUSCH.

[0033] In the dedicated signaling, the signaling transmits a 2-bit field of the TPC command for PUSCH, and there is a mapping between the TPC command field and absolute and / or cumulative values.

[0034] In embodiments of this disclosure, at least one of the power increment step for PUSCH and the TPC command for PUSCH can be used to calculate the power of the PUSCH in the request message.

[0035] In embodiments of this disclosure, the dedicated signaling includes at least one of the following: dedicated signaling for random access in a Radio Resource Control (RRC) message; a handover command message; a beam fault recovery message; and a Physical Downlink Control Channel (PDCCH) that commands random access using a two-step CFRA.

[0036] In embodiments of this disclosure, the dedicated signaling for random access is the RACH-ConfigDedicated information element (IE).

[0037] In embodiments of this disclosure, the network node is the target network node for handover, and the method may further include receiving dedicated signaling from the source network node for handover. One or more power control parameters configured in the dedicated signaling may be sent from the target network node to the source network node for handover.

[0038] In embodiments of this disclosure, CFRA is a two-step contention-free random access CFRA, and the method may further include receiving a response from a network node indicating whether the CFRA was successful.

[0039] A second aspect of this disclosure provides a method implemented at a network node. The method includes sending at least one power control parameter to an end device. The method also includes receiving a request message for Contention-Free Random Access (CFRA) from the end device. The power of the request message for CFRA is controlled based on the at least one power control parameter. The request message includes a Random Access Channel (RACH) preamble and a Physical Uplink Shared Channel (PUSCH).

[0040] In embodiments of this disclosure, the network node is the target network node for handover, and sending at least one power control parameter to the terminal device may include sending one or more power control parameters configured in dedicated signaling to the source network node for handover, wherein the source network node for handover sends the dedicated signaling to the terminal device.

[0041] In embodiments of this disclosure, CFRA is a two-step contention-free random access CFRA, and the method may further include sending a response to the terminal device indicating whether the CFRA was successful.

[0042] A third aspect of this disclosure provides a terminal device comprising: a processor; and a memory. The memory stores instructions executable by the processor, thereby enabling the terminal device to obtain at least one power control parameter, which will be used for a request message for Contention-Free Random Access Request (CFRA); and to send the CFRA request message to a network node. The power of the CFRA request message is controlled based on the at least one power control parameter. The request message includes a Random Access Channel (RACH) preamble and a Physical Uplink Shared Channel (PUSCH).

[0043] A fourth aspect of this disclosure provides a network device comprising: a processor; and a memory. The memory stores instructions executable by the processor, thereby enabling the network device to transmit at least one power control parameter to an end device; and to receive a request message for Contention-Free Random Access RA (CFRA) from the end device. The power of the request message for CFRA is controlled based on the at least one power control parameter. The request message includes a Random Access Channel (RACH) preamble and a Physical Uplink Shared Channel (PUSCH).

[0044] A fifth aspect of this disclosure provides a terminal device. The terminal device includes an acquisition module and a transmission module. The acquisition module can be configured to acquire at least one power control parameter, which will be used in a request message for Contention-Free Random Access Request (CFRA). The transmission module can be configured to send the CFRA request message to a network node. The power of the CFRA request message is controlled based on the at least one power control parameter. The request message includes a Random Access Channel (RACH) preamble and a Physical Uplink Shared Channel (PUSCH).

[0045] A sixth aspect of this disclosure provides a network node. The network node includes a transmitting module and a receiving module. The transmitting module can be configured to send at least one power control parameter to a terminal device. The receiving module can be configured to receive a request message for Contention-Free Random Access (CFRA) from the terminal device. The power of the request message for CFRA is controlled based on the at least one power control parameter. The request message includes a Random Access Channel (RACH) preamble and a Physical Uplink Shared Channel (PUSCH).

[0046] A seventh aspect of this disclosure provides a computer program product including instructions that, when executed on at least one processor, cause the at least one processor to perform any method according to the first or second aspects of this disclosure.

[0047] An eighth aspect of this disclosure provides a communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a terminal device. The cellular network includes the aforementioned network nodes and / or the aforementioned terminal devices.

[0048] In embodiments of this disclosure, the system further includes a terminal device configured to communicate with the network node.

[0049] In embodiments of this disclosure, the processing circuitry of the host computer is configured to execute a host computer application to provide user data; the terminal device includes processing circuitry configured to execute a client application associated with the host computer application.

[0050] A ninth aspect of this disclosure provides a communication system including a host computer and a network node. The host computer includes a communication interface configured to receive user data transmitted from a terminal device. The transmission is from the terminal device to the network node. The network node is as described above, and / or the terminal device is as described above.

[0051] In embodiments of this disclosure, the processing circuitry of the host computer is configured to execute a host computer application. The terminal device is configured to execute a client application associated with the host computer application, thereby providing user data to be received by the host computer.

[0052] A tenth aspect of this disclosure provides a method implemented in a communication system that may include a host computer, a network node, and a UE. The method may include providing user data at the host computer. Optionally, the method may include, at the host computer, initiating a transmission carrying user data to the UE via a cellular network, the cellular network including network nodes capable of performing any steps of the method according to a second aspect of this disclosure.

[0053] The eleventh aspect of this disclosure provides a communication system including a host computer. The host computer may include processing circuitry and a communication interface, the processing circuitry being configured to provide user data and the communication interface being configured to forward the user data to a cellular network for transmission to a UE. The cellular network may include network nodes having radio interfaces and processing circuitry. The processing circuitry of the network nodes may be configured to perform any step of the method according to the second aspect of this disclosure.

[0054] A twelfth aspect of this disclosure provides a method implemented in a communication system, which may include a host computer, a network node, and a UE. The method may include providing user data at the host computer. Optionally, the method may include, at the host computer, initiating a transmission carrying user data to the UE via a cellular network including the network node. The UE may perform any step of the method according to a first aspect of this disclosure.

[0055] The thirteenth aspect of this disclosure provides a communication system including a host computer. The host computer may include processing circuitry configured to provide user data, and a communication interface configured to forward the user data to a cellular network for transmission to a UE. The UE may include a radio interface and processing circuitry. The UE's processing circuitry may be configured to perform any step of the method according to the first aspect of this disclosure.

[0056] The fourteenth aspect of this disclosure provides a method implemented in a communication system that may include a host computer, a network node, and a UE. The method may include receiving user data transmitted from the UE to the network node at the host computer, and the UE may perform any step of the method according to the first aspect of this disclosure.

[0057] The fifteenth aspect of this disclosure provides a communication system including a host computer. The host computer may include a communication interface configured to receive user data originating from transmissions from a UE to a network node. The UE may include a radio interface and processing circuitry. The processing circuitry of the UE may be configured to perform any step of the method according to the first aspect of this disclosure.

[0058] The sixteenth aspect of this disclosure provides a method implemented in a communication system that may include a host computer, a network node, and a UE. The method may include receiving, at the host computer, user data transmitted from the network node that has already been received by the network node from the UE. The network node may perform any step of the method according to the second aspect of this disclosure.

[0059] The seventeenth aspect of this disclosure provides a communication system that may include a host computer. The host computer may include a communication interface configured to receive user data originating from transmissions from a UE to a network node. The network node may include a radio interface and processing circuitry. The processing circuitry of the network node may be configured to perform any step of the method according to the second aspect of this disclosure.

[0060] The eighteenth aspect of this disclosure provides a computer-readable storage medium for storing instructions that, when executed on at least one processor, cause the at least one processor to perform any of the methods according to the first and second aspects of this disclosure.

[0061] The embodiments described herein offer numerous advantages, and the following is a non-exhaustive list of examples of these advantages. In some embodiments herein, methods for msgA PUSCH power control in CFRA are proposed. In some embodiments herein, the proposed methods can take into account flexible signaling dynamically provided in dedicated messages and signaling overhead by reusing some existing parameters from existing parameters. The embodiments herein are not limited to the features and advantages described above. Additional features and advantages will be recognized by those skilled in the art upon reading the following detailed description. Attached Figure Description

[0062] From the following detailed description with reference to the accompanying drawings, by way of example, the above and other aspects, features, and benefits of various embodiments of the present disclosure will become more fully apparent, in which similar reference numerals or letters are used to refer to similar or equivalent elements. The drawings are shown to facilitate a better understanding of the embodiments of the present disclosure and are not necessarily drawn to scale, wherein:

[0063] Figure 1 This is a diagram illustrating the four-step random access process;

[0064] Figure 2aThis is a diagram illustrating the two-step random access process;

[0065] Figure 2b This is a diagram illustrating a CFRA with a two-step RA type;

[0066] Figure 2c This is a diagram illustrating a CBRA with a two-step RA type;

[0067] Figure 3 A flowchart of a method according to an embodiment of the present disclosure is shown;

[0068] Figure 4 A flowchart of a method according to another embodiment of the present invention is shown;

[0069] Figure 5 A flowchart of a method according to another embodiment of the present invention is shown;

[0070] Figure 6 This is a block diagram illustrating an apparatus suitable for implementing some embodiments of the present disclosure;

[0071] Figure 7 This is a block diagram illustrating a terminal device according to an embodiment of the present disclosure;

[0072] Figure 8 This is a block diagram illustrating a network node according to an embodiment of the present disclosure;

[0073] Figure 9 This is a schematic diagram illustrating a wireless network according to some embodiments;

[0074] Figure 10 This is a schematic diagram illustrating a user equipment according to some embodiments;

[0075] Figure 11 This is a schematic diagram illustrating a virtualized environment according to some embodiments;

[0076] Figure 12 This is a schematic diagram illustrating a telecommunications network connected to a host computer via an intermediate network according to some embodiments;

[0077] Figure 13 This is a schematic diagram illustrating a host computer communicating with a user equipment via a base station through a partially wireless connection according to some embodiments;

[0078] Figure 14 This is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments;

[0079] Figure 15 This is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments;

[0080] Figure 16 This is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments; and

[0081] Figure 17 This is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments. Detailed Implementation

[0082] Embodiments of this disclosure are described in detail with reference to the accompanying drawings. It should be understood that these embodiments are discussed only for the purpose of enabling those skilled in the art to better understand and thus implement this disclosure, and not to suggest any limitation on the scope of this disclosure. References to features, advantages, or similar language throughout this specification do not imply that all features and advantages achievable with this disclosure should be included in or in any single embodiment of this disclosure. Rather, references to features and advantages should be understood as meaning that a particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of this disclosure. Furthermore, in one or more embodiments, the features, advantages, and characteristics described in this disclosure may be combined in any suitable manner. Those skilled in the art will recognize that this disclosure can be practiced without one or more particular features or advantages in a particular embodiment. In other instances, additional features and advantages may be recognized in some embodiments, and these additional features and advantages may not be present in all embodiments of this disclosure.

[0083] As used herein, the term "network" or "communication network" refers to a network that follows any suitable wireless communication standard. For example, wireless communication standards can include New Radio (NR), Long Term Evolution (LTE), LTE Advanced, Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), and other wireless networks. CDMA networks can implement radio technologies such as Universal Terrestrial Radio Access (UTRA). UTRA includes other variants of WCDMA and CDMA. TDMA networks can implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA networks can implement radio technologies such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, Ad-hoc networks, wireless sensor networks, etc. In the following description, the terms "network" and "system" are used interchangeably. Furthermore, communication between two devices in a network can be performed according to any suitable communication protocol, including but not limited to wireless or wired communication protocols defined by standards organizations such as the 3rd Generation Partnership Project (3GPP). For example, wireless communication protocols may include first-generation (1G), 2G, 3G, 4G, 4.5G, 5G communication protocols and / or any other currently known or future-developed protocols.

[0084] The term "network node" or "network-side node" refers to a network device in a communication network that has access capabilities, through which terminal devices access the network and receive services. A network node can include a base station (BS), access point (AP), multi-cell / multicast coordination entity (MCE), controller, or any other suitable device in a wireless communication network. A BS can be, for example, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), a next-generation Node B (gNodeB or gNB), a remote radio unit (RRU), a radio head unit (RH), a remote radio head unit (RRH), a repeater, a low-power node (e.g., femtosecond, picosecond), etc.

[0085] Another example of a network node includes multi-standard radio (MSR) equipment such as an MSR BS, a network controller such as a radio network controller (RNC) or base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmission node, a location node, etc. However, more generally, a network node can represent any suitable device (or group of devices) that is capable of, configured, arranged, and / or operable to enable terminal devices to access a wireless communication network and / or provide certain services to terminal devices already connected to the wireless communication network.

[0086] In addition, the terms "network node" or "network-side node" can also refer to network equipment with core network functions. A network node can refer to a Mobility Management Entity (MME) or a Mobile Switching Center (MSC).

[0087] The term "terminal device" refers to any end device that can access a communication network and receive services from it. By way of example and not limitation, a terminal device refers to a mobile terminal, user equipment (UE), or other suitable device. A UE can be, for example, a subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices can include, but are not limited to, portable computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback devices, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable devices, personal digital assistants (PDAs), portable computers, desktop computers, wearable terminal devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEE), laptop installed devices (LME), USB dongles, smart devices, wireless premises equipment (CPE), etc. In the following description, the terms "terminal device," "terminal," "user equipment," and "UE" are used interchangeably. As an example, a terminal device can represent a UE configured to communicate according to one or more communication standards published by 3GPP, such as 3GPP's LTE or NR standards. As used herein, a “user equipment” or “UE” may not necessarily have a “user” in relation to a human user who owns and / or operates the associated device. In some embodiments, a terminal device may be configured to send and / or receive information without direct human interaction. For example, when triggered by an internal or external event, or in response to a request from a communication network, a terminal device may be designed to send information to the network according to a predetermined schedule. Alternatively, a UE may represent a device intended for sale to a human user or operated by a human user but which may not initially be associated with a particular human user.

[0088] As another example, in the Internet of Things (IoT) scenario, a terminal device can represent a machine or other device that performs monitoring and / or measurement, and transmits the results of such monitoring and / or measurement to another terminal device and / or network device. In this case, the terminal device can be a machine-to-machine (M2M) device, which in the 3GPP context can be referred to as a machine-type communication (MTC) device. As a specific example, a terminal device can be a UE that implements the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices (e.g., electricity meters, industrial machinery) or household or personal appliances (e.g., refrigerators, televisions), personal wearable devices (e.g., watches), etc. In other scenarios, a terminal device can represent a vehicle or other device capable of monitoring and / or reporting its operational status or other functions related to its operation.

[0089] As used in this article, downlink (DL) transmission refers to transmission from network device to terminal device, while uplink (UL) transmission refers to transmission in the opposite direction.

[0090] References to "an embodiment," "embodiment," "exemplary embodiment," etc., in the specification indicate that the described embodiment may include specific features, structures, or characteristics, but not every embodiment necessarily includes such specific features, structures, or characteristics. Furthermore, these phrases do not necessarily refer to the same embodiment. Additionally, when a specific feature, structure, or characteristic is described in connection with an embodiment, whether or not it is explicitly described, it is believed that such features, structures, or characteristics affecting other embodiments are within the knowledge of those skilled in the art.

[0091] It should be understood that while the terms “first” and “second” may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed terms.

[0092] As used in this article, the phrase “at least one of A and B” should be understood as meaning “A only, B only, or both A and B”. The phrase “A and / or B” should be understood as “A only, B only, or both A and B”.

[0093] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” as used herein are also intended to include the plural forms. It will be further understood that, when used herein, the terms “comprising,” “including,” “having,” “owning,” “containing,” and / or “covering” specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0094] Note that the terms used in this article are for ease of description and to distinguish between nodes, devices, or networks, etc. As technology evolves, other terms with similar / identical meanings may also be used.

[0095] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0096] Note that some embodiments of this disclosure are described primarily with respect to 5G or NR specifications, which are used as non-limiting examples of certain exemplary network configurations and system deployments. Therefore, the descriptions of the exemplary embodiments given herein specifically refer to terms directly related to them. Such terms are used only in the context of the presented non-limiting examples and embodiments and are not intended to limit this disclosure in any way. Rather, any other system configuration or radio technology may be used as well, provided that the exemplary embodiments described herein are applicable.

[0097] Figure 2 illustrates the two-step random access procedure, also known as the Type-2 random access procedure. As shown in Figure 2, initial random access is completed in just two steps. Similar to the four-step random access procedure, the terminal equipment (e.g., User Equipment (UE)) detects the synchronization signals (SS) in the Physical Broadcast Channel (PBCH), which include the Primary Synchronization Signal (PSS) and the Secondary Synchronization Signal (SSS), and decodes the system information broadcast in the Radio Resource Control (RRC) message, which includes the Remaining Minimal System Information (RMSI) and Other System Information (OSI). In the first step, the UE sends a request message (Message A, MsgA) for random access to the base station. As the second step, the UE receives a response (Message B, MsgB) from the base station indicating whether the random access was successful. The request message (MsgA) may include the RACH preamble and PUSCH.

[0098] Specifically, message A (msgA) may include a random access preamble along with higher-layer data on the PUSCH, such as a Radio Resource Control (RRC) connection request that may have some small payload. Message B (MsgB) may include UE identifier allocation, timing advance information, and contention resolution messages, etc.

[0099] In this two-step RACH process, before the UE receives the random access response (message B), the preamble and PUSCH will be sent by the UE in a message called message A.

[0100] At the NR RAN#85 meeting, as directed in RP-192330 (Revised work item proposal: two-step RACH for NR, Newport Beach, USA, Sept. 16-20, 2019), the contents of which are hereby incorporated in their entirety by reference, we agree to support the CFRA two-step RACH.

[0101] For the transmission of msgA PUSCH, i.e., the PUSCH portion of msgA, the concept of a PUSCH resource unit has been introduced. This PUSCH resource unit consists of the time-frequency radio resources used for transmission and the DMRS (demodulation reference signal) sequence configuration. The receiver can distinguish between two simultaneous msgA PUSCH transmissions because different PUSCH resource units have been used for both simultaneous transmissions. The concept of PUSCH timing has also been introduced, where PUSCH timing consists of the time-frequency radio resources used for transmitting the msgA PUSCH.

[0102] In four-step and two-step random access, random access can be performed in two different ways: contention-based random access (CBRA) and contention-free random access (CFRA). The difference lies in which preamble is used. In contention-based access, the UE randomly selects a preamble from a set of preambles. If two UEs select the same preamble, a conflict may occur. In contention-free access, the network provides the UE with a specific preamble, and because it is given by the network, this ensures that two UEs will not select the same preamble, thus preventing conflicts. CBRA can be used when a UE is in an idle / inactive state and wants to enter a connected state, while CFRA can be used for handover and / or during beam failure.

[0103] Figure 2b This is a diagram illustrating a CFRA with a two-step RA type. Figure 2c This is a diagram illustrating a CBRA with a two-step RA type.

[0104] A two-step RA type MsgA includes a preamble on the PRACH and a payload on the PUSCH. After the MsgA transmission, the UE monitors the network response within a configured window. For CFRA, as... Figure 2b As shown, when a network response is received, the UE terminates the random access procedure. For CBRA, as... Figure 2c As shown, if contention resolution is successful upon receiving a network response, the UE terminates the random access procedure; however, if a backoff indication is received in MsgB, the UE performs the Msg3 transmission and monitors contention resolution. If contention resolution fails after the Msg3 (re)transmission, the UE returns to the MsgA transmission.

[0105] Power control configuration for msg3 PUSCH

[0106] To address near-far effects and mitigate inter-channel interference, power control for each channel and signal is required in the uplink for NR.

[0107] For PUSCH transmission on active UL BWP (bandwidth portion) b of carrier f in serving cell c, the UE first scales the transmission power P by the ratio of the number of antenna ports with non-zero PUSCH transmission power to the number of antenna ports configured for the PUSCH transmission scheme. PUSCH,b,f,c (i,j,q d linear values ​​of l) The UE distributes the generated scaling power evenly across the antenna port, where the UE transmits PUSCH at non-zero power.

[0108] Formula (1) below is used for the transmit power of all PUSCH transmissions in NR Release 15, see Section 7.1 of 3GPP TS 38.213V16.0.0 for details.

[0109] The power of the PUSCH in the transmission timing i on the active UL BWP b of carrier f in serving cell c is adjusted using the parameter set configuration with index j and the PUSCH power control state with index l: in, ·P CMAX,f,c (i) is the maximum output power configured for the UE in [3GPP TS 38.101-1], [3GPP TS 38.101-2] and [3GPP TS 38.101-3] for the carrier f of the serving cell c in PUSCH transmission timing i. · μ is the bandwidth allocated to PUSCH resources, expressed in resource blocks, for PUSCH transmission on carrier f of serving cell c during active UL BWPb, and μ is the SCS configuration defined in [3GPP TS 38.211]. For K S =1.25, then For K S =0, then Δ TF,b,f,c (i) = 0 where for each carrier f and each UL BWPb of the serving cell c, K S Provided by deltaMCS. Active UL BWPb, BPRE, and [other parameters] for each carrier f and each serving cell c. Calculated as follows -For PUSCH with UL-SCH data And for CSI transmission in PUSCH without UL-SCH data, in • C is the number of transmitted code blocks, K r This refers to the size of code block r, N RE It is the quantity of resource elements, which is determined as in This refers to the number of symbols i during PUSCH transmission on carrier f of serving cell c, specifically the number of symbols i during active UL BWPb transmission. This refers to the number of subcarriers in PUSCH symbol j that exclude DM-RS subcarriers and phase-tracking RS samples [3GPP TS 38.211]. And C,K r It is defined in [3GPP TS 38.212]. • When PUSCH includes UL-SCH data, And as described in Section 9.3, when PUSCH includes CSI but not UL-SCH data, ·Q m R is the modulation order, and R is the target code rate. As described in [3GPP TS 38.214], they are provided by the DCI format that schedules PUSCH transmissions that include CSI but not UL-SCH data.

[0110] In addition, for msg3, other relevant parameters in the formula used for power control are considered in the 4-step RACH process in NR version 15 as follows. Parameter 1 P O_PUSCH,b,f,c (j), which is composed of component P O_NOMINAL_PUSCH,f,c (j) and component P O_UE_PUSCH,b,f,c The sum of (j) constitutes the message. And for message 3, j = 0, P...O_UE_PUSCH,f,c (0) = 0 and P O_NOMINAL_PUSCH,f,c (0)=P O_PRE +Δ PREAMBLE_Msg3 The parameter preambleReceivedTargetPower [see 3GPP TS 38.321 V15.8.0, the entire contents of which are incorporated herein by reference] (for P O_PRE ) and msg3-DeltaPreamble (for Δ PREAMBLE_Msg3 It is provided by a higher layer for the carrier f of the serving cell. Parameter 2 α b,f,c (j), j = 0, if provided, α b,f,c (0) is the value of the higher-level parameter msg3-Alpha; otherwise, α b,f,c (0) = 1. Parameter 3 PL b,f,c (q d This refers to downlink path loss estimation. For msg3 PUSCH, the UE uses the same RS (Reference Signal) resource index q as the corresponding PRACH (Physical Random Access Channel) for transmission. d Parameter 4 f b,f,c (i,l) represents the PUSCH power control adjustment state. For Msg3 PUSCH, l = 0. as well as, f b,f,c (0,l)=ΔP rampup,b,f,c +δ msg2,b,f,c , where l = 0 and -δ msg2,b,f,c It is the TPC command value indicated in the random access response grant of the random access response message corresponding to the active UL BWPb transmitted on the PRACH of carrier f in serving cell c, and - and ΔP rampuprequested,b,f,c Provided by a higher layer, and corresponding to the total power ramp-up requested by the higher layer from the first to the last random access preamble for carrier f in serving cell c. Δ represents the bandwidth allocated to PUSCH resources, expressed in terms of the number of resource blocks, for the first PUSCH transmission on carrier f of serving cell c in an active UL BWPb. TF,b,f,c (0) is the power adjustment for the first PUSCH transmission on the active UL BWPb of carrier f in serving cell c.

[0111] Here are some dedicated signaling messages (i.e., not broadcast signaling) copied from 3GPP TS 38.331 V15.8.0, which are sent from the base station to the UE in connected mode: msg3-Alpha A dedicated alpha value for msg3 PUSCH. Corresponds to the L1 parameter 'alpha-ue-pusch-msg3' (see 3GPP TS 38.213, Section 7.1). When this field is not present, the UE applies the value 1. delta MCS Indicates whether delta MCS is applied. When this field is absent, the UE applies Ks=0 in the delta_TFC formula used for PUSCH. This corresponds to the L1 parameter 'deltaMCS-Enabled' (see 3GPP TS 38.213, Section 7.1).

[0112] Power control of msgA PUSCH in two-step CBRA

[0113] For a two-step RA (random access), during the MsgA PUSCH retransmission, for the msgA PUSCH in CBRA, the MsgA PUSCH Tx (transmission) power in transmission instance i is P. PUSCH (i), where Where P CMAX ,preambleReceivedTargetPower(for the P in the previous section) O_PRE ), The meanings of PL(i) are the same as those described in the previous section.

[0114] Power growth component Δ rampup (i) is given by the following formula, where the variable PREAMPLE_POWER_RAMPING_COUNTER starts at zero for the first transmission of msgA PUSCH and increases by one for each subsequent retransmission of msgA PUSCH.

[0115] Table 1 shows the three parameters for each BWP configuration used for msgA PUSCH control. Table 1

[0116] During the two-step RA process, the preamble and msgA PUSCH are sent by the UE in a message called message A. The allocation of msgA PUSCH resources for CFRA can typically be as follows. The PUSCH resources associated with the dedicated preamble for two-step CFRA are configured to the UE via dedicated signaling (i.e., not included in SIB1 (System Information Block Type 1)). To handle near-far effects and mitigate inter-channel interference, uplink for NR requires power control for each channel and signal. However, there is no solution for power control of the msgA PUSCH in CFRA.

[0117] To overcome or mitigate the aforementioned or other problems, some embodiments of this disclosure propose solutions for power control of msgA PUSCH in CFRA. The solutions proposed according to some embodiments take into account flexible signaling dynamically provided in dedicated messages and, consequently, signaling overhead through the reuse of some parameters from existing parameters.

[0118] Figure 3 A flowchart of a method according to an embodiment of the present disclosure is shown, which can be performed by means implemented in / as a terminal device or communicatively coupled to a terminal device. Thus, the means can provide components for completing various parts of method 300, as well as components for combining with other components to complete other processes.

[0119] In block 302, the terminal device can obtain at least one power control parameter, which will be used for a request message for contention-free random access (CFRA). The power of the CFRA request message can be controlled based on at least one power control parameter. The request message may include a random access channel (RACH) preamble and a physical uplink shared channel (PUSCH). The RACH preamble can be configured to the terminal device via dedicated signaling. The dedicated signaling can be any suitable dedicated signaling, such as the RACH-ConfigDedicated information element (IE) in a radio resource control (RRC) message as described in 3GPP TS36.331 V15.8.0 (the disclosure of which is incorporated herein by reference in its entirety). The CFRA can be any suitable random access. In one embodiment, the CFRA can be a two-step CFRA. The request message can be the MsgA of a two-step CFRA.

[0120] In one embodiment, at least one power control parameter can be used to calculate the power of the PUSCH of a request message. The at least one power control parameter can be any suitable power control parameter that can be used to calculate the power of the PUSCH of a request message, such as any parameter shown in the formula above. At least one power control parameter can be configured to the terminal device in various ways. For example, the power control parameter can be pre-configured in the terminal device. The power control parameter can be sent to the terminal device in dedicated signaling. The power control parameter can be sent to the terminal device in broadcast signaling. The power control parameter can be reused from other power control parameters used for other messages, and other power control parameters can be configured to the terminal device in dedicated signaling or broadcast signaling.

[0121] In one embodiment, the at least one power control parameter may include at least one of the following: one or more power control parameters configured in dedicated signaling; one or more power control parameter configurations for the PUSCH in a two-step contention-based random access (CBRA); and one or more power control parameter configurations for the PUSCH in a four-step random access. The dedicated signaling may be any suitable dedicated signaling, such as the RACH-ConfigDedicated information element (IE) in a Radio Resource Control (RRC) message as described in 3GPP TS36.331 V15.8.0. The one or more power control parameter configurations for the PUSCH in a two-step contention-based random access (CBRA) may be any suitable power control parameter configurations for the PUSCH in a two-step CBRA as described above. The one or more power control parameter configurations for the PUSCH in a four-step random access may be any suitable power control parameter configurations for the PUSCH in a four-step random access as described above.

[0122] In one embodiment, dedicated signaling for the preamble and dedicated signaling for one or more power control parameters may be in an RRC message, such as in the same IE (e.g., RACH-ConfigDedicatedIE) within an RRC message.

[0123] In one embodiment, one or more power control parameters configured in the dedicated signaling may include at least one of the following: - The power offset of the PUSCH relative to the preamble receive target power (e.g., corresponding to Δ) MsgA_PUSCH ); - A dedicated alpha value for PUSCH (e.g., corresponding to α in the formula), where alpha is a scaling factor for path loss; - Power ramping step used for PUSCH (e.g., corresponding to MsgApowerRampingStep); - An indication of whether a delta modulation and coding scheme (MCS) is applied; - Whether to enable an indication with cumulative transmit power control (TPC); and - TPC commands used for PUSCH.

[0124] In one embodiment, when the power offset of the PUSCH relative to the preamble receive target power is configured in dedicated signaling, the power offset of the PUSCH relative to the preamble receive target power configured in dedicated signaling is used to calculate the power of the PUSCH of the request message.

[0125] In one embodiment, when the power offset of the PUSCH relative to the preamble receive target power is not present in the dedicated signaling and the msgADeltaPreamble in the two-step CBRA is configured, the msgADeltaPreamble in the two-step CBRA is used to calculate the power of the PUSCH of the request message.

[0126] In one embodiment, when the power offset of the PUSCH relative to the preamble receive target power is not present in dedicated signaling and the msgADeltaPreamble is not present in two-step CBRA, but the msg3-DeltaPreamble is configured in four-step random access, the msg3-DeltaPreamble in four-step random access is used to calculate the PUSCH power of the request message.

[0127] In one embodiment, the range of the power offset value configured in the dedicated signaling relative to the preamble receive target power of the PUSCH may include -1dB, 0dB, 1dB, 2dB, 3dB, 4dB, 5dB, and 6dB. In other embodiments, the range of the power offset value may include any other value.

[0128] In one embodiment, when msgADeltaPreamble is configured in a two-step CBRA, the power of the PUSCH of the request message can be calculated using msgADeltaPreamble in a two-step CBRA.

[0129] In one embodiment, when the msg3-DeltaPreamble in four-step random access is configured, the msg3-DeltaPreamble in four-step random access can be used to calculate the power of the PUSCH of the request message.

[0130] In one embodiment, when a dedicated alpha value for PUSCH is configured in dedicated signaling, the dedicated alpha value for PUSCH configured in dedicated signaling can be used to calculate the power of the PUSCH of the request message.

[0131] In one embodiment, when there is no dedicated alpha value for PUSCH in the dedicated signaling and msgA-Alpha in the two-step CBRA is configured, the PUSCH of the power request message can be calculated using msgA-Alpha in the two-step CBRA.

[0132] In one embodiment, when there is no dedicated alpha value for PUSCH in the dedicated signaling, there is no msgA-Alpha in the two-step CBRA, and msg3-Alpha is configured in the four-step random access, the msg3-Alpha in the four-step random access can be used to calculate the power of the PUSCH of the request message.

[0133] In one embodiment, when the dedicated alpha value for PUSCH is absent in the dedicated four-step random access for PUSCH, the msgA-Alpha value is absent in the two-step CBRA, and the msg3-Alpha value is absent in the four-step random access, the dedicated alpha value for PUSCH can be set to 1.

[0134] In one embodiment, a range of dedicated alpha values ​​configured in dedicated signaling for PUSCH can be enumerated, for example, {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1}. The value alpha0 corresponds to the value 0, alpha04 to the value 0.4, alpha05 to the value 0.5, alpha06 to the value 0.6, alpha07 to the value 0.7, alpha08 to the value 0.8, alpha09 to the value 0.9, alpha1 to the value 1, and so on. In other embodiments, the range of dedicated alpha values ​​may include any other suitable enumerated values.

[0135] In one embodiment, when msgA-Alpha in a two-step CBRA is configured, the power of the PUSCH of the request message can be calculated using msgA-Alpha in the two-step CBRA.

[0136] In one embodiment, when msg3-Alpha is configured in four-step random access, msg3-Alpha in four-step random access can be used to calculate the power of the PUSCH of the request message.

[0137] In one embodiment, the range of power increment steps configured in dedicated signaling for PUSCH can be enumerated, for example, {dB0, dB2, dB4, dB6}. dBx represents a power increment step of x dB. In other embodiments, the range of power increment steps may include any other suitable enumerated values.

[0138] In one embodiment, when the msgApreamble-powerRampingStep in the two-step CBRA is configured, the msgApreamble-powerRampingStep in the two-step CBRA can be used to calculate the power of the PUSCH of the request message.

[0139] In one embodiment, when there is no indication of whether delta MCS is applied, Ks = 0 is used in the delta_TFC formula for PUSCH, where Ks is provided by an indication of whether delta MCS is applied for each UL BWP b of each carrier f and serving cell c.

[0140] In one embodiment, when the deltaMCS indication in four-step random access is configured, the deltaMCS indication in four-step random access can be used to calculate the power of the PUSCH of the request message.

[0141] In one embodiment, when a TPC with accumulation is enabled, a TPC command with accumulation is applied.

[0142] In one embodiment, when accumulated TPC is not enabled, the application does not have accumulated TPC commands.

[0143] In one embodiment, TPC with accumulation is enabled when there is no indication in the dedicated signaling whether to enable it.

[0144] In one embodiment, when a tpc-Accumulation indication is configured in four-step random access, the tpc-Accumulation indication in four-step random access can be used to calculate the power of the PUSCH of the request message.

[0145] In embodiments of this disclosure, one or more power control parameters configured in the dedicated signaling include at least one of the following: a power offset of the PUSCH relative to the preamble receive target power; a dedicated alpha value for the PUSCH, where alpha is a scaling factor for path loss; a power increment step size for the PUSCH; an indication of whether a delta modulation and coding scheme (MCS) is applied; an indication of whether transmit power control (TPC) with cumulative output is enabled; and a TPC command for the PUSCH.

[0146] In embodiments of this disclosure, when there is no power offset of the PUSCH relative to the preamble receive target power in the dedicated signaling and a power offset of the PUSCH relative to the preamble receive target power is configured in the two-step CBRA, the power offset of the PUSCH relative to the preamble receive target power in the two-step CBRA is used to calculate the power of the PUSCH of the request message.

[0147] In embodiments of this disclosure, when there is no power offset of the PUSCH relative to the preamble receive target power in the dedicated signaling and no power offset of the PUSCH relative to the preamble receive target power in the two-step CBRA, and a power offset of the PUSCH relative to the preamble receive target power is configured in the four-step random access, the power offset of the PUSCH relative to the preamble receive target power in the four-step random access is used to calculate the power of the PUSCH of the request message.

[0148] In embodiments of this disclosure, the range of values ​​for the power offset of the PUSCH relative to the preamble receive target power configured in dedicated signaling includes -1dB, 0dB, 1dB, 2dB, 3dB, 4dB, 5dB, and 6dB.

[0149] In embodiments of this disclosure, the power offset of the PUSCH relative to the preamble receive target power in the two-step CBRA is used to calculate the power of the PUSCH of the request message.

[0150] In embodiments of this disclosure, the power offset of the PUSCH relative to the preamble receive target power in the four-step random access is used to calculate the power of the PUSCH of the request message.

[0151] In embodiments of this disclosure, when there is no dedicated alpha value for PUSCH in the dedicated signaling and the alpha value in the two-step CBRA is configured, the alpha value in the two-step CBRA is used to calculate the power of the PUSCH of the request message.

[0152] In embodiments of this disclosure, when there is no dedicated alpha value for PUSCH in the dedicated signaling, no alpha value in the two-step CBRA, and an alpha value is configured in the four-step random access, the alpha value in the four-step random access is used to calculate the PUSCH power of the request message.

[0153] In embodiments of this disclosure, when there is no dedicated alpha value for PUSCH in the dedicated signaling, no alpha value in the two-step CBRA, and no alpha value in the four-step random access, the dedicated alpha value for PUSCH is set to 1.

[0154] In the embodiments of this disclosure, the range of dedicated alpha values ​​configured in the dedicated signaling for PUSCH is {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1}, where alpha0 corresponds to 0, alpha04 corresponds to 0.4, alpha05 corresponds to 0.5, alpha06 corresponds to 0.6, alpha07 corresponds to 0.7, alpha08 corresponds to 0.8, alpha09 corresponds to 0.9, and alpha1 corresponds to 1.

[0155] In embodiments of this disclosure, the alpha value in the two-step CBRA is used to calculate the power of the PUSCH of the request message.

[0156] In embodiments of this disclosure, the alpha value in the four-step random access is used to calculate the power of the PUSCH of the request message.

[0157] In the embodiments of this disclosure, the range of the power increment step size configured in the dedicated signaling for PUSCH is {dB0,dB2,dB4,dB6}, where dB0 corresponds to a power increment step size of 0dB, dB2 corresponds to a power increment step size of 0dB, dB4 corresponds to a power increment step size of 0dB, and dB6 corresponds to a power increment step size of 0dB.

[0158] In embodiments of this disclosure, when a power increment step size for PUSCH is configured in a two-step CBRA, the power increment step size for PUSCH in the two-step CBRA is used to calculate the power of the PUSCH of the request message.

[0159] In embodiments of this disclosure, when there is no indication of whether delta MCS is applied, Ks = 0 is used to calculate the power of the PUSCH of the request message, where Ks is provided by the indication of whether delta MCS is applied.

[0160] In embodiments of this disclosure, the delta MCS indicator in four-step random access is used to calculate the power of the PUSCH of the request message.

[0161] In embodiments of this disclosure, when a TPC with accumulation is enabled, a TPC command with accumulation is applied; when a TPC with accumulation is not enabled, a TPC instruction without accumulation is applied; when there is no indication in the dedicated signaling whether a TPC with accumulation is enabled, a TPC with accumulation is enabled.

[0162] In embodiments of this disclosure, the TPC cumulative indication in four-step random access is used to calculate the power of the PUSCH in the request message. The TPC cumulative indication indicates whether the sum of the TPC command values ​​in the set of TPC command values ​​should be used for PUSCH power control.

[0163] In one embodiment, the fields of the TPC command for PUSCH can be sent via signaling in dedicated signaling. The fields of the TPC command can occupy any suitable bit size, such as 2 bits, 3 bits, 4 bits, etc.

[0164] In one embodiment, the 3-bit field of the TPC command for PUSCH can be sent in dedicated signaling. Table 2 shows the TPC command δ for PUSCH. msgAPUscH Examples. Table 2 0 -6 1 -4 2 -2 3 0 4 2 5 4 6 6 7 8

[0165] In one embodiment, a 2-bit field of the TPC command for PUSCH can be sent in dedicated signaling, and there is a mapping between the TPC command field and the absolute value and / or cumulative value. Table 3 shows the TPC commands δ used for PUSCH. msgAPUSCH Examples. Table 3 0 -1 -4 1 0 -1 2 1 1 3 3 4

[0166] In one embodiment, at least one of the power increment step for PUSCH and the TPC command for PUSCH can be used to calculate the power of the PUSCH for the request message. For example, assume that the power of the PUSCH for the request message is calculated using the following formula. If we only consider the power increase of msgA PUSCH, then f b,f,c The (i,l) section will only include the power growth portion. When only dynamic power control is supported, f b,f,c The (i,l) section will only include the dynamic power control portion calculated based on TPC commands. When using both power control methods, both sections will be included in f. b,f,c In (i,l).

[0167] In one embodiment, the dedicated signaling may include at least one of the following: - Dedicated signaling for random access in a Radio Resource Control (RRC) message, such as the RACH-ConfigDedicated information element (IE) in the RRC message; - Switch command messages; - Beam fault recovery message; and - The command uses a two-step CFRA to randomly access the physical downlink control channel (PDCCH).

[0168] In box 304, the terminal device can send a request message for CFRA to the network node.

[0169] In box 306 (optional), when the CFRA is a two-step CFRA, the terminal device can receive a response from the network node indicating whether the CFRA was successful. The response may be a MsgB for a two-step RA.

[0170] Figure 4 A flowchart of a method according to another embodiment of the present disclosure is shown, which can be performed by means implemented in / as a terminal device or communicatively coupled to a terminal device. Therefore, the means can provide components for performing various parts of method 400 and components for combining with other components to perform other processes. For the sake of brevity, the parts already described in the above embodiments will not be repeated here. In this embodiment, the network node is a switching target network node.

[0171] In box 402, the terminal device can receive dedicated signaling from the switching source network node. One or more power control parameters configured in the dedicated signaling can be sent from the switching target network node to the switching source network node.

[0172] In box 404, the terminal device can obtain at least one power control parameter, which will be used in a request message for Contention-Free Random Access (CFRA). Box 404 is similar to... Figure 3 Box 302.

[0173] In box 406, the terminal device can send a request message for CFRA to the target network node for switching. Box 406 is similar to... Figure 3 Box 304.

[0174] In box 408, when the CFRA is a two-step CFRA, the terminal device can receive a response from the target network node indicating whether the CFRA was successful. Box 408 is similar to... Figure 3 Box 306.

[0175] Figure 5 A flowchart of a method according to another embodiment of this disclosure is shown, which can be performed by means implemented in a network node / as a network node or communicatively coupled to a network node. Therefore, the means can provide components for completing various parts of method 500, as well as components for combining with other components to complete other processes. For the sake of brevity, the parts already described in the above embodiments will not be repeated here.

[0176] In box 502, a network node can send at least one power control parameter to an end device. The at least one power control parameter can be sent to the end device via various messages such as dedicated signaling, broadcast signaling, etc. The network node can send the at least one power control parameter to the end device directly or via another network node.

[0177] In one embodiment, the network node is the target network node for handover, which can send one or more power control parameters configured in dedicated signaling to the source network node for handover, and the source network node for handover sends the dedicated signaling to the terminal device.

[0178] In box 504, a network node can receive a request message for Contention-Free Random Access (CFRA) from an end device. For example, the end device can... Figure 3 In block 304, a request message is sent, which the network node can then receive. In one embodiment, the power of the request message for CFRA can be controlled based on at least one power control parameter. In one embodiment, the request message may include a Random Access Channel (RACH) preamble and a Physical Uplink Shared Channel (PUSCH). The RACH preamble can be configured to the terminal device via dedicated signaling.

[0179] In box 506 (optionally), when the CFRA is a two-step CFRA, the network node can send a response to the end device indicating whether the CFRA was successful. The response can be a MsgB of the two-step RA.

[0180] In one embodiment, power control of msgA PUSCH in CFRA may take into account one or more of the following parameters configured separately in dedicated signaling and / or reuse the configuration for msgA PUSCH in CBRA and / or reuse the configuration for msg3. ● Power offset of the msgA PUSCH relative to the preamble receive target power. For example, msgADeltaPreambleCFRA can indicate the power offset of msgA relative to the preamble receive target power PUSCH. If msgADeltaPreambleCFRA is configured, it can be used for power control of the msgA PUSCH in the CFRA. If the msgADeltaPreambleCFRA parameter does not exist, but the msgADeltaPreamble parameter is configured, the end device can reuse the msgADeltaPreamble parameter for power control of the msgA PUSCH in the CFRA. If a 4-step RACH msg3-DeltaPreamble is configured and neither the msgADeltaPreambleCFRA parameter nor the msgADeltaPreamble parameter exists, the end device can reuse the 4-step RACH msg3-DeltaPreamble for power control of the msgA PUSCH in the CFRA. The value of msgADeltaPreambleCFRA can range from integers (-1, 6) in dB. As another example, msgADeltaPreamble used for CBRA in a 2-step RACH can be used for power control of msgAPUSCH in CFRA. ● A dedicated alpha value for the MsgA PUSCH. For example, msgA-AlphaCFRA can indicate a dedicated alpha value for power control of the MsgA PUSCH in CFRA. If the parameter msgA-AlphaCFRA is not present, the end device can use msgA-Alpha for CBRA for power control of the MsgA PUSCH in CFRA if msgA-Alpha is configured. If msg3-Alpha is configured but msgA-Alpha and msgA-AlphaCFRA are not configured, the end device can use msg3-Alpha for power control of the MsgA PUSCH in CFRA. If none of these three parameters are configured, the end device can set msgA-AlphaCFRA to 1. The value of msgA-AlphaCFRA can be in the range of the enumeration {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1}. Value alpha0 corresponds to value 0, value alpha04 corresponds to value 0.4, value alpha05 corresponds to value 0.5, and so on. As another example, msgA-Alpha used for CBRA in 2-step RACH can be used for power control of msgA PUSCH in CFRA. ● Power ramp-up step size for msgA PUSCH. For example, msgApreamble-powerRampingStepCFRA can indicate the power ramp-up step size for msgA PUSCH in CFRA. The value of msgApreamble-powerRampingStepCFRA can range from the enumerated {dB0,dB2,dB4,dB6}. Where dBx represents a power ramp-up step size of x dB. As another example, msgApreamble-powerRampingStep in a 2-step RACH is used for CBRA to indicate the power ramp-up step size for msgA PUSCH in CFRA. ● An indication of whether delta MCS is applied. For example, deltaMCS can indicate whether deltaMCS is applied in CFRA. When the deltaMCS field is not present, the UE applies Ks=0 in the delta_TFC formula used for PUSCH (see 3GPP TS 38.213, Section 7.1). As another example, the deltaMCS indication for msg3 is used to indicate whether delta MCS is applied in CFRA. For example, the terminal device can reuse the deltaMCS parameter indicated in the PUSCH-PowerControl IE defined in 3GPP TS 38.331 V15.8.0. ● Whether to enable TPC with accumulation. As an example, tpc-Accumulation can be transmitted in dedicated signaling. If TPC with accumulation is enabled, the UE applies TPC commands via accumulation. If TPC with accumulation is not enabled, the UE applies TPC commands without accumulation. If the tpc-Accumulation field is not present, TPC accumulation is enabled (see 3GPP TS 38.213 V16.0.0, Section 7.1). As another example, the tpc-Accumulation parameter is indicated in the PUSCH-PowerControl IE defined in 3GPP TS 38.331 V15.8.0. ● The TPC command used for msgA PUSCH in CFRA. As an example, a 3-bit field "TPC command for msgA PUSCH" can be transmitted in dedicated signaling. msgAPUSCH Example TPC commands are shown in Table 2 above. As another example, a 2-bit field "TPC command for msgA PUSCH" can be transmitted in dedicated signaling. msgAPUsCH Map the dedicated signaling of the TPC command field for scheduling PUSCH transmissions to absolute and cumulative δ. msgAPUSCH Example mappings of values ​​are shown in Table 3 above.

[0181] In another embodiment, the power control of msgA PUSCH in CFRA can consider one or both of the following power control methods: -msgA PUSCH power growth - TPC command for msgA PUSCH used for dynamic power control

[0182] For example, if only the power increase of msgA PUSCH is considered, then f b,f,c The (i,l) section will only include the power growth portion. When only dynamic power control is supported, fb,f,c The (i,l) section will only include the dynamic power control portion calculated based on TPC commands. When using both power control methods, both sections will be included in f. b,f,c In (i,l).

[0183] Figure 6 This is a block diagram illustrating an apparatus suitable for practicing some embodiments of the present disclosure. For example, any of the network node and terminal device described above can be implemented as or through apparatus 600.

[0184] Apparatus 600 includes at least one processor 621, such as a DP, and at least one memory 622 coupled to the processor 621. Apparatus 620 may also include a transmitter TX and a receiver RX 623 coupled to the processor 621. Memory 622 stores a program 624. Program 624 may include instructions that, when executed on the associated processor 621, enable apparatus 620 to operate according to embodiments of the present disclosure. Combinations of at least one processor 621 and at least one memory 622 can form a processing apparatus 625 suitable for implementing various embodiments of the present disclosure.

[0185] Various embodiments of this disclosure can be implemented by one or more executable computer programs that are processor 621, software, firmware, hardware, or a combination thereof.

[0186] The memory 622 can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as, by way of non-limiting example, semiconductor-based storage devices, magnetic storage devices and systems, optical storage devices and systems, fixed memory and removable memory.

[0187] The processor 621 may be of any type suitable for the local technical environment and may include one or more of the following: as non-limiting examples, general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), and processors based on multi-core processor architectures.

[0188] In embodiments where the device is implemented as a terminal device or implemented at a terminal device, memory 622 stores instructions executable by processor 621, thereby enabling the terminal device to... Figure 3-4 Operate using either of the methods described in 300 and 400.

[0189] In embodiments where the device is implemented as a network node or at a network node, memory 622 stores instructions executable by processor 621, thereby enabling the network node to... Figure 5 The described method 500 is used for operation.

[0190] Figure 7 This is a block diagram illustrating a terminal device according to an embodiment of the present disclosure. As shown, the terminal device 700 includes an acquisition module 702 and a transmission module 704. The acquisition module 702 can be configured to acquire at least one power control parameter, which will be used for a request message for Contention-Free Random Access Request (CFRA). The transmission module 704 can be configured to send the CFRA request message to a network node. The power of the CFRA request message is controlled based on the at least one power control parameter. The request message includes a Random Access Channel (RACH) preamble and a Physical Uplink Shared Channel (PUSCH). The RACH preamble is configured to be sent to the terminal device via dedicated signaling.

[0191] Figure 8 This is a block diagram illustrating a network node according to an embodiment of the present disclosure. As shown, network node 800 includes a transmitting module 802 and a receiving module 804. The transmitting module 802 can be configured to transmit at least one power control parameter to a terminal device. The receiving module 804 can be configured to receive a request message for contention-free random access (CFRA) from the terminal device. The power of the request message for CFRA is controlled based on at least one power control parameter. The request message includes a random access channel (RACH) preamble and a physical uplink shared channel (PUSCH).

[0192] The term "unit" may have a conventional meaning in the field of electronic devices, electrical equipment and / or electronic equipment, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logic solid-state and / or discrete devices, computer programs or instructions for performing corresponding tasks, processes, calculations, output and / or display functions, such as those described herein.

[0193] Using functional units, terminal devices or network devices do not require fixed processors or memory; any computing and storage resources can be allocated from the terminal devices or network devices in the communication system. The introduction of virtualization and network computing technologies can improve the efficiency of network resource utilization and network flexibility.

[0194] In addition, an exemplary overall communication system including terminal devices and network nodes such as base stations will be described below.

[0195] Embodiments of this disclosure provide a communication system including a host computer, the host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a terminal device. The cellular network includes base stations, such as the network equipment described above, and / or the terminal device described above.

[0196] In embodiments of this disclosure, the system further includes a terminal device configured to communicate with the base station.

[0197] In embodiments of this disclosure, the processing circuitry of the host computer is configured to execute a host computer application to provide user data; the terminal device includes processing circuitry configured to execute a client application associated with the host computer application.

[0198] Embodiments of this disclosure also provide a communication system including a host computer and a base station. The host computer includes a communication interface configured to receive user data transmitted from a terminal device. The transmission is from the terminal device to the base station. The base station is as described above, and / or the terminal device is as described above.

[0199] In embodiments of this disclosure, the processing circuitry of the host computer is configured to execute a host computer application. The terminal device is configured to execute a client application associated with the host computer application, thereby providing user data to be received by the host computer.

[0200] Figure 9 This is a schematic diagram illustrating a wireless network according to some embodiments.

[0201] Although the subjects described herein can be implemented using any suitable components in any suitable type of system, the embodiments disclosed herein are described with respect to wireless networks, for example... Figure 9 The example wireless network shown is for simplicity. Figure 9 The wireless network depicted only includes network 1006, network nodes 1060 (corresponding to network-side nodes) and 1060b, and WDs (corresponding to terminal devices) 1010, 1010b, and 1010c. In practice, the wireless network may also include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device (e.g., a landline telephone, a service provider, or any other network node or terminal device). Among the components shown, network node 1060 and wireless device (WD) 1010 are depicted with additional details. The wireless network can provide communication and other types of services to one or more wireless devices to facilitate access to and / or use of services provided by or via the wireless network.

[0202] A wireless network may include an interface and / or interface with any type of communications, telecommunications, data, cellular and / or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to a specific standard or other type of predefined rules or procedures. Thus, specific embodiments of the wireless network may implement communication standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE) and / or other suitable 2G, 3G, 4G, or 5G standards; Wireless Local Area Network (WLAN) standards such as the IEEE 802.11 standard; and / or any other suitable wireless communication standards such as Global Microwave Access Interoperability (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.

[0203] Network 1006 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WAN), local area networks (LAN), wireless local area networks (WLAN), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

[0204] Network node 1060 and WD 1010 include various components described in more detail below. These components work together to provide network node and / or wireless device functionality, such as providing wireless connectivity in a wireless network. In various embodiments, the wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that can facilitate or participate in communication of data and signals via wired or wireless connections.

[0205] As used herein, a network node refers to a device that is capable of, configured, positioned, and / or operable to communicate directly or indirectly with wireless devices and / or with other network nodes or devices in a wireless network to enable and / or provide wireless access to the wireless devices and / or perform other functions (e.g., management) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points) and base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)). Base stations can be classified based on the coverage they provide (or, in other words, their transmit power levels) and may also be referred to as femtocells, picocells, microcells, or macrocells. A base station can be a relay node or a relay donor node that controls a relay. A network node may also include one or more components (or all components) of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio headend (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. Components of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Another example of a network node includes multi-standard radio (MSR) equipment (e.g., MSR BS), network controllers (e.g., Radio Network Controller (RNC) or Base Station Controller (BSC), Base Transceiver Station (BTS), transport point, transport node), multi-cell / multicast coordination entity (MCE), core network nodes (e.g., MSC, MME), O&M nodes, OSS nodes, SON nodes, location nodes (e.g., E-SMLC), and / or MDT. As another example, a network node can be a virtual network node, as described in more detail below. However, more generally, a network node can represent any suitable device (or group of devices) capable of, configured, deployed, and / or operable to enable wireless devices to access the wireless network and / or provide access to the wireless network to wireless devices or provide certain services to wireless devices already connected to the wireless network.

[0206] exist Figure 9 In the network node 1060, processing circuitry 1070, device-readable medium 1080, interface 1090, auxiliary equipment 1084, power supply 1086, power supply circuitry 1087, and antenna 1062 are included. Although in Figure 9The network node 1060 shown in the example wireless network can represent a device including the illustrated combination of hardware components, but other embodiments may include network nodes with different combinations of components. It should be understood that a network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. Furthermore, while the components of network node 1060 are depicted as a single box within a larger box or a single box nested within multiple boxes, in practice, a network node may include multiple different physical components constituting a single illustrated component (e.g., device-readable medium 1080 may include multiple separate hard disk drives and multiple RAM modules).

[0207] Similarly, network node 1060 may consist of multiple physically separate components (e.g., NodeB components and RNC components, or BTS components and BSC components, etc.), each of which may have its own corresponding components. In some scenarios where network node 1060 includes multiple individual components (e.g., BTS and BSC components), one or more individual components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such scenarios, each unique NodeB and RNC pair may be considered a single, individual network node in certain circumstances. In some embodiments, network node 1060 may be configured to support multiple Radio Access Technologies (RATs). In such embodiments, some components (e.g., separate device-readable media 1080 for different RATs) may be duplicated, and some components may be reused (e.g., the same antenna 1062 may be shared by the RATs). Network node 1060 may also include a variety of illustrated components for various wireless technologies integrated into network node 1060, such as GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies can be integrated into the same or different chips or chipsets and other components within network node 1060.

[0208] Processing circuitry 1070 is configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) provided by a network node as described herein. These operations performed by processing circuitry 1070 may include processing information acquired by processing circuitry 1070, for example, converting the acquired information into other information, comparing the acquired or converted information with information stored in the network node, and / or performing one or more operations based on the acquired or converted information, and making a determination as a result of said processing.

[0209] Processing circuitry 1070 may include a combination of one or more of the following: a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coded logic, which may operate individually or in conjunction with other network node 1060 components (e.g., device-readable medium 1080) to provide network node 1060 functionality. For example, processing circuitry 1070 may execute instructions stored in memory within device-readable medium 1080 or processing circuitry 1070. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 1070 may include a system-on-a-chip (SoC).

[0210] In some embodiments, the processing circuitry 1070 may include one or more of the following: a radio frequency (RF) transceiver circuitry 1072 and a baseband processing circuitry 1074. In some embodiments, the RF transceiver circuitry 1072 and the baseband processing circuitry 1074 may be on separate chips (or chipsets), boards, or units (e.g., radio units and digital units). In alternative embodiments, a portion or all of the RF transceiver circuitry 1072 and the baseband processing circuitry 1074 may be on the same chip or chipset, board, or unit.

[0211] In some embodiments, some or all of the functions described herein as provided by a network node, base station, eNB, or other such network device can be executed by processing circuitry 1070 by executing instructions stored on device-readable medium 1080 or memory within processing circuitry 1070. In alternative embodiments, some or all of the functions can be provided by processing circuitry 1070, for example, in a hard-wired manner, without executing instructions stored on separate or discrete device-readable media. In any of these embodiments, processing circuitry 1070 can be configured to perform the described functions regardless of whether instructions stored on device-readable storage media are executed. The benefits provided by such functions are not limited to processing circuitry 1070 or other components of network node 1060, but are generally enjoyed by network node 1060 as a whole and / or by end users and wireless networks.

[0212] Device-readable medium 1080 may include any form of volatile or non-volatile computer-readable storage, including but not limited to permanent storage devices, solid-state storage, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, optical disc (CD), or digital video disc (DVD)), and / or any other volatile or non-volatile, non-transient device-readable and / or computer-executable storage device. Device-readable medium 1080 may store any suitable instructions, data, or information, including computer programs, software, including one or more of logic, rules, codes, tables, etc., and / or other instructions executable by processing circuitry 1070 and usable by network node 1060. Device-readable medium 1080 may store any calculations performed by processing circuitry 1070 and / or any data received through interface 1090. In some embodiments, the processing circuitry 1070 and the device-readable medium 1080 may be considered integrated.

[0213] Interface 1090 is used for wired or wireless communication of signaling and / or data between network node 1060, network 1006, and / or WD 1010. As shown, interface 1090 includes a port / terminal 1094 for sending and receiving data to and from network 1006 via a wired connection. Interface 1090 also includes radio front-end circuitry 1092, which may be coupled to antenna 1062, or in some embodiments, is part of antenna 1062. Radio front-end circuitry 1092 includes filter 1098 and amplifier 1096. Radio front-end circuitry 1092 may be connected to antenna 1062 and processing circuitry 1070. Radio front-end circuitry 1092 may be configured to modulate the signal transmitted between antenna 1062 and processing circuitry 1070. Radio front-end circuitry 1092 may receive digital data to be transmitted wirelessly to other network nodes or WD. Radio front-end circuitry 1092 may use a combination of filter 1098 and / or amplifier 1096 to convert digital data into radio signals with appropriate channel and bandwidth parameters. The radio signals can then be transmitted via antenna 1062. Similarly, when receiving data, antenna 1062 can collect the radio signals, which are then converted into digital data by radio front-end circuitry 1092. The digital data can then be passed to processing circuitry 1070. In other embodiments, the interface may include different components and / or different combinations of components.

[0214] In some alternative embodiments, network node 1060 may not include a separate radio front-end circuitry 1092; instead, processing circuitry 1070 may include radio front-end circuitry and may be connected to antenna 1062 without a separate radio front-end circuitry 1092. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1072 may be considered part of interface 1090. In still other embodiments, interface 1090 may include one or more ports or terminals 1094, radio front-end circuitry 1092, and RF transceiver circuitry 1072 as part of a radio unit (not shown), and interface 1090 may communicate with baseband processing circuitry 1074, which is part of a digital unit (not shown).

[0215] Antenna 1062 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna 1062 may be coupled to radio front-end circuitry 1090 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 1062 may include one or more omnidirectional, sector, or planar antennas operable to transmit / receive radio signals, for example, between 2 GHz and 66 GHz. Omnidirectional antennas can be used to transmit / receive radio signals in any direction, sector antennas can be used to transmit / receive radio signals from devices within a specific area, and planar antennas may be line-of-sight antennas used to transmit / receive radio signals in a relatively straight line. In some cases, the use of more than one antenna may be referred to as MIMO. In some embodiments, antenna 1062 may be detachable from network node 1060 and may be connected to network node 1060 via an interface or port.

[0216] Antenna 1062, interface 1090, and / or processing circuitry 1070 can be configured to perform any receive operation and / or certain acquire operation described herein as being performed by a network node. Any information, data, and / or signals can be received from a wireless device, another network node, and / or any other network device. Similarly, antenna 1062, interface 1090, and / or processing circuitry 1070 can be configured to perform any transmit operation described herein as being performed by a network node. Any information, data, and / or signals can be transmitted to a wireless device, another network node, and / or any other network device.

[0217] Power supply circuit 1087 may include or be coupled to power management circuitry and is configured to provide power to the components of network node 1060 to perform the functions described herein. Power supply circuit 1087 may receive power from power source 1086. Power source 1086 and / or power supply circuit 1087 may be configured to provide power to the respective components of network node 1060 in a manner suitable for each component (e.g., at the voltage and current levels required by each respective component). Power source 1086 may be included in or outside power supply circuit 1087 and / or network node 1060. For example, network node 1060 may be connected to an external power source (e.g., a power outlet) via input circuitry or an interface (e.g., a cable), thereby supplying power to power supply circuit 1087. As another example, power source 1086 may include a power source in the form of a battery or battery pack, which is connected to or integrated into power supply circuit 1087. The battery can provide backup power if the external power source fails. Other types of power sources, such as photovoltaic devices, may also be used.

[0218] Alternative embodiments of network node 1060 may include, in addition to Figure 9 Additional components beyond those shown may be responsible for providing certain aspects of the network node's functionality, including any of the functions described herein and / or any functions necessary to support the topics described herein. For example, network node 1060 may include a user interface device to allow information input to and output from network node 1060. This allows users to perform diagnostic, maintenance, repair, and other management functions for network node 1060.

[0219] As used herein, a wireless device (WD) means a device capable of, configured, positioned, and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Unless otherwise stated, the term WD may be used interchangeably with User Equipment (UE) herein. Wireless communication may involve sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information through the air. In some embodiments, a WD may be configured to send and / or receive information without direct human-machine interaction. For example, when triggered by an internal or external event, or in response to a request from the network, a WD may be designed to transmit information to the network according to a predetermined schedule. Examples of WDs include, but are not limited to, smartphones, mobile phones, cellular phones, Voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptops, laptop embedded devices (LEEs), laptop-to-vehicle devices (LMEs), smart devices, wireless client devices (CPEs), in-vehicle wireless terminal devices, etc. For example, by implementing 3GPP standards for sidechain communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X), a WD can support device-to-device (D2D) communication, and in this case, it can be referred to as a D2D communication device. As another concrete example, in the Internet of Things (IoT) scenario, a WD can represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another WD and / or a network node. In this case, the WD can be a machine-to-machine (M2M) device, which can be referred to as an MTC device in the 3GPP context. As a specific example, a WD can be a UE that implements the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, such as metering devices like power meters, industrial machinery, or household or personal appliances (e.g., refrigerators, televisions, etc.), and personal wearable devices (e.g., watches, fitness trackers, etc.). In other scenarios, a WD can represent a vehicle or other device capable of monitoring and / or reporting its operating status or other functions associated with its operation. As mentioned above, WD can represent a wireless connection endpoint, in which case the device can be called a wireless terminal. Furthermore, as mentioned above, WD can also be mobile, in which case it can be called a mobile device or mobile terminal.

[0220] As shown in the figure, the wireless device 1010 includes an antenna 1011, an interface 1014, processing circuitry 1020, a device-readable medium 1030, a user interface device 1032, an auxiliary device 1034, a power supply 1036, and a power supply circuit 1037. WD 1010 may include a collection of one or more of the components shown for different wireless technologies supported by WD 1010 (to name just a few, such as GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies). These wireless technologies may be integrated into the same or different chipsets as other components in WD 1010.

[0221] Antenna 1011 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals and connected to interface 1014. In some alternative embodiments, antenna 1011 may be detachable from WD 1010 and connectable to WD 1010 via an interface or port. Antenna 1011, interface 1014, and / or processing circuitry 1020 may be configured to perform any receive or transmit operations described herein as performed by a WD. Any information, data, and / or signals may be received from a network node and / or another WD. In some embodiments, radio front-end circuitry and / or antenna 1011 may be considered as an interface.

[0222] As shown, interface 1014 includes radio front-end circuitry 1012 and antenna 1011. Radio front-end circuitry 1012 includes one or more filters 1018 and amplifiers 1016. Radio front-end circuitry 1014 is connected to antenna 1011 and processing circuitry 1020 and is configured to modulate signals communicating between antenna 1011 and processing circuitry 1020. Radio front-end circuitry 1012 may be coupled to antenna 1011 or a portion thereof. In some embodiments, WD 1010 may not include a separate radio front-end circuitry 1012; instead, processing circuitry 1020 may include radio front-end circuitry and may be connected to antenna 1011. Similarly, in some embodiments, some or all of RF transceiver circuitry 1022 may be considered part of interface 1014. Radio front-end circuitry 1012 can receive digital data that will be transmitted wirelessly to other network nodes or WD. Radio front-end circuitry 1012 may use a combination of filters 1018 and / or amplifiers 1016 to convert digital data into radio signals with appropriate channel and bandwidth parameters. Radio signals can then be transmitted via antenna 1011. Similarly, when receiving data, antenna 1011 can collect radio signals, which are then converted into digital data by radio front-end circuitry 1012. The digital data can then be passed to processing circuitry 1020. In other embodiments, the interface may include different components and / or different combinations of components.

[0223] Processing circuitry 1020 may include a combination of one or more of the following: a microprocessor, controller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coded logic, which may operate to provide WD 1010 functionality, either alone or together with other WD1010 components (e.g., device-readable medium 1030). Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 1020 may execute instructions stored in memory within device-readable medium 1030 or processing circuitry 1020 to provide the functionality disclosed herein.

[0224] As shown in the figure, the processing circuit 1020 includes one or more of the following: an RF transceiver circuit 1022, a baseband processing circuit 1024, and an application processing circuit 1026. In other embodiments, the processing circuit may include different components and / or different combinations of components. In some embodiments, the processing circuit 1020 of WD 1010 may include a System-on-a-Chip (SOC). In some embodiments, the RF transceiver circuit 1022, the baseband processing circuit 1024, and the application processing circuit 1026 may be on a separate chip or chipset. In alternative embodiments, some or all of the baseband processing circuit 1024 and the application processing circuit 1026 may be combined into a single chip or a set of chips, and the RF transceiver circuit 1022 may be on a separate chip or a set of chips. In yet another alternative embodiment, some or all of the RF transceiver circuit 1022 and the baseband processing circuit 1024 may be on the same chip or chipset, and the application processing circuit 1026 may be on a separate chip or chipset. In yet another alternative embodiment, some or all of the RF transceiver circuitry 1022, baseband processing circuitry 1024, and application processing circuitry 1026 may be combined in the same chip or chipset. In some embodiments, the RF transceiver circuitry 1022 may be part of interface 1014. The RF transceiver circuitry 1022 may modulate the RF signals used for processing circuitry 1020.

[0225] In some embodiments, some or all of the functions described herein as being performed by WD can be provided by processing circuitry 1020 executing instructions stored on device-readable medium 1030, which in some embodiments may be computer-readable storage medium. In alternative embodiments, some or all of the functions can be provided by processing circuitry 1020, for example, in a hard-wired manner, without executing instructions stored on separate or discrete device-readable storage media. In any of these particular embodiments, processing circuitry 1020 can be configured to perform the described functions regardless of whether instructions stored on device-readable storage media are executed. The benefits provided by such functions are not limited to processing circuitry 1020 alone or other components of WD 1010, but are generally enjoyed by WD 1010 and / or by end users and wireless networks.

[0226] Processing circuitry 1020 may be configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being performed by WD. These operations performed by processing circuitry 1020 may include processing information acquired by processing circuitry 1020, for example, converting the acquired information into other information, comparing the acquired or converted information with information stored in WD 1010, and / or performing one or more operations based on the acquired or converted information, and making a determination as a result of said processing.

[0227] Device-readable medium 1030 is operable to store computer programs, software, including one or more applications of logic, rules, code, tables, etc., and / or other instructions executable by processing circuitry 1020. Read-readable medium 1030 may include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., optical disc (CD) or digital video disc (DVD)), and / or any other volatile or non-volatile, non-transient device-readable and / or computer-executable storage device that stores information, data, and / or instructions usable by processing circuitry 1020. In some embodiments, processing circuitry 1020 and device-readable medium 1030 may be considered integrated.

[0228] User interface device 1032 can provide components that allow a human user to interact with WD 1010. This interaction can take many forms, such as visual, auditory, tactile, etc. User interface device 1032 can operate to produce outputs to the user and allow the user to provide inputs to WD 1010. The type of interaction can vary depending on the type of user interface device 1032 installed in WD 1010. For example, if WD 1010 is a smartphone, interaction can be via a touchscreen; if WD 1010 is a smart meter, interaction can be via a screen providing usage information (e.g., gallons used) or a speaker providing audible alerts (e.g., if smoke is detected). User interface device 1032 can include input interfaces, devices, and circuitry, as well as output interfaces, devices, and circuitry. User interface device 1032 is configured to allow information to be input into WD 1010 and is connected to processing circuitry 1020 to allow processing circuitry 1020 to process the input information. User interface device 1032 can include, for example, a microphone, proximity sensor or other sensor, keys / buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface device 1032 is also configured to allow information output from WD 1010, and processing circuitry 1020 to output information from WD 1010. User interface device 1032 may include, for example, a speaker, display, vibration circuitry, USB port, headphone jack, or other output circuitry. Using one or more input and output interfaces, devices, and circuitry of user interface device 1032, WD 1010 can communicate with end users and / or wireless networks, allowing them to benefit from the functionality described herein.

[0229] The auxiliary device 1034 is operable to provide more specific functions that are not typically performed by the WD. This may include dedicated sensors for measuring for various purposes, interfaces for additional types of communication such as wired communication, etc. The inclusion and type of components of the auxiliary device 1034 may vary depending on the embodiment and / or scenario.

[0230] In some embodiments, power supply 1036 may be in the form of a battery or battery pack. Other types of power sources may also be used, such as an external power source (e.g., a power outlet), a photovoltaic device, or a battery. WD 1010 may also include power circuitry 1037 for delivering power from power supply 1036 to various accessories of WD 1010 that require power from power supply 1036 to perform any of the functions described or indicated herein. In some embodiments, power circuitry 1037 may include power management circuitry. Power circuitry 1037 may additionally or alternatively be operable to receive power from an external power source; in this case, WD 1010 may be connected to an external power source (e.g., a power outlet) via an interface such as an input circuit or power cord. In some embodiments, power circuitry 1037 may also be used to deliver power from an external power source to power supply 1036. This may be used, for example, to charge power supply 1036. Power circuitry 1037 may perform any formatting, conversion, or other modifications on the power from power supply 1036 to suit the power for the various components of the WD 1010 being powered.

[0231] Figure 10 This is a schematic diagram illustrating a user device according to some embodiments.

[0232] Figure 10 An embodiment of a UE according to the various aspects described herein is illustrated. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and / or operates the associated device. Instead, a UE may represent a device intended to be sold to or operated by a human user but may not or initially be associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device not intended to be sold to or operated by an end user but may be associated with or operated for the benefit of a user (e.g., a smart meter). UE 1100 can be any UE identified by the 3rd Generation Partnership Project (3GPP), including NB-IoT UEs, Machine Type Communication (MTC) UEs, and / or Enhanced MTC (eMTC) UEs. Figure 10 As shown, UE 1100 is an example of a WD configured to communicate according to one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP) (such as 3GPP's GSM, UMTS, LTE, and / or 5G standards). As previously stated, the terms WD and UE are used interchangeably. Therefore, although Figure 10 It is a UE, but the components discussed here also apply to WD, and vice versa.

[0233] exist Figure 10In this embodiment, UE 1100 includes processing circuitry 1101 operatively coupled to input / output interface 1105, radio frequency (RF) interface 1109, network connectivity interface 1111, memory 1115 (including random access memory (RAM) 1117, read-only memory (ROM) 1119, and storage medium 1121, etc.), communication subsystem 1131, power supply 1133, and / or any other components, or any combination thereof. Storage medium 1121 includes operating system 1123, applications 1125, and data 1127. In other embodiments, storage medium 1121 may include other similar types of information. Some UEs may utilize... Figure 10 The components shown may represent all or only a subset of the components. The level of integration between components may vary from one UE to another. Furthermore, some UEs may contain multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0234] exist Figure 10 In this embodiment, processing circuitry 1101 can be configured to process computer instructions and data. Processing circuitry 1101 can be configured to implement any sequential state machine operable to execute machine instructions stored as a machine-readable computer program in memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic and appropriate firmware; one or more stored programs, a general-purpose processor, such as a microprocessor or digital signal processor (DSP), and appropriate software; or any combination thereof. For example, processing circuitry 1101 may include two central processing units (CPUs). Data may be information in a form suitable for computer use.

[0235] In the depicted embodiments, input / output interface 1105 can be configured to provide a communication interface to input devices, output devices, or both input and output devices. UE 1100 can be configured to use output devices via input / output interface 1105. Output devices can use interface ports of the same type as input devices. For example, a USB port can be used to provide input to UE 1100 and output from UE 1100. Output devices can be speakers, sound cards, video cards, displays, monitors, printers, actuators, transmitters, smart cards, other output devices, or any combination thereof. UE 1100 can be configured to use input devices via input / output interface 1105 to allow a user to capture information into UE 1100. Input devices can include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital camcorders, webcams, etc.), microphones, sensors, mice, trackballs, arrow keys, trackpads, scroll wheels, smart cards, etc. Presence-sensitive displays can include capacitive or resistive touch sensors to sense input from the user. For example, a sensor can be an accelerometer, gyroscope, tilt sensor, force sensor, magnetometer, optical sensor, proximity sensor, another similar sensor, or any combination thereof. For example, an input device can be an accelerometer, magnetometer, digital camera, microphone, or optical sensor.

[0236] exist Figure 10 In this configuration, RF interface 1109 can be configured to provide a communication interface to RF components such as transmitters, receivers, and antennas. Network connectivity interface 1111 can be configured to provide a communication interface to network 1143a. Network 1143a may include wired and / or wireless networks, such as local area networks (LANs), wide area networks (WANs), computer networks, wireless networks, telecommunications networks, another similar network, or any combination thereof. For example, network 1143a may include a Wi-Fi network. Network connectivity interface 1111 can be configured to include receiver and transmitter interfaces for communicating with one or more other devices over the communication network according to one or more communication protocols (e.g., Ethernet, TCP / IP, SONET, ATM, etc.). Network connectivity interface 1111 can implement receiver and transmitter functions suitable for communication network links (e.g., optical, electrical, etc.). Transmitter and receiver functions may share circuit components, software, or firmware, or they may be implemented separately.

[0237] RAM 1117 can be configured to interface with processing circuitry 1101 via bus 1102 to provide storage or caching of data or computer instructions during the execution of software programs such as operating systems, applications, and device drivers. ROM 1119 can be configured to provide computer instructions or data to processing circuitry 1101. For example, ROM 1119 can be configured to store invariant low-level system code or data for basic system functions, such as basic input and output (I / O), initiating or receiving keystrokes from a keyboard, which are stored in non-volatile memory. Storage medium 1121 can be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk, optical disk, floppy disk, hard disk, removable magnetic tape, or flash memory drive. In one example, storage medium 1121 may be configured to include operating system 1123, application 1125 (e.g., web browser application, widget or gadget engine, or another application), and data file 1127. Storage medium 1121 may store any of a variety of different operating systems for use by the UE 1100, or a combination of operating systems.

[0238] Storage medium 1121 can be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile optical disc (HD-DVD) drive, an internal hard drive, a Blu-ray disc drive, a holographic digital data storage (HDDS) disc drive, an external mini dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro DIMM SDRAM, smart card memory (e.g., a user identity module or a removable user identity (SIM / RUIM) module), other memory, or any combination thereof. Storage medium 1121 can allow UE 1100 to access computer-executable instructions, applications, etc., stored on temporary or non-temporary storage media to offload or upload data. Manufactured articles (e.g., manufactured articles utilizing communication systems) can be tangibly embodied in storage medium 1121, which can include device-readable media.

[0239] exist Figure 10In this configuration, processing circuitry 1101 can be configured to communicate with network 1143b using communication subsystem 1131. Networks 1143a and 1143b can be the same network, multiple networks, different networks, or multiple networks. Communication subsystem 1131 can be configured to include one or more transceivers for communicating with network 1143b. For example, communication subsystem 1131 can be configured to include one or more transceivers for communicating with one or more remote transceivers of another device capable of wireless communication, such as another WD, UE, or radio access network (RAN) base station, according to one or more communication protocols (e.g., IEEE 802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc.). Each transceiver can include transmitter 1133 and / or receiver 1135 to respectively implement transmitter or receiver functions suitable for the RAN link (e.g., frequency allocation, etc.). Furthermore, transmitter 1133 and receiver 1135 of each transceiver can share circuit components, software, or firmware, or can be implemented separately.

[0240] In the illustrated embodiment, the communication functions of the communication subsystem 1131 may include data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as using a Global Positioning System (GPS) to determine location, another similar communication function, or any combination thereof. For example, the communication subsystem 1131 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 1143b may include wired and / or wireless networks, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network 1143b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 1113 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 1100.

[0241] The features, benefits, and / or functions described herein may be implemented in one of the components of UE 1100 or partitioned across multiple components of UE 1100. Furthermore, the features, benefits, and / or functions described herein may be implemented in any combination of hardware, software, or firmware. In one example, the communication subsystem 1131 may be configured to include any of the components described herein. Additionally, the processing circuitry 1101 may be configured to communicate with any such component via bus 1102. In another example, any such component may be represented by program instructions stored in memory, which, when executed by the processing circuitry 1101, perform the corresponding functions described herein. In another example, the functionality of any such component may be partitioned between the processing circuitry 1101 and the communication subsystem 1131. In yet another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0242] Figure 11 This is a schematic diagram illustrating a virtualized environment according to some embodiments.

[0243] Figure 11 This is a schematic block diagram illustrating a virtualized environment 1200 that can virtualize functionality implemented by some embodiments. In this context, virtualization means creating a virtual version of a device or equipment, which may include virtualized hardware platforms, storage devices, and network resources. As used herein, virtualization can be applied to nodes (e.g., virtualized base stations or virtualized radio access nodes) or devices (e.g., UEs, wireless devices, or any other type of communication equipment) or components thereof, and relates to implementations in which at least a portion of functionality is implemented as one or more virtual components (e.g., through one or more applications, components, functions, virtual machines, or containers running on one or more physical processing nodes in one or more networks).

[0244] In some embodiments, some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines, which are implemented in one or more virtual environments 1200 hosted by one or more hardware nodes 1230. Furthermore, in embodiments where the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), the network node may be fully virtualized.

[0245] The functionality may be implemented by one or more applications 1220 (which may alternatively be referred to as software instances, virtual devices, network functions, virtual nodes, virtual network functions, etc.) operable to implement some of the features, functions, and / or benefits of some embodiments disclosed herein. Applications 1220 operate in a virtualized environment 1200 providing hardware 1230 including processing circuitry 1260 and memory 1290. Memory 1290 stores instructions 1295 executable by processing circuitry 1260, thereby enabling application 1220 to operate to provide one or more of the features, benefits, and / or functions disclosed herein.

[0246] The virtualization environment 1200 includes general-purpose or special-purpose network hardware devices 1230, which include one or more processors or processing circuitry 1260, which may be commercial off-the-shelf (COTS) processors, application-specific integrated circuits (ASICs), or any other type of processing circuitry, including digital or analog hardware components or special-purpose processors. Each hardware device may include memory 1290-1, which may be non-persistent memory for temporarily storing instructions 1295 or software executed by the processing circuitry 1260. Each hardware device may include one or more network interface controllers (NICs) 1270, also referred to as network interface cards, which include physical network interfaces 1280. Each hardware device may also include non-transitory, persistent, machine-readable storage media 1290-2 in which software 1295 and / or instructions executable by the processing circuitry 1260 are stored. Software 1295 may include any type of software, including software for instantiating one or more virtualization layers 1250 (also referred to as hypervisors), software for executing virtual machines 1240, and software that allows them to perform functions, features, and / or benefits related to some of the embodiments described herein.

[0247] Virtual machine 1240 includes virtual processing, virtual memory, virtual network or interface, and virtual storage, and can be run by a corresponding virtualization layer 1250 or hypervisor. Different embodiments of instances of virtual device 1220 can be implemented on one or more virtual machines 1240, and can be implemented in different ways.

[0248] During operation, the processing circuitry 1260 executes software 1295 to instantiate a hypervisor or virtualization layer 1250, which may sometimes be referred to as a virtual machine monitor (VMM). The virtualization layer 1250 can present a virtual operating platform that appears to be network hardware to the virtual machine 1240.

[0249] like Figure 11As shown, hardware 1230 can be a standalone network node with general or specific components. Hardware 1230 may include antenna 12225 and may implement some functions through virtualization. Alternatively, hardware 1230 may be part of a larger hardware cluster (e.g., in a data center or customer premises equipment (CPE)) where many hardware nodes work together and are managed by management and orchestration (MANO) 12100, which, among other things, oversees the lifecycle management of application 1220.

[0250] Hardware virtualization is sometimes referred to as Network Functions Virtualization (NFV). NFV can be used to integrate many types of network devices into industry-standard, high-capacity server hardware, physical switches, and physical storage, which can reside in data centers and client devices.

[0251] In the context of NFV, virtual machine 1240 can be a software implementation of a physical machine running a program as if the program were running on a physical, non-virtualized machine. Each virtual machine 1240, and the portion of the hardware 1230 that executes that virtual machine, whether dedicated to that virtual machine or shared by that virtual machine with other virtual machines 1240, forms a separate virtual network element (VNE).

[0252] Still within the context of NFV, a Virtual Network Function (VNF) is responsible for handling specific network functions running in one or more virtual machines 1240 on top of the hardware network infrastructure 1230 and corresponds to Figure 11 Application 1220.

[0253] In some embodiments, one or more radio units 12200 (each including one or more transmitters 12220 and one or more receivers 12210) may be coupled to one or more antennas 12225. The radio units 12200 may communicate directly with the hardware node 1230 through one or more suitable network interfaces and may be used in conjunction with virtual components to provide a radio-capable virtual node, such as a radio access node or base station.

[0254] In some embodiments, the control system 12230 may be used to implement some signaling, and the control system 12230 may be used instead for communication between the hardware node 1230 and the radio unit 12200.

[0255] Figure 12 This is a schematic diagram illustrating a telecommunications network connected to a host computer via an intermediate network according to some embodiments.

[0256] Reference Figure 12According to an embodiment, the communication system includes a telecommunications network 1310, such as a 3GPP-type cellular network, which includes an access network 1311, such as a radio access network, and a core network 1314. The access network 1311 includes multiple base stations 1312a, 1312b, and 1312c, such as NBs, eNBs, gNBs, or other types of wireless access points, each base station defining a corresponding coverage area 1313a, 1313b, or 1313c. Each base station 1312a, 1312b, or 1312c can be connected to the core network 1314 via a wired or wireless connection 1315. A first UE 1391 located in coverage area 1313c is configured to wirelessly connect to or be paged by the corresponding base station 1312c. A second UE 1392 located in coverage area 1313a can wirelessly connect to the corresponding base station 1312a. Although multiple UEs 1391 and 1392 are shown in this example, the disclosed embodiments are equally applicable to situations where a single UE is in the coverage area or a single UE is connected to the corresponding base station 1312.

[0257] Telecommunications network 1310 is itself connected to host computer 1330, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server cluster. Host computer 1330 may be under the ownership or control of the service provider, or may be operated by the service provider or on behalf of the service provider. Connections 1321 and 1322 between telecommunications network 1310 and host computer 1330 may extend directly from core network 1314 to host computer 1330, or may extend via optional intermediate network 1320. Intermediate network 1320 may be one or a combination of more than one of the following: a public network, a private network, or a hosted network; intermediate network 1320 may be a backbone network or the Internet, if any; in particular, intermediate network 1320 may include two or more subnetworks (not shown).

[0258] Figure 12The communication system as a whole enables connectivity between connected UEs 1391 and 1392 and host computer 1330. This connectivity can be described as an over-the-top (OTT) connection 1350. Host computer 1330 and connected UEs 1391 and 1392 are configured to transmit data and / or signaling via OTT connection 1350 using access network 1311, core network 1314, any intermediate network 1320, and possible further infrastructure (not shown) as intermediate media. OTT connection 1350 can be transparent in the sense that the participating communication devices traversing OTT connection 1350 are unaware of the routes for uplink and downlink communications. For example, base station 1312 may not or need to be informed of past routes for incoming downlink communications containing data originating from host computer 1330 that will be forwarded (e.g., switched) to connected UE 1391. Similarly, base station 1312 does not need to know the future routes for outgoing uplink communications from UE 1391 to host computer 1330.

[0259] Figure 13 This is a schematic diagram illustrating a host computer communicating with a user equipment via a base station through a partial wireless connection, according to some embodiments.

[0260] According to the embodiments, reference will now be made to Figure 13 Example implementations of the UE, base station, and host computer discussed in the preceding paragraphs are described. In the communication system 1400, the host computer 1410 includes: hardware 1415 including a communication interface 1416 configured to establish and maintain wired or wireless connections with interfaces of different communication devices of the communication system 1400. The host computer 1410 also includes processing circuitry 1418, which may have storage and / or processing capabilities. In particular, the processing circuitry 1418 may include: one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The host computer 1410 also includes software 1411, which is stored in or accessible by the host computer 1410 and executable by the processing circuitry 1418. The software 1411 includes host computer applications 1412. Host computer application 1412 can be used to provide services to remote users, such as UE 1430 connected via OTT connection 1450 terminated at UE 1430 and host computer 1410. When providing services to remote users, host computer application 1412 can provide user data sent using OTT connection 1450.

[0261] The communication system 1400 also includes a base station 1420, which is provided in the telecommunications system and includes hardware 1425 that enables it to communicate with the host computer 1410 and the UE 1430. Hardware 1425 may include a communication interface 1426 for establishing and maintaining wired or wireless connections with different communication devices of the communication system 1400, and for communicating with the coverage area served by the base station 1420. Figure 13 The UE 1430 (not shown) establishes and maintains at least the radio interface 1427 of the wireless connection 1470. The communication interface 1426 can be configured to facilitate a connection 1460 to the host computer 1410. The connection 1460 can be direct, or it can be via the core network of the telecommunications system (…). Figure 13 (not shown) and / or via one or more intermediate networks outside the telecommunications system. In the illustrated embodiment, the hardware 1425 of base station 1420 also includes processing circuitry 1428, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. Base station 1420 also has software 1421 stored internally or accessible via an external connection.

[0262] The communication system 1400 also includes the previously mentioned UE 1430. Its hardware 1435 may include a wireless interface 1437 configured to establish and maintain a wireless connection 1470 with a base station serving the coverage area currently occupied by the UE 1430. The hardware 1435 of the UE 1430 also includes processing circuitry 1438, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The UE 1430 further includes software 1431, which is stored in or accessible by the UE 1430 and executable by the processing circuitry 1438. The software 1431 includes a client application 1432. The client application 1432 can be used to provide services to human or non-human users via the UE 1430 with the support of the host computer 1410. In host computer 1410, the executing host computer application 1412 can communicate with the executing client application 1432 by terminating the OTT connection 1450 at UE 1430 and host computer 1410. In providing services to the user, client application 1432 can receive request data from host computer application 1412 and provide user data in response to the request data. OTT connection 1450 can transmit both request data and user data. Client application 1432 can interact with the user to generate the user data it provides.

[0263] Notice, Figure 13The host computer 1410, base station 1420, and UE 1430 shown can communicate with Figure 12 The host computer 1330, one of the base stations 1312a, 1312b, and 1312c, and one of the UEs 1391 and 1392 are similar to or identical to each other. That is to say, the internal operation of these entities can be as follows: Figure 13 As shown, and independently, the surrounding network topology can be Figure 12 The surrounding network topology.

[0264] exist Figure 13 The OTT connection 1450 has been abstractly depicted to illustrate communication between host computer 1410 and UE 1430 via base station 1420, without explicitly referencing any intermediate devices or the precise routing of messages via these devices. The network infrastructure can determine the routing and can be configured to hide it from UE 1430 or the service provider operating host computer 1410, or both. When the OTT connection 1450 is active, the network infrastructure can further make decisions by dynamically changing the routing (e.g., based on load balancing considerations or network reconfiguration).

[0265] The wireless connection 1470 between UE 1430 and base station 1420 is based on the teachings of embodiments described throughout this disclosure. One or more embodiments in various embodiments use OTT connection 1450 to improve the performance of OTT services provided to UE 1430, wherein wireless connection 1470 forms the final segment. More precisely, the teachings of these embodiments can improve latency and thus provide benefits such as reduced user latency.

[0266] Measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors improved by one or more embodiments. Optional network functions may also be available for reconfiguring the OTT connection 1450 between host computer 1410 and UE 1430 in response to changes in measurement results. The measurement procedures and / or network functions for reconfiguring the OTT connection 1450 may be implemented in software 1411 and hardware 1415 of host computer 1410, or in software 1431 and hardware 1435 of UE 1430, or both. In embodiments, sensors (not shown) may be deployed in or associated with communication devices through which the OTT connection 1450 passes; the sensors may participate in the measurement procedure by providing values ​​of the monitored quantities exemplified above or by providing values ​​of other physical quantities, from which software 1411, 1431 may calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 1450 may include message formats, retransmission settings, preferred routing, etc.; reconfiguration need not affect base station 1420, and base station 1420 may be unaware of or unaware of it. This process and functionality are known and practiced in the art. In some embodiments, the measurement may involve proprietary UE signaling, which facilitates the host computer 1410 in measuring throughput, propagation time, latency, etc. The measurement can be implemented in software 1411 and 1431, which uses OTT connection 1450 to transmit messages (especially empty messages or "virtual" messages), while software 1411 and 1431 monitor propagation time, errors, etc.

[0267] Figure 14 This is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments.

[0268] Figure 14 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Figure 12 and Figure 13 Those described. For the sake of brevity in this disclosure, this section includes only references. Figure 14 The accompanying drawings are shown. In step 1510, the host computer provides user data. In sub-step 1511 of step 1510 (which may be optional), the host computer provides user data by executing a host computer application. In step 1520, the host computer initiates a transmission carrying user data to the UE. In step 1530 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station sends the user data carried in the host computer-initiated transmission to the UE. In step 1540 (which may also be optional), the UE executes a client application associated with the host computer application executed by the host computer.

[0269] Figure 15 This is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments.

[0270] Figure 15 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Figure 12 and Figure 13 Those described. For the sake of brevity in this disclosure, only references will be included in this section. Figure 15 The accompanying drawings are shown. In step 1610 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides user data by executing a host computer application. In step 1620, the host computer initiates a transmission carrying the user data to the UE. According to the teachings of the embodiments described throughout this disclosure, the transmission may be via a base station. In step 1630 (which may be optional), the UE receives the user data carried in the transmission.

[0271] Figure 16 This is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments.

[0272] Figure 16 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Figure 12 and Figure 13 Those described. For the sake of brevity in this disclosure, this section includes only references. Figure 16 The accompanying drawings are shown. In step 1710 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1720, the UE provides user data. In sub-step 1721 of step 1720 (which may be optional), the UE provides user data by executing a client application. In sub-step 1711 of step 1710 (which may be optional), the UE executes a client application that provides user data in response to the received input data provided by the host computer. When providing user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which user data is provided, the UE initiates the transmission of user data to the host computer in sub-step 1730 (which may be optional). In step 1740 of the method, the host computer receives user data sent from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

[0273] Figure 17 This is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments.

[0274] Figure 17 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Figure 12 and 13 Those described. For the sake of brevity in this disclosure, this section includes only references. Figure 17 The accompanying drawings are shown. In step 1810 (which may be optional), the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout this disclosure. In step 1820 (which may be optional), the base station initiates a transmission of the received user data to the host computer. In step 1830 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0275] According to one aspect of this disclosure, a computer program product tangibly stored on a computer-readable storage medium and including instructions is provided, which, when executed on at least one processor, cause the at least one processor to perform any of the methods described above.

[0276] According to one aspect of this disclosure, a computer-readable storage medium is provided that stores instructions which, when executed by at least one processor, cause the at least one processor to perform any of the methods described above.

[0277] The embodiments described herein offer numerous advantages, and the following is a non-exhaustive list of examples of these advantages. In some embodiments herein, methods for msgA PUSCH power control in CFRA are proposed. In some embodiments herein, the proposed methods can take into account flexible signaling dynamically provided in dedicated messages and signaling overhead by reusing some existing parameters from existing parameters. The embodiments herein are not limited to the features and advantages described above. Additional features and advantages will be recognized by those skilled in the art upon reading the following detailed description.

[0278] Furthermore, this disclosure may also provide a carrier containing the aforementioned computer program, which may be one of electronic signals, optical signals, radio signals, or a computer-readable storage medium. The computer-readable storage medium may be, for example, an optical disc or electronic storage device, such as RAM (random access memory), ROM (read-only memory), flash memory, magnetic tape, CD-ROM, DVD, Blu-ray disc, etc.

[0279] The techniques described herein can be implemented in various ways, such that the means for implementing one or more functions of the corresponding apparatus described in the embodiments includes not only prior art components, but also components for implementing one or more functions of the corresponding apparatus described together with the embodiments, and it may include separate components for each individual function or components that can be configured to perform two or more functions. For example, these techniques can be implemented in hardware (one or more devices), firmware (one or more devices), software (one or more modules), or a combination thereof. For firmware or software, implementation can be accomplished by modules (e.g., processes, functions, etc.) that perform the functions described herein.

[0280] Exemplary embodiments of this document have been described above with reference to block diagrams and flowcharts illustrating methods and apparatus. It will be understood that each block in the block diagrams and flowcharts, as well as combinations of blocks in the block diagrams and flowcharts, can be implemented by various components including computer program instructions. These computer program instructions can be loaded onto a general-purpose computer, a special-purpose computer, or other programmable data processing equipment to produce a machine, such that the instructions, which execute on the computer or other programmable data processing equipment, create components for implementing the functions specified in the flowchart blocks or blocks.

[0281] Furthermore, although the operations are depicted in a specific order, this should not be construed as requiring that these operations be performed in the specific order shown or sequentially, or requiring that all illustrated operations be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the foregoing discussion, these should not be construed as limiting the scope of the subject matter described herein, but rather as descriptions of features that may be specific to particular embodiments. Certain features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0282] While this specification contains numerous specific implementation details, these should not be construed as limiting the scope of any implementation or the scope that may be claimed, but rather as descriptions of features specific to particular embodiments that may be specific to a particular implementation. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments. Furthermore, while the foregoing features may be described as functioning in certain combinations, or even initially claimed in this way, in certain circumstances one or more features from the claimed combination may be removed from the combination, which may be for sub-combinations or variations thereof.

[0283] It will be apparent to those skilled in the art that the inventive concept can be implemented in various ways as technology advances. The above embodiments are given for description purposes only and not for limitation of this disclosure. It should be understood that, as will be readily apparent to those skilled in the art, modifications and variations can be made without departing from the spirit and scope of this disclosure. Such modifications and variations are considered to be within the scope of this disclosure and the appended claims. The scope of protection of this disclosure is defined by the appended claims.

Claims

1. A method (300) implemented at a terminal device, the method comprising: Obtain (302) at least two power control parameters, which will be used for a request message for a two-step contention-free random access CFRA; and Send the request message (304) for the two-step CFRA to the network node; Wherein, the power of the request message for the two-step CFRA is controlled based on the at least two power control parameters; and The request message includes a random access channel (RACH) preamble and a physical uplink shared channel (PUSCH). The at least two power control parameters include: A dedicated alpha value for PUSCH is configured in the dedicated signaling for the two-step CFRA, wherein the dedicated alpha value is a scaling factor for path loss. The power offset of the PUSCH relative to the preamble receive target power configured in the broadcast signaling, and The power increment step size for PUSCH in two-step CFRA configured in dedicated signaling.

2. The method according to claim 1, wherein, The at least two power control parameters are used to calculate the power of the PUSCH in the request message.

3. The method according to claim 1, wherein, The at least two power control parameters also include at least one of the following: Indication on whether to apply delta modulation and coding scheme (MCS); Whether to enable the indication of TPC with cumulative transmit power control; and TPC commands used for PUSCH.

4. The method according to claim 1 or 2, in, The range of values ​​for the power offset of the PUSCH relative to the preamble receive target power configured in the broadcast signaling includes -1dB, 0dB, 1dB, 2dB, 3dB, 4dB, 5dB, and 6dB.

5. The method according to claim 1 or 2, in, The power offset of the PUSCH relative to the preamble receive target power in the two-step CBRA is used to calculate the power of the PUSCH of the request message.

6. The method according to claim 1 or 2, in, The power offset of the PUSCH relative to the preamble receive target power in the four-step random access is used to calculate the power of the PUSCH in the request message.

7. The method according to claim 1 or 2, in, The range of the dedicated alpha value configured in the dedicated signaling for PUSCH is {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1}, where alpha0 corresponds to 0, alpha04 corresponds to 0.4, alpha05 corresponds to 0.5, alpha06 corresponds to 0.6, alpha07 corresponds to 0.7, alpha08 corresponds to 0.8, alpha09 corresponds to 0.9, and alpha1 corresponds to 1.

8. The method according to claim 1 or 2, in, The range of the power increment step size configured for PUSCH in the dedicated signaling is {dB0, dB2, dB4, dB6}, where dB0 corresponds to a power increment step size of 0dB, dB2 corresponds to a power increment step size of 2dB, dB4 corresponds to a power increment step size of 4dB, and dB6 corresponds to a power increment step size of 6dB.

9. The method according to claim 3, in, When the indication of whether delta MCS is applied is not present, Ks = 0 is used to calculate the power of the PUSCH of the request message, wherein Ks is provided by the indication of whether delta MCS is applied.

10. The method according to claim 3, wherein, In four-step random access, the delta MCS indicator is used to calculate the power of the PUSCH in the request message.

11. The method according to claim 3, wherein, When TPC with accumulation is enabled, apply TPC commands with accumulation; When TPC with accumulation is not enabled, apply TPC commands without accumulation; When there is no indication in the dedicated signaling whether to enable TPC with accumulation, TPC with accumulation is enabled.

12. The method according to claim 3, wherein, In four-step random access, the TPC cumulative indication is used to calculate the power of the PUSCH in the request message, and the TPC cumulative indication is an indication of whether the sum of the TPC command values ​​in the set of TPC command values ​​should be used for PUSCH power control.

13. The method according to claim 3, wherein, The dedicated signaling transmits the field of the TPC command used for PUSCH.

14. The method according to claim 13, wherein, In the dedicated signaling, the signaling transmits the 3-bit field of the TPC command used for PUSCH.

15. The method according to claim 13, wherein, In the dedicated signaling, the signaling transmits a 2-bit field of the TPC command for PUSCH, and there is a mapping between the TPC command field and absolute and / or cumulative values.

16. The method according to claim 3, wherein, The power increment step for PUSCH and at least one of the TPC commands for PUSCH are used to calculate the power of the PUSCH in the request message.

17. The method according to any one of claims 1-3, wherein, The dedicated signaling includes at least one of the following: Dedicated signaling for random access in a Radio Resource Control (RRC) message; Toggle command messages; Beam fault recovery message; and The command uses a two-step CFRA to randomly access the physical downlink control channel (PDCCH).

18. The method according to claim 17, wherein, The dedicated signaling used for random access is the RACH-ConfigDedicated information element (IE).

19. The method according to any one of claims 1 to 3, wherein, The network node is the target network node to be switched, and the method further includes: (402) The dedicated signaling is received from the switching source network node, wherein the at least two or more power control parameters configured in the dedicated signaling are sent from the switching target network node to the switching source network node.

20. The method according to any one of claims 1 to 3, further comprising: Receive (306) a response from the network node indicating whether the two-step CFRA was successful.

21. A method (500) implemented at a network node, the method comprising: Send at least two power control parameters (502) to the terminal device; and Receive (504) a request message for two-step contention-free random access CFRA from the terminal device; Specifically, the power of the request message for the two-step CFRA is controlled based on the at least two power control parameters; and The request message includes a random access channel (RACH) preamble and a physical uplink shared channel (PUSCH). The at least two power control parameters include: A dedicated alpha value for PUSCH is configured in the dedicated signaling for the two-step CFRA, wherein the dedicated alpha value is a scaling factor for path loss. The power offset of the PUSCH relative to the preamble receive target power configured in the broadcast signaling, and The power increment step size for PUSCH in two-step CFRA configured in dedicated signaling.

22. The method according to claim 21, wherein, The at least two power control parameters are used to calculate the power of the PUSCH in the request message.

23. The method according to claim 21, wherein, The at least two power control parameters also include at least one of the following: Indication on whether to apply delta modulation and coding scheme (MCS); Whether to enable the indication of TPC with cumulative transmit power control; and TPC commands used for PUSCH.

24. The method according to claim 21 or 22, in, The range of values ​​for the power offset of the PUSCH relative to the preamble receive target power configured in the broadcast signaling includes -1dB, 0dB, 1dB, 2dB, 3dB, 4dB, 5dB, and 6dB.

25. The method according to claim 21 or 22, in, The power offset of the PUSCH relative to the preamble receive target power in the two-step CBRA is used to calculate the power of the PUSCH of the request message.

26. The method according to claim 21 or 22, in, The power offset of the PUSCH relative to the preamble receive target power in the four-step CBRA is used to calculate the power of the PUSCH of the request message.

27. The method according to claim 21 or 22, in, The range of the dedicated alpha value configured in the dedicated signaling for PUSCH is {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1}, where alpha0 corresponds to 0, alpha04 corresponds to 0.4, alpha05 corresponds to 0.5, alpha06 corresponds to 0.6, alpha07 corresponds to 0.7, alpha08 corresponds to 0.8, alpha09 corresponds to 0.9, and alpha1 corresponds to 1.

28. The method according to claim 21 or 22, in, The range of the power increment step size configured for PUSCH in the dedicated signaling is {dB0, dB2, dB4, dB6}, where dB0 corresponds to a power increment step size of 0dB, dB2 corresponds to a power increment step size of 2dB, dB4 corresponds to a power increment step size of 4dB, and dB6 corresponds to a power increment step size of 6dB.

29. The method according to claim 23, in, When the indication of whether delta MCS is applied is not present, Ks = 0 is used to calculate the power of the PUSCH of the request message, wherein Ks is provided by the indication of whether delta MCS is applied.

30. The method according to claim 23, wherein, In four-step random access, the delta MCS indicator is used to calculate the power of the PUSCH in the request message.

31. The method according to claim 23, wherein, When TPC with accumulation is enabled, apply TPC commands with accumulation; When TPC with accumulation is not enabled, apply TPC commands without accumulation; When there is no indication in the dedicated signaling whether to enable TPC with accumulation, TPC with accumulation is enabled.

32. The method according to claim 23, wherein, In four-step random access, the TPC cumulative indication is used to calculate the power of the PUSCH in the request message, and the TPC cumulative indication is an indication of whether the sum of the TPC command values ​​in the set of TPC command values ​​should be used for PUSCH power control.

33. The method according to claim 23, wherein, The dedicated signaling transmits the field of the TPC command used for PUSCH.

34. The method according to claim 33, wherein, In the dedicated signaling, the signaling transmits the 3-bit field of the TPC command used for PUSCH.

35. The method according to claim 33, wherein, In the dedicated signaling, the signaling transmits a 2-bit field of the TPC command for PUSCH, and there is a mapping between the TPC command field and absolute and / or cumulative values.

36. The method according to claim 23, wherein, The power increment step for PUSCH and at least one of the TPC commands for PUSCH are used to calculate the power of the PUSCH in the request message.

37. The method according to any one of claims 21-23, wherein, The dedicated signaling includes at least one of the following: Dedicated signaling for random access in a Radio Resource Control (RRC) message; Toggle command messages; Beam fault recovery message; and The command uses a two-step CFRA to randomly access the physical downlink control channel (PDCCH).

38. The method according to claim 37, wherein, The dedicated signaling used for random access is the RACH-ConfigDedicated information element (IE).

39. The method according to any one of claims 21 to 23, wherein, The network node is the target network node for switching, and sending at least two power control parameters to the terminal device includes: The at least two power control parameters configured in the dedicated signaling are sent to the switching source network node, and the switching source network node sends the dedicated signaling to the terminal device.

40. The method according to any one of claims 21 to 23, further comprising: Send a (506) response to the terminal device indicating whether the two-step CFRA was successful.

41. A terminal device (600), comprising: Processor (621); and A memory (622) stores instructions executable by the processor (621), thereby enabling the terminal device (600) to: Obtain at least two power control parameters, which will be used in response to a request message for a two-step contention-free random access CFRA. and Send the request message for the two-step CFRA to the network node; Wherein, the power of the request message for the CFRA is controlled based on the at least two power control parameters; and The request message includes a random access channel (RACH) preamble and a physical uplink shared channel (PUSCH). The at least two power control parameters include: A dedicated alpha value for PUSCH is configured in the dedicated signaling for the two-step CFRA, wherein the dedicated alpha value is a scaling factor for path loss. The power offset of the PUSCH relative to the preamble receive target power configured in the broadcast signaling, and The power increment step size for PUSCH in two-step CFRA configured in dedicated signaling.

42. The terminal device according to claim 41, wherein, The memory (622) stores instructions executable by the processor (621) that enable the terminal device to perform the method according to any one of claims 2 to 20.

43. A network node (600), comprising: Processor (621); and A memory (622) stores instructions executable by the processor (621), thereby enabling the network node (600) to: Send at least two power control parameters to the terminal device; and Receive a request message from the terminal device for two-step contention-free random access (CFRA); Specifically, the power of the request message for the two-step CFRA is controlled based on the at least two power control parameters; and The request message includes a random access channel (RACH) preamble and a physical uplink shared channel (PUSCH). The at least two power control parameters include: A dedicated alpha value for PUSCH is configured in the dedicated signaling for the two-step CFRA, wherein the dedicated alpha value is a scaling factor for path loss. The power offset of the PUSCH relative to the preamble receive target power configured in the broadcast signaling, and The power increment step size for PUSCH in two-step CFRA configured in dedicated signaling.

44. The network node according to claim 43, wherein, The memory (622) stores instructions executable by the processor (621) that enable the network node to perform the method according to any one of claims 22 to 40.

45. A computer-readable storage medium storing instructions that, when executed by at least one processor associated with a terminal device, cause the terminal device to perform the method according to any one of claims 1 to 20, or, when executed by at least one processor associated with a network node, cause the network node to perform the method according to any one of claims 21 to 40.

46. ​​A computer program product comprising instructions that, when executed by at least one processor associated with a terminal device, cause the terminal device to perform the method according to any one of claims 1 to 20, or, when executed by at least one processor associated with a network node, cause the network node to perform the method according to any one of claims 21 to 40.

Images