Indicating resources for shared channel transmissions

Abstract

Example embodiments of the present disclosure relate to indicating resources for shared channel transmission. A method includes receiving a random access response to a random access request from a second device; determining a target resource based on whether a resource offset for the first device is indicated in at least one of the reference resource and the random access response or a paging message from the second device; and performing a transmission to the second device using the target resource in response to the random access response.

Description

Technical Field

[0001] Various example embodiments of this disclosure relate generally to the telecommunications field, and more specifically to methods, apparatus, devices, and computer-readable storage media for indicating resources for shared channel transmission. Background Technology

[0002] A communication network can be used as a facility to enable communication between two or more communication devices or to provide communication devices with access to a data network. A mobile or wireless communication network is an example of a communication network.

[0003] Communication networks can operate according to standards provided by organizations such as the 3rd Generation Partnership Project (3GPP) or the European Telecommunications Standards Institute (ETSI). Examples of standards provided by 3GPP are the so-called 3GPP standards used for different generations of cellular technologies, such as the 3GPP standards for 4G, 5G, 6G, etc. Summary of the Invention

[0004] In a first aspect of this disclosure, a first apparatus is provided. The first apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus to at least: receive a paging message from a second apparatus; determine a target resource based on a reference resource and whether the paging message indicates a resource offset for the first apparatus; and perform a transmission for connection to the second apparatus using the target resource.

[0005] In a second aspect of this disclosure, a second apparatus is provided. The second apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus to at least: determine a target resource for a first apparatus; transmit a paging message to the first apparatus based on whether the target resource is offset relative to a reference resource; and receive a transmission from the first apparatus using the target resource for connecting to the second apparatus.

[0006] In a third aspect of this disclosure, a method is provided. The method includes: receiving a paging message from a second device; determining a target resource based on a reference resource and whether the paging message indicates a resource offset for a first device; and using the target resource to perform a transmission for connecting to the second device.

[0007] In a fourth aspect of this disclosure, a method is provided. The method includes: determining a target resource for a first device; transmitting a paging message to the first device based on whether the target resource is offset relative to a reference resource; and receiving a transmission from the first device using the target resource for connecting to a second device.

[0008] In a fifth aspect of this disclosure, a first apparatus is provided. The first apparatus includes: components for receiving a paging message from a second apparatus; components for determining a target resource based on a reference resource and whether the paging message indicates a resource offset for the first apparatus; and components for performing a transmission for connecting to the second apparatus using the target resource.

[0009] In a sixth aspect of this disclosure, a second apparatus is provided. The second apparatus includes: components for determining a target resource for a first apparatus; components for transmitting a paging message to the first apparatus based on whether the target resource is offset relative to a reference resource; and components for receiving a transmission from the first apparatus for connecting to the second apparatus using the target resource.

[0010] In a seventh aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to perform at least the method according to a third aspect.

[0011] In an eighth aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to perform at least the method according to the fourth aspect.

[0012] In a ninth aspect of this disclosure, a first apparatus is provided. The first apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus to at least: receive a random access response to a random access request from a second apparatus; determine a target resource based on whether at least one of a reference resource and the random access response or a paging message from the second apparatus indicates a resource offset for the first apparatus; and, in response to the random access response, perform a transmission to the second apparatus using the target resource.

[0013] In a tenth aspect of this disclosure, a second apparatus is provided. The second apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus to at least: determine whether a target resource allocated for a first apparatus is offset relative to a reference resource; transmit to the first apparatus a random access response to a random access request from the first apparatus, wherein at least one of the random access response or a paging message is based on the result of the determination; and receive a transmission from the first apparatus using the target resource.

[0014] In the eleventh aspect of this disclosure, a method is provided. The method includes: receiving a random access response to a random access request from a second device; determining a target resource based on a reference resource and whether at least one of the random access response or a paging message from the second device indicates a resource offset for a first device; and performing a transmission to the second device using the target resource in response to the random access response.

[0015] In a twelfth aspect of this disclosure, a method is provided. The method includes: determining whether a target resource allocated for a first device is offset relative to a reference resource; transmitting to the first device a random access response to a random access request from the first device, wherein at least one of the random access response or a paging message is based on the determined result; and receiving a transmission from the first device using the target resource.

[0016] In a thirteenth aspect of this disclosure, a first apparatus is provided. The first apparatus includes: means for receiving a random access response to a random access request from a second apparatus; means for determining a target resource based on a reference resource and whether at least one of the random access response or a paging message from the second apparatus indicates a resource offset for the first apparatus; and means for performing a transmission to the second apparatus using the target resource in response to the random access response.

[0017] In a fourteenth aspect of this disclosure, a second apparatus is provided. The second apparatus includes: means for determining whether a target resource allocated to a first apparatus is offset relative to a reference resource; means for transmitting to the first apparatus a random access response to a random access request from the first apparatus, wherein at least one of the random access response or a paging message is based on the determination result; and means for receiving a transmission from the first apparatus using the target resource.

[0018] In a fifteenth aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to perform at least the method according to an eleventh aspect.

[0019] In a sixteenth aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to perform at least the method according to the twelfth aspect.

[0020] It should be understood that the summary portion is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0021] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which: Figure 1An example communication environment in which example embodiments of this disclosure may be implemented is shown; Figure 2 The signaling diagram for the paging and random access procedures used to transition to connected mode is shown; Figure 3 Signaling diagrams indicating transmission resources according to some example embodiments of this disclosure are shown; Figure 4 A schematic diagram illustrating the calculation of the starting position of a transmission according to some example embodiments of the present disclosure is shown; Figure 5 Signaling diagrams for paging and random access procedures for transitioning to a connection mode, according to some example embodiments of the present disclosure, are shown; Figure 6 Signaling diagrams indicating transmission resources according to some example embodiments of this disclosure are shown; Figure 7 A signaling diagram of another paging and random access procedure for switching to a connected mode is shown according to some example embodiments of the present disclosure; Figure 8 A flowchart is shown illustrating a method implemented at a first device according to some exemplary embodiments of the present disclosure; Figure 9 A flowchart is shown illustrating a method implemented at a second device according to some example embodiments of the present disclosure; Figure 10 A flowchart is shown illustrating a method implemented at a first device according to some exemplary embodiments of the present disclosure; Figure 11 A flowchart is shown illustrating a method implemented at a second device according to some example embodiments of the present disclosure; Figure 12 A simplified block diagram of a device suitable for implementing example embodiments of the present disclosure is shown; and Figure 13 A block diagram of an example computer-readable medium according to some example embodiments of the present disclosure is shown.

[0022] In all the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0023] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. The embodiments described herein can be implemented in various ways other than those described below.

[0024] 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.

[0025] References to "an embodiment," "embodiment," "example embodiment," etc., in this disclosure indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment needs to include that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is claimed that, whether explicitly described or not, it is within the knowledge of those skilled in the art to influence such feature, structure, or characteristic in conjunction with other embodiments.

[0026] It should be understood that although the terms “first,” “second,” etc., may be used before (multiple) nouns 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, and they do not restrict the order of (multiple) nouns. 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 listed terms.

[0027] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, wherein the list of two or more elements is combined with “and” or “or”, means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0028] As used herein, unless explicitly stated otherwise, the “responding to A” action does not mean that the action is performed immediately after “A” occurs, but may include one or more intermediate steps.

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

[0030] As used in this application, the term "circuit" may refer to one or more or all of the following: (a) Hardware circuit implementation only (e.g., implemented with purely analog and / or digital circuits) and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and (ii) Any part of a hardware processor(s) having software (including (multiple) digital signal processors, software, and (multiple) memories, which work together to enable a device (such as a mobile phone or server) to perform various functions), and (c) The operation requires software (e.g., firmware) for the operation of (multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or parts thereof, but the software may be absent when the operation does not require the software.

[0031] This definition of "circuit" applies to all use of the term in this application (including in any claim). As another example, as used in this application, the term "circuit" also covers only hardware circuitry or processors (or processors), or a portion of hardware circuitry or processors and their accompanying software and / or firmware implementations. For example, if applicable to a particular claim element, the term "circuit" also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0032] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-A Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation-based communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), 5.5G, sixth-generation (6G) communication protocols and / or any other currently known or future-developed protocols. Embodiments of this disclosure can be applied to a variety of communication systems. Given the rapid development in communications, there will naturally be communication technologies and systems that embody future types of this disclosure. The scope of this disclosure should not be considered limited to the aforementioned systems.

[0033] As used herein, the term "network device" refers to a node in a communications network through which terminal devices access the network and receive services. Depending on the terminology and technology applied, a network device can refer to a base station (BS) or access point (AP), such as a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also known as a gNB), a Remote Radio Unit (RRU), a Radio Head (RH), a Remote Radio Head (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a low-power node (such as a femtosecond or picosecond), a non-terrestrial network (NTN) or non-terrestrial network equipment (such as satellite network equipment, low Earth orbit (LEO) satellites, and geostationary Earth orbit (GEO) satellites), an aircraft network device, etc. In some example embodiments, the Radio Access Network (RAN) split architecture includes a centralized unit (CU) and a distributed unit (DU) at the IAB donor node. An IAB node includes: a mobile terminal (IAB-MT) portion that behaves similarly to a UE when facing its parent node; and a DU portion of the IAB node that behaves similarly to a base station when facing the next-hop IAB node.

[0034] The term "terminal device" refers to any terminal device capable of wireless communication. As an example and not a limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablet computers, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), gaming terminal devices, music storage and playback facilities, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop-mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. The terminal device may also correspond to the mobile terminal (MT) portion of an IAB node (e.g., a relay node). In the following description, the terms "terminal device," "communication device," "terminal," "user equipment," and "UE" are used interchangeably.

[0035] As used herein, the terms “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” or “downlink resource” can refer to any resource used to perform communication (e.g., communication between a terminal device and a network device), such as resources in the time domain, resources in the frequency domain, resources in the spatial domain, resources in the code domain, or any other combination of time-domain, frequency-domain, spatial-domain, and / or code-domain resources capable of communication. In the following, unless explicitly stated otherwise, resources in both the frequency and time domains will be used as examples of transmission resources used to describe some exemplary embodiments of this disclosure. Note that the exemplary embodiments of this disclosure are equally applicable to other resources in other domains.

[0036] Figure 1 An example communication environment 100, in which exemplary embodiments of the present disclosure may be implemented, is illustrated. In communication environment 100, multiple communication devices (including a first device 110 and a second device 120) can communicate with each other. Figure 1 In the example, the first device 110 may include a terminal device (e.g., a UE), and the second device 120 may include a network device (also simply referred to as a network, such as a gNB). The service area of ​​the second device 120 may be referred to as cell 102.

[0037] It should be understood that Figure 1 The number of the first device 110 and the second device 120 shown is given for illustrative purposes and does not imply any limitation. The communication environment 100 may include any suitable number of devices configured to implement the exemplary embodiments of this disclosure. Although not shown, it should be understood that one or more additional devices may be located in cell 102, and one or more additional cells may be deployed in the communication environment 100. Note that although shown as a network device, the second device 120 may be a device other than a network device. Although shown as a terminal device, the first device 110 may be a device other than a terminal device.

[0038] In the following description, for illustrative purposes, some exemplary embodiments are described in which the first device 110 operates as a terminal device and the second device 120 operates as a network device. However, in some exemplary embodiments, the operations described in connection with the terminal device can be implemented at the network device or other devices, and the operations described in connection with the network device can be implemented at the terminal device or other devices.

[0039] In some example embodiments, if the first device 110 is a terminal device or is included in a terminal device and the second device 120 is a network device or is included in a network device, then the link from the second device 120 to the first device 110 is referred to as a downlink (DL), and the link from the first device 110 to the second device 120 is referred to as an uplink (UL). In the DL, the second device 120 is a transmitting (TX) device (or transmitter), and the first device 110 is a receiving (RX) device (or receiver). In the UL, the first device 110 is a TX device (or transmitter), and the second device 120 is an RX device (or receiver).

[0040] In the communication, the Random Access Channel (RACH) procedure is used to establish communication between the first device 110 and the second device 120. Specifically, the RACH procedure can be performed by the first device 110 to establish a Radio Resource Control (RRC) connection to the second device 120.

[0041] Communication in communication environment 100 can be implemented according to any suitable communication protocol(s), including but not limited to cellular communication protocols such as first-generation (1G), second-generation (2G), third-generation (3G), fourth-generation (4G), fifth-generation (5G), 5.5G, and sixth-generation (6G), wireless local area network communication protocols such as IEEE 802.11, and / or any other currently known or future-developed protocols. Furthermore, communication can utilize any suitable wireless communication technology, including but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple Access (OFDM), Discrete Fourier Transform Extended OFDM (DFT-s-OFDM), and / or any other currently known or future-developed technologies.

[0042] In 5G, when the UE is not actively transmitting data, it switches to idle mode to conserve battery life. During this time, the UE periodically checks for paging messages that may indicate incoming data or calls. Upon receiving a paging message, the UE initiates a service request procedure to establish a connection with the network. This may involve RRC connection establishment, authentication, and non-access stratum (NAS) security settings. PO stands for scheduling time, during which the UE listens for paging messages based on specific indices such as the Paging Frame Index (PFI) and Paging Timing Index (POI).

[0043] Paging is a mechanism used to notify idle UEs of incoming data, call requests, or network updates. In idle mode, the UE monitors paging frames within radio frames, and within these frames, the UE monitors the paging channel (PCH) for incoming paging messages at a paging opportunity (PO). A paging opportunity is a specific subframe within a paging frame in which the network searches for an idle UE to deliver data. Conversely, an idle UE is woken up in a specific subframe (subframe 0, subframe 4, subframe 5, or subframe 9) within a radio frame. These specific subframes within a paging frame that wake the UE are called POs. The paging opportunity is determined by a combination of the cell's paging cycle and the radio frame number (RFN). Paging opportunities are used to minimize signaling overhead by limiting the number of subframes in which the network searches for an idle UE.

[0044] The paging frame (PF) and PO used for paging are determined by calculating the System Frame Number (SFN) and PO index using a specific formula. The SFN for the PF can be calculated using the following formula:

[0045] Where T is the paging repetition period, and N is the number of paging frames within a given period. It is the unique identifier of the first device (UE). It is used to adjust the offset of the starting frame used for paging.

[0046] index( The index of the PO can be determined by the following formula:

[0047] in It is the number of paging opportunities within a frame.

[0048] In NR, paging messages can have the following structure: Paging ::= SEQUENCE { pagingRecordListPagingRecordList OPTIONAL,-- Need N lateNonCriticalExtensionOCTET STRING OPTIONAL, nonCriticalExtensionSEQUENCE{} OPTIONAL } PagingRecordList ::= SEQUENCE (SIZE(1..maxNrofPageRec)) OFPagingRecord PagingRecord ::= SEQUENCE { UE-IdentityPagingUE-Identity, accessTypeENUMERATED {non3GPP} OPTIONAL, -- Need N ... } PagingUE-Identity ::= CHOICE { ng-5G-S-TMSING-5G-S-TMSI, fullI-RNTII-RNTI-Value, ... } maxNrofPageRec INTEGER ::= 32 -- Maximum number of page records". To establish an RRC connection, the RACH random access procedure can be performed by the UE. Two types of random access procedures are supported: contention-based random access (CBRA) and contention-free or non-contention-based random access (CFRA).

[0049] In CBRA, the UE randomly selects a preamble from a preamble pool shared with other UEs. This means that a UE has the potential risk of selecting the same preamble as another UE, and thus may experience conflicts or contention. The gNB uses a contention resolution mechanism to handle this type of access request. In this process, the result is random, and not all random access is successful. CBRA is also known as the four-step RACH process.

[0050] Step 1 is called random access preamble transmission, which includes the transmission of message 1 (Msg1). In step 1, the UE transmits the preamble to the appropriate beam of the gNB.

[0051] Step 2, known as the Random Access Response, includes the transmission of message 2 (Msg2). Upon receiving the preamble, the gNB requests the Temporary Cell Radio Network Temporary Identifier (TC-RNTI), as well as uplink and downlink scheduling resources. The gNB then transmits the Random Access (RA) response via the Physical Downlink Shared Channel (PDSCH). The RA response includes the RA preamble identifier, timing alignment information, initial uplink grant, and the Temporary Cell Radio Network Temporary Identifier (C-RNTI). A single PDSCH transmission can carry RA responses for multiple UEs. After transmitting the preamble, the UE monitors the Physical Downlink Control Channel (PDCCH) and waits for the RA response within the RA response window. If the UE receives a response containing an RA preamble identifier that matches the identifier of the transmitted RA preamble, the RA response is therefore considered successful, and the UE subsequently transmits uplink scheduling information.

[0052] If the UE does not receive a response or cannot verify the response within the RA response window, the RA procedure is considered unsuccessful. In this case, if the number of RA attempts is less than the predefined upper limit (i.e., 10), the UE retryes the RA procedure. Otherwise, the RA procedure fails.

[0053] Step 3, referred to as the scheduled UL transport, includes the transmission of message 3 (Msg3). The UE transmits uplink scheduling information on the PUSCH. The signaling messages and information sent by the UE differ in different RA scenarios. Examples of these scenarios are provided below.

[0054] In the initial RRC connection establishment scenario, the RRCSetupRequest message carrying the NAS UE_ID is transmitted at the Radio Link Control (RLC) layer in Transparent Mode (TM) via the Common Control Channel (CCCH). This message is not fragmented. In the RRC connection re-establishment scenario, without the need for an NSA message, the RRC Re-establishment Request message is transmitted at the RLC layer in TM via the CCCH, and the message is not fragmented. In the handover scenario, if the UE accesses the target cell during handover without a dedicated preamble, a contention-based RA is triggered. The RRC handover confirmation message and C-RNTI are transmitted via the Dedicated Control Channel (DCCH) and may include a Buffer Status Report (BSR). In other scenarios, at least the UE's C-RNTI is transmitted.

[0055] Step 4, known as contention resolution, involves the transmission of message 4 (Msg4). After transmitting Msg3, the UE starts a contention resolution timer. The gNB assists in contention resolution by providing a C-RNTI on the PDCCH or a UE contention resolution identifier (IE) on the PDSCH. The UE monitors the PDCCH until the timer expires and considers contention resolution successful, stopping the timer if any of the following conditions are met: One condition is that the UE receives a C-RNTI on the PDCCH. Another condition is that the UE receives a provisional C-RNTI on the PDCCH, successfully decodes a Media Access Control (MAC) Protocol Data Unit (PDU), and the UE contention resolution identifier (IE) received via the PDSCH matches the identifier in Msg3 transmitted by the UE.

[0056] If the contention resolution timer expires, the UE considers the contention resolution unsuccessful. In this case, if the number of RA attempts has not yet reached the predefined upper limit (i.e., 10), the UE retrieves the RA procedure. If the upper limit is reached, the RA procedure is terminated.

[0057] Figure 2 An example signaling flow for the paging and RACH procedures used to switch to RRC connection mode is shown. Figure 2 As shown, at 203, UE 201 is in RRC idle mode and is monitoring paging messages. gNB 202 transmits (204) a PDCCH message scrambled with paging RNTI (P-RNTI) to UE 201. Then, gNB 202 transmits (205) a paging message to indicate that DL data has arrived for the relevant UE. After reading the paging message, UE 201 initiates CBRA procedure 206.

[0058] Specifically, UE 201 transmits (207) the RACH preamble (Msg1) to gNB 202 and waits for a Random Access Response (RAR) (also referred to as Msg2) from gNB 202 within a specific response window. UE 201 receives (208) the RAR (Msg2), which includes a timing advance (TA) and PUSCH resources for Msg3 transmission. UE 201 transmits (210) Msg3, specifically an RRC Setup Request, which is the first Layer 3 (L3) message transmitted by the UE in response to receiving a paging message. gNB 202 schedules and receives Msg3 transmitted from the UE based on previously allocated uplink resources. gNB 202 transmits (211) contention resolution to UE 201. gNB 202 transmits (212) the RRC Setup message to UE 201. UE 201 transmits a (213) RRCSetupRequestComplete message to gNB 202 to confirm the establishment of the RRC connection. At 214, UE 201 switches to RRC connection mode.

[0059] During paging, the associated conventional RACH procedure is required to obtain the TA and PUSCH resources needed for the UE to transmit the RRCSetupRequest message, thereby establishing an RRC connection with the network. The conventional paging and RACH process, which transitions the UE from RRC idle mode to RRC connected mode, involves multiple steps, increasing latency. Furthermore, there is resource overhead associated with these steps.

[0060] Resources used for PUSCH transmissions can be specified and reserved for use after a paging message is received. However, reserving these resources can be inefficient, as real-time network conditions may necessitate scheduling additional traffic on the same resources. Due to the variability of network demand and the dynamic nature of paging requests, reserving resources for unpredictable paging messages may actually be suboptimal.

[0061] In situations where the network requires the UE to transmit data (such as reports or measurements), the network and the UE should perform the following procedures: (1) RACH, (2) RRC connection establishment, and subsequently (3) Core Network (CN) procedures. Data transmission and reception between the network and the UE can only occur after these procedures have been successfully completed.

[0062] In one solution, PUSCH resources can be provided within the paging message. The UE can use these PUSCH resources to transmit Msg3 of the RACH procedure (see [link]). Figure 2 However, providing PUSCH resources (for the paged UE) in the paging message introduces additional overhead and increases the size of the paging message. This overhead may cause the network to reduce the number of paging records within the paging message.

[0063] Another solution is for the network to reserve resources and provide an index of those resources in the paging message. The UE can use these resources to send PUSCH, but this approach has the following problems. One problem with the above solution is that resource reservation introduces additional overhead, and reserving the same resources is inefficient given the unpredictable dynamics of UL / DL data for the scheduler (cell). Therefore, reserving these resources may limit the scheduler's ability to allocate those resources and reduce scheduling efficiency. Another problem is that the UE must perform a RACH procedure to obtain the appropriate TA and provisional RNTI (T-RNTI).

[0064] Given the above, several technical issues need to be addressed. One issue is how to enable a UE in RRC idle state to transmit PUSCH data to the network with accurate TA upon receiving a paging message, while avoiding the overhead associated with resource reservation and the conventional PUSCH assignment method in paging messages. Additionally, the RACH procedure needs to be eliminated to reduce latency.

[0065] According to some example embodiments of this disclosure, a solution for indicating transmission resources is provided. In this solution, a first device (e.g., a UE) receives a paging message from a second device (e.g., a gNB). The first device determines a target resource based on a reference resource and whether the paging message indicates a resource offset for the first device. Then, by using the target resource, the first device performs a transmission for connecting to the second device. Thus, the first device can enter a connected state with the second device.

[0066] According to these example embodiments of the present disclosure, the resources used for transmission (e.g., shared channel transmission) can be indicated by an offset in the paging message. In this way, the latency and overhead for indicating transmission resources can be reduced.

[0067] For example, if the transmission includes an L3 message, the first device can respond to the paging message by transmitting the L3 message at an appropriate timing in advance, thereby optimizing resource utilization (e.g., PUSCH / PUCCH resources) and reducing the latency and overhead typically involved in transitioning a UE from an RRC idle state to an RRC connected state during normal procedures. The advantages of this disclosure include, but are not limited to, the benefits described above.

[0068] The exemplary embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0069] Now for reference Figure 3 The diagram illustrates a signaling diagram 300 indicating transmission resources according to some example embodiments of the present disclosure. Signaling diagram 300 relates to [reference needed]. Figure 1 The first device 110 and the second device 120 are described.

[0070] The second device 120 determines (320) a target resource for the first device 110. This target resource will be used for a transmission from the first device 110 to the second device 120 and may therefore also be referred to as a transmission resource. This transmission is used to connect the first device 110 to the second device 120. In some example embodiments, the transmission may be a shared channel transmission, such as a PUSCH transmission. For example, the transmission may include the transmission of a message carrying PUSCH data.

[0071] The second device 120 transmits a paging message (325) to the first device 110 based on whether the target resource is offset relative to the reference resource. An example embodiment regarding the reference resource will be described below.

[0072] The second device 120 can determine whether the target resource has an offset relative to a reference resource. In some example embodiments, the second device 120 can determine whether the first device 110 meets the criteria for efficient resource allocation. If the first device 110 meets the criteria, the target resource for the first device 110 has an offset relative to a reference source. For example, paging messages can be directed to multiple UEs, and the gNB (as an example of the second device 120) can select one or more UEs from the multiple UEs based on the criteria for efficient resource allocation.

[0073] As examples, criteria for efficient resource allocation may include a UE subscribing to a special Ultra-Reliable and Low-Latency Communication (URLLC) service. Alternatively or additionally, the criterion may include a stationary or low-mobility UE derived by applying artificial intelligence and using the UE's historical mobility information. Alternatively or additionally, the criterion may include a UE requiring urgent paging. Alternatively or additionally, the criterion may include a UE being a highly valued (VIP) subscriber. Alternatively or additionally, the criterion may include a situation where the gNB does not anticipate UL / DL traffic and reserves some PUSCH resources. In this case, the gNB may choose to utilize the PUSCH offset for paging, enabling the UE to perform a RACH-free paging procedure. These criteria are examples and are not limiting.

[0074] If the second device 120 determines that the target resource for the first device 110 has a resource offset relative to a reference resource, the second device 120 may indicate the resource offset in a paging message. In some example embodiments, the paging message may include at least one paging record corresponding to at least one device identifier, and the paging record corresponding to the device identifier of the first device 110 may include an offset value of the resource offset. For example, the paging message may include at least one paging record corresponding to at least one UE ID, and the paging record corresponding to the UE ID of the first device 110 includes a resource offset value.

[0075] In some example embodiments, a paging message may involve multiple devices. Therefore, different devices may have different offset values ​​in the paging message. For example, another paging record in the paging message may correspond to a different device identifier than the device identifier of the first device 110, and this other paging record may include a different offset value. For example, another paging record corresponding to a UE ID different from the UE ID of the first device 110 may include a different offset value.

[0076] The example structure of a paging record in a paging message in Internet Explorer can be as follows: PagingRecord ::= SEQUENCE { UE-IdentityPagingUE-Identity, accessTypeENUMERATED {non3GPP} OPTIONAL, -- Need N resourceOffset………… } The parameter “ue-Identity” represents the UE ID, and the new parameter “resourceOffset” represents the resource offset value for the corresponding UE ID.

[0077] In some example embodiments, the second device 120 may reserve target resources for the first device 110 based on the estimated size of the transmission to be performed and reference resources. For example, the first L3 message to be sent on the PUSCH resource may have a fixed size or a known size, so the gNB may estimate the PUSCH resource size accordingly. The gNB may reserve resources of a fixed size or an estimated size (based on the expected size of the L3 message) with reference to a predetermined reference resource or point, and assign an offset value to the UE in the paging message.

[0078] Accordingly, the first device 110 receives (330) a paging message from the second device 120. The first device 110 then determines (335) a target resource based on a reference resource and whether the paging message indicates a resource offset for the first device 110.

[0079] In some example embodiments, if a paging message indicates a resource offset for the first device 110, the target resource can be determined by applying the indicated resource offset relative to a reference resource. For example, if a paging record with the device identifier of the first device 110 includes an offset value for the resource offset, the first device 110 can determine the target resource by applying the offset value to a reference resource.

[0080] In some example embodiments, if the paging message does not indicate a resource offset for the first device 110, at least a portion of the reference resource is determined as the target resource for the first device 110. For example, if a paging record with the device identifier of the first device 110 lacks parameters for the resource offset, the first device 110 may use at least a portion of the reference resource as the target resource.

[0081] In some example embodiments, the first device 110 may determine the size of the target resource based on the size of the transmission to be performed. For example, the UE may estimate the allocated PUSCH resource based on the size of the L3 message from a predetermined reference point and the PUSCH offset received in the paging message.

[0082] Continuing with Figure 300, the first device 110 performs (340) a transmission to the second device 120 using the identified target resource to connect to the second device 120. The second device 120 receives (345) the transmission from the first device. As described above, the transmission can be a PUSCH transmission, such as an L3 message. This transmission is performed without a RACH process and is therefore also referred to as a RACH-free transmission, for example, a RACH-free PUSCH transmission.

[0083] Some example embodiments of the reference resource will now be described. For example... Figure 3 As shown, the second device 120 can transmit (305) system information to the first device 110 to indicate a reference resource through information elements in the system information. The first device 110 receives (310) the system information from the second device 120 and determines (315) the reference resource based on the system information. For example, the system information may be System Information Block 1 (SIB1).

[0084] In some example embodiments, the reference resources may include resources for MsgA transmission during a two-step RA procedure. For example, if the second device 120 supports a two-step random access procedure, the second device 120 may use the resources in SIB1's " msgA-PUSCH- Config "Reference resources are provided in IE."

[0085] Taking gNB and UE as examples, gNB supports a 2-step RACH procedure. For the 2-step RACH procedure, gNB provides PUSCH resources in SIB1, SIB1-> msgA-PUSCH-Config This is used as a reference resource. This reference resource provides a predetermined reference point for the gNB and UE. Therefore, the UE and gNB can use this point as a predetermined reference to evaluate the (proposed) PUSCH offset. The gNB assigns the PUSCH offset in the paging message, and the UE can estimate the assigned PUSCH resource from the received PUSCH offset. The UE will use SIB1-> msgA-PUSCH-Config The PUSCH is taken as a predetermined reference point, and the allocated PUSCH resources are estimated. The estimated PUSCH is then allocated to the UE for transmitting PUSCH data.

[0086] In the example, since the PUSCH data size is almost fixed or known to the gNB, and the gNB is responsible for assigning the PUSCH offset, the gNB can determine the PUSCH offset based on the given information. msgA-PUSCH-Config The required PUSCH resources are assigned in the offset. This offset will allow the UE to send PUSCH data without any conflicts.

[0087] In the alternative example, if the gNB wants the UE to use "SIB1-> msgA-PUSCH-Config"With reserved PUSCH resources, the gNB can skip sending the offset value in the paging message. This could be an indication to the UE that the UE can use the offset value provided by..." msgA-PUSCH-Config The PUSCH resource is indicated. This resource can be used by (multiple) other UEs. Therefore, this example may lead to a conflict, and conflict resolution can be done in a manner very similar to CBRA conflicts.

[0088] This section describes an example approach for conflict resolution, without imposing any limitations. If any UE is performing a 2-step RACH procedure and sending PSUCH on the resources provided by "msgA-PUSCH-Config", while another UE is performing a PUSCH transmission without RACH, both can use the same resources to send PUSCH data. In the first option, the gNB can successfully read one of these messages and will respond to the UE using the associated ID (CRNTI). The UE gains access to the gNB and continues transmitting and receiving.

[0089] In the second option, the gNB may not read or reply to any messages. In this case, (multiple) UEs may choose to perform the following operations. For example, (multiple) UEs may select PUSCH resources and send PUSCH data and wait for parsing. In a 2-step RACH, (multiple) UEs may choose to perform RACH to obtain PUSCH resources for sending PUSCH data (the first L3 message).

[0090] The gNB can refer to "msgA-PUSCH-Config" and provide an offset. During RACH, the UE can use PUSCH resources at that offset to send PUSCH. The gNB can send this offset value to the UE in the paging message, and the UE can use "msgA-PUSCH-Config" and the offset received in the paging message to calculate the allocated PUSCH resources (because the size of msg3 is fixed, the UE and NW refer to "msgA-PUSCH-Config" and the offset to synchronize PUSCH resources) to send the first Layer 3 message.

[0091] In some example embodiments, the first device 110 can receive information from the second device 120 indicating resources for shared channel transmission without a random access procedure. The first device 110 can then determine a reference resource based on the indicated resources. For example, if the second device 120 does not support a two-step random access procedure, the second device 120 can configure resources for PUSCH transmissions without a RA procedure as the reference resource. For example, system information (such as SIB1) may include new IE " Rachless-PUSCH-ref "To indicate reference resources."

[0092] Taking gNB and UE as examples, if the gNB does not support the 2-step RACH procedure, the gNB may need to predetermine a reference point to evaluate or estimate the offset for PUSCH resources. The information element "Rachless-PUSCH-ref" can be used as the predetermined reference point. This IE can be broadcast in the SIB, for example, SIB1 (-> "Rachless-PUSCH-ref"). The gNB and UE can regard SIB1 (-> "Rachless-PUSCH-ref") as the predetermined reference point for PUSCH resource allocation as described above.

[0093] Some example embodiments of determining the starting position of a target resource will now be described. In some example embodiments, the resource offset may correspond to the number of Physical Resource Blocks (PRBs). In other words, the resource offset may be indicated by the number of PRBs.

[0094] Now for reference Figure 4 This illustrates an example used to calculate the starting position. As shown in the figure, PRB 401 is based on " SIB1-> msgA-PUSCH-Config The 2-step RACH process uses the PUSCH position or is based on SIB1 -> " Rachless-PUSCH-ref The PUSCH location is indicated by the resource offset 402 in the paging record (e.g., puschStartPrb INTEGER(0…272)). This offset can indicate to the UE the offset from PBR 403 to the (transmitted) PUSCH. Here, in the example, puschStartPrb = 3, so the calculated PRB 403 for transmitting the PUSCH (without RACH) is shown in shaded. The PRBs following PRB 401 with indices 0, 1, 2, and 3 are offset calculations ((puschStartPrb = 3)) to obtain the starting position of the PUSCH. If the gNB refers to "msgA-PUSCH-Config" or "...", the PUSCH location will be determined by the resource offset 402 in the paging record (e.g., puschStartPrb INTEGER(0…272)). Rachless-PUSCH-ref "By sending the offset value to the UE, the UE can send PUSCH resources without any conflicts. This is because the gNB is responsible for allocating the offset, and the size of msg3 to be sent via PUSCH is fixed. Therefore, if the gNB wants to allocate PUSCH resources to many UEs, it can refer to..." Rachless-PUSCH-ref "or" msgA-PUSCH-Config "Select appropriate offsets for all UEs without resource overlap."

[0095] In the above example embodiments, PUSCH resources can be dynamically assigned. A novel approach to dynamically assigning PUSCH resources is proposed. An offset value can be provided in the paging message. The UE can use this offset with respect to a predetermined reference to evaluate resource allocation. In this way, the overhead involved in PUSCH resource allocation in the paging message can be reduced. After paging, the first L3 message to be sent on the PUSCH resource has a nearly fixed or known size, so the UE and gNB can estimate the PUSCH resource size accordingly. The proposed solution can significantly reduce the overhead involved in PUSCH resource allocation in the paging message and achieve efficient connection to the gNB.

[0096] As an example, the UE maintains DL synchronization with the (serving) cell through periodic SSB measurements and reads the PDCCH to indicate data arrival. Upon receiving a paging message, the UE performs UL synchronization and executes the RRC connection establishment procedure. In the proposed solution, the gNB sends a PUSCH allocation "offset" to the UE in the paging message. The UE uses the offset value to reference either "msgA-PUSCH-Config" or "..." as described above. Rachless-PUSCH-ref "To calculate UL authorization."

[0097] The UE can use any mechanism to internally estimate the (T)-CRNTI. One such mechanism could be that the UE selects an RNTI from a given RNTI pool configured by the gNB and shares the RNTI with the gNB via PUSCH transmission, allowing the gNB to use the RNTI in subsequent transmissions for DCI scrambling against the UE. Another mechanism could be to establish a common RNTI calculation framework between the UE and the gNB, where both the gNB and the UE calculate the C-RNTI based on timing, frequency, location within the cell, etc., without requiring RNTI communication between the UE and the gNB.

[0098] The UE can estimate the timing offset internally using any available mechanism. For timing offset calculation, two different signals or timing references are required. One will be used as a reference point, and the other will be used to calculate the offset. This can be detailed in a separate IR, which includes further details about the reference signals that the UE can use to calculate its own timing offset.

[0099] The above steps enable the UE to send PUSCH without the need for RACH procedures and inefficient resource reservation and allocation mechanisms. Therefore, paging response latency, overhead signaling, and inefficient resource reservation can be saved.

[0100] To better understand the above solution, please refer to... Figure 5 Example description. Figure 5Signaling diagram 500 for paging and random access procedures for transitioning to connected mode according to some example embodiments of this disclosure is shown. Signaling diagram 500 can be considered as an example of signaling diagram 300. UE 501 can be considered as an example of first device 110, and gNB 502 can be considered as an example of second device 120. Figure 5 As shown in the process, the UE can use the proposed solution to switch to RRC connection mode without performing the RACH procedure.

[0101] like Figure 5 As shown, gNB 502 preferably broadcasts (505) IE " to UE 501 via SIB1. MsgA-PUSCH-Config "or" RACHLESS-PUSCH-ref The broadcast provides information about a predetermined reference point used as the starting position for the PUSCH. Using this information, the PUSCH is assigned an offset, enabling data transmission without performing the regular RACH procedure. This is achieved by allowing the use of a reference point relative to… MsgA-PUSCH-Config "or" RACHLESS-PUSCH-ref The method eliminates the need to transmit full frequency-time domain information for the PUSCH location by offsetting the PUSCH position, thus improving efficiency.

[0102] At 510, UE 501 is in RRC idle mode. At 515, UE 501 is monitoring PDCCH scrambled using P-RNTI. At 520, gNB 502 transmits an enhanced paging message (denoted as "paging ->puschStartPrb") containing a dedicated start PRB for PUSCH, and optionally the number of PRBs. It is assumed that a fixed number of PRBs are allocated for MSG-A transmissions, corresponding to the higher-layer parameter "nrofPRB-perMsgA-PO". UE 501 can use this offset to calculate the PUSCH resources required for a no-RACH response.

[0103] In some example implementations, the gNB 502 may not allocate dedicated PUSCH resources for all UEs in the paging message. Instead, the gNB 502 may selectively reserve uplink resources for certain UEs and include them in the paging message by applying artificial intelligence and / or based on key UE notifications received from the core network (such as Access and Mobility Management Functions (AMF)). The gNB 502 may store historical mobility information of UEs and use this information to determine the availability of UEs within the cell. Therefore, only those UEs with higher priority are allocated dedicated PUSCH resources, and their corresponding initial PRB information is transmitted in the paging message.

[0104] At 525, UE 501 calculates the TA using the previous TA value and an arbitrary internal calculation method. This may involve using two different resources transmitted at different times to determine the timing offset. UE 501 then utilizes this timing offset for uplink synchronization during PUSCH transmission in subsequent time slots. If necessary, gNB 502 can apply additional corrections. UE 501 then bases the received " msgA-PUSCH-Config "or "Rachless-PUSCH-ref" and the received offset are used to estimate PUSCH resources, as referenced Figure 3 As stated above.

[0105] At 530, UE 501 calculates the TC-RNTI using the method described above and transmits (540) PUSCH (L3 message) to gNB 502, then waits for a response from gNB 502. (See reference) Figure 4 A detailed explanation of PUSCH location calculation.

[0106] At positions 545 and 550, UE 501 awaits downlink assignment and uses the T-CRNTI to descramble the DCI. During this process, gNB 502 can assign a new C-TNTI within the downlink assignment or promote the T-CRNTI to a permanent C-RNTI allocation. gNB 502 transmits an RRCSetup message containing regular content to UE 501. UE 501 then uses this content to establish a signaling radio bearer (SRB) and implement additional instructions.

[0107] At 555, after successfully applying the SRB and other configurations, UE 501 transmits an RRCSetup completion message to gNB 502 to confirm the establishment of the RRC connection. At 560, UE 501 transitions to the RRC connected state and performs the necessary operations.

[0108] In the above example embodiments, the solution is applied to transmissions without a RA procedure. In some example embodiments, the solution can be applied to cases where a RACH procedure is performed after a paging message is received.

[0109] Now for reference Figure 6 This is to illustrate such an example embodiment. Figure 6 Signaling diagram 600 is shown, indicating transmission resources according to some example embodiments of the present disclosure. Signaling diagram 600 relates to [reference needed]. Figure 1 The first device 110 and the second device 120 are described.

[0110] like Figure 6As shown, in some example embodiments, prior to the RA process, the second device 120 may broadcast (625) a paging message to at least one device including the first device 110. Accordingly, the first device 110 may receive (630) a paging message from the second device 120.

[0111] The first device 110 initiates an RA procedure to the second device 120. The first device 110 may transmit an RA request (635) to the second device 120. The RA procedure may be a two-step RA procedure, and the RA request may be MsgA. Alternatively, the RA procedure may be a four-step RA procedure, and the RA request may include a preamble.

[0112] The second device 120 may receive (640) an RA request from the first device 110. In response, the second device 120 transmits (645) an RA response to the first device 110. In the case of a 2-step RA process, the RA response may be MsgB or RAR. In the case of a 4-step RA process, the RA response may be Msg3.

[0113] like Figure 6 As shown, the second device 120 determines (620) whether the target resource allocated to the first device is offset relative to a reference resource. At least one of a paging message or an RA response is based on this determination. The target resource will be used for a transmission from the first device 110 to the second device 120 and may therefore also be referred to as a transmission resource. This transmission is used to connect the first device 110 to the second device 120. In some example embodiments, the transmission may be a shared channel transmission, such as a PUSCH transmission. For example, the transmission may include a transmission of a message carrying PUSCH data.

[0114] In some example embodiments, the second device 120 may determine whether the first device 110 meets the criteria for efficient resource allocation. If the first device 110 meets the criteria, the target resource for the first device 110 has an offset relative to a reference source. For example, paging messages may be directed to multiple UEs, and the gNB (as an example of the second device 120) may select one or more UEs from the multiple UEs based on the criteria for efficient resource allocation.

[0115] As examples, criteria for efficient resource allocation could include a UE subscribing to a special Ultra-Reliable and Low-Latency Communication (URLLC) service. Alternatively or additionally, the criteria could include identifying stationary or low-mobility UEs by applying artificial intelligence and using the UE's historical mobility information. Alternatively or additionally, the criteria could include a UE requiring urgent paging. Alternatively or additionally, the criteria could include a UE being a Highly Valuable Customer (VIP) subscriber. Alternatively or additionally, the criteria could include situations where the gNB does not anticipate UL / DL traffic and reserves some PUSCH resources. In this case, the gNB could choose to utilize the PUSCH offset for paging, enabling the UE to perform a RACH-free paging procedure. These criteria are examples and are not limiting.

[0116] In some example embodiments, if the target resource is offset relative to the reference resource, at least one of the RA response or paging message indicates the resource offset from the target resource to the reference resource of the first device 110.

[0117] If the second device 120 determines that the target resource for the first device 110 has a resource offset relative to a reference resource, the second device 120 may indicate the resource offset in a paging message. In some example embodiments, the paging message may include at least one paging record corresponding to at least one device identifier, and the paging record corresponding to the device identifier of the first device 110 may include an offset value of the resource offset. For example, the paging message may include at least one paging record corresponding to at least one UE ID, and the paging record corresponding to the UE ID of the first device 110 includes a resource offset value.

[0118] In some example embodiments, a paging message may involve multiple devices. Therefore, different devices may have different offset values ​​in the paging message. For example, another paging record in the paging message may correspond to a different device identifier than the device identifier of the first device 110, and this other paging record may include a different offset value. For example, another paging record corresponding to a UE ID different from the UE ID of the first device 110 may include a different offset value.

[0119] In some example embodiments, the second device 120 may reserve target resources for the first device 110 based on the estimated size of the transmission to be performed and reference resources. For example, the first L3 message to be sent on the PUSCH resource may have a fixed size or a known size, so the gNB may estimate the PUSCH resource size accordingly. The gNB may reserve resources of a fixed size or an estimated size (based on the expected size of the L3 message) with reference to a predetermined reference resource or point, and assign an offset value to the UE in a paging message or RA response.

[0120] Accordingly, the first device 110 receives (650) an RA response from the second device 120. The first device 110 determines (655) a target resource based on whether at least one of the RA response or a paging message from the second device 120 indicates a reference resource and a resource offset for the first device 110.

[0121] In some example embodiments, if a paging message or RA response indicates a resource offset for the first device 110, the target resource can be determined by applying the indicated resource offset relative to a reference resource. For example, if a paging record with the device identifier of the first device 110 includes an offset value for the resource offset, the first device 110 can determine the target resource by applying the offset value to a reference resource.

[0122] In some example embodiments, if the paging message does not indicate a resource offset for the first device 110, at least a portion of the reference resource is determined as the target resource for the first device 110. For example, if a paging record with the device identifier of the first device 110 lacks a parameter for the resource offset and the RA response does not include a value for the resource offset, the first device 110 may use at least a portion of the reference resource as the target resource.

[0123] In some example embodiments, the first device 110 may determine the size of the target resource based on the size of the transmission to be performed. For example, the UE may estimate the allocated PUSCH resource based on the size of the L3 message from a predetermined reference point and the PUSCH offset received in the paging message.

[0124] Continuing with Figure 600, the first device 110 uses the determined target resource to perform (660) a transmission to the second device 120. The second device 120 receives (665) the transmission from the first device 110. In the case of a 4-step RA process, the transmission can be a Msg3 transmission. In the case of a 2-step RA process, the transmission can be a PUSCH transmission.

[0125] Some example embodiments of the reference resource will now be described. For example... Figure 6 As shown, the second device 120 can transmit (605) system information to the first device 110 to indicate a reference resource through information elements in the system information. The first device 110 receives (610) the system information from the second device 120 and determines (615) the reference resource based on the system information. For example, the system information may be SIB1.

[0126] In some example embodiments, the reference resources may include resources for MsgA transmission during a two-step RA procedure. For example, if the second device 120 supports a two-step random access procedure, the second device 120 may use the resources in SIB1's " msgA-PUSCH- Config "Reference resources are provided in IE."

[0127] Taking gNB and UE as an example, gNB supports a 2-step RACH procedure. For the 2-step RACH procedure, gNB provides PUSCH resources in SIB1, SIB1->msgA-PUSCH-Config, which is used as a reference resource. This reference resource provides a predetermined reference point for both gNB and UE. Therefore, UE and gNB can use this point as a predetermined reference to evaluate the (proposed) PUSCH offset. gNB assigns the PUSCH offset in the paging message, and UE can estimate the assigned PUSCH resource from the received PUSCH offset. UE uses SIB1->msgA-PUSCH-Config as the predetermined reference point and estimates the allocated PUSCH resource. This estimated PUSCH is allocated to UE for transmitting PUSCH data.

[0128] In the example, since the PUSCH data size is almost fixed or known to the gNB, and the gNB is responsible for assigning the PUSCH offset, the gNB can determine the PUSCH offset based on the given information. msgA-PUSCH-Config The ->offset assigns the necessary PUSCH resources. This offset will allow the UE to send PUSCH data without any conflicts.

[0129] In an alternative example, if the gNB wants the UE to use the PUSCH resources reserved by "SIB1->msgA-PUSCH-Config", the gNB can skip sending the offset value in the paging message. This could be an instruction to the UE that the UE can use the PUSCH resources reserved by "SIB1->msgA-PUSCH-Config". msgA-PUSCH-Config The specified PUSCH resource can be used by (multiple) other UEs. Therefore, this example can lead to a conflict, and conflict resolution can be done in a manner very similar to CBRA conflict resolution. Conflict resolution can be referenced above. Figure 3 The descriptions are similar, so they will not be repeated here.

[0130] In some example embodiments, the first device 110 can receive information from the second device 120 indicating resources for shared channel transmission without a random access procedure. The first device 110 can then determine a reference resource based on the indicated resources. For example, if the second device 120 does not support a two-step random access procedure, the second device 120 can configure the resources used for PUSCH transmission as the reference resource without a RA procedure. For example, system information (such as SIB1) may include the new IE " Rachless-PUSCH-ref "To indicate reference resources."

[0131] Taking gNB and UE as examples, if the gNB does not support the 2-step RACH procedure, the gNB may need to predetermine a reference point to evaluate or estimate the offset for PUSCH resources. The information element "Rachless-PUSCH-ref" can be used as the predetermined reference point. This IE can be broadcast in the SIB, for example, SIB1 (-> "Rachless-PUSCH-ref"). The gNB and UE can regard SIB1 (-> "Rachless-PUSCH-ref") as the predetermined reference point for PUSCH resource allocation as described above.

[0132] The determination of the starting location of the target resource can be referenced above. Figure 3 and Figure 4 The descriptions are similar, so they will not be repeated here.

[0133] For reference Figure 6 The described embodiment is an example of a solution that may be applicable if the UE performs a RACH procedure after receiving a paging message. As part of the RACH procedure (e.g., a 2-step RACH procedure), the gNB can communicate via RAR or through the IE in SIB1. MsgA-PUSCH-Config "To assign PUSCH resources. In these example embodiments, the PUSCH resource offset can be provided in the RAR or paging message. Providing the offset will reduce the overhead involved in regular PUSCH resource allocation and eliminate the overhead via IE in SIB1." MsgA-PUSCH-Config The conflict of PUSCH resources. For a 4-step RACH procedure, gNB can assign the PUSCH offset in the RAR message (regarding the IE in SIB1). MsgA-PUSCH-Config "or IE "Rachless-PUSCH-ref" in SIB1). This will reduce the overhead involved in the regular PUSCH assignment method in RAR.

[0134] To better understand the above solution, please refer to... Figure 7 Example description. Figure 7 Signaling diagram 700 for paging and random access procedures for transitioning to a connection mode, according to some example embodiments of this disclosure, is shown. Signaling diagram 700 can be considered as an example of signaling diagram 600. UE 701 can be considered as an example of first device 110, and gNB 702 can be considered as an example of second device 120. Figure 7 As shown in the process, the UE can use the proposed solution to switch to RRC connection mode without performing the RACH procedure.

[0135] like Figure 7As shown, gNB 702 broadcasts (705) SIB1 with IE "MsgA-PUSCH-Config" or SIB1 with IE "RACHLESS-PUSCH-ref" to UE 701. At 710, UE 701 is in RRC idle mode and monitors for paging messages. gNB 702 transmits (715) a PDCCH message scrambled with P-RNTI to UE 701. Then, gNB 702 transmits (720) a paging message to indicate that DL data has arrived for the relevant UE including UE 701. In the next step, UE 701 transmits (725) a RACH preamble as a RA request to gNB 702 and waits for a RAR response from gNB 702. gNB 702 transmits (730) a RAR to UE 701, which includes the PUSCH offset and other standard regular RAR content. In traditional RAR, PUSCH resource allocation contains complete information, including time-domain and frequency-domain information.

[0136] The proposed solution utilizing PUSCH offset introduces a novel mechanism for allocating PUSCH resources via RAR. The proposed solution significantly reduces the overhead associated with including complete PUSCH information in a regular RAR. By simplifying the PUSCH resource allocation process, this method optimizes overall efficiency and reduces signaling load. At 735, UE 701 estimates the PUSCH resources based on the received IE "msgA-PUSCH-Config" or "Rachless-PUSCH-ref" and the received offset. UE 701 then transmits a (740) RRCSetupRequest message to gNB 702. At 745, gNB 702 performs contention resolution. At 750, gNB 702 sends an RRCSetup message. At 755, the UE sends an RRCSetupRequestComplete message to gNB 702 to confirm the establishment of the RRC connection. At 760, UE 701 switches to RRC connection mode.

[0137] This alternative solution is applicable if the UE wants to perform a RACH procedure after receiving a paging message. If the UE does not support CRNTI and TA calculations, the UE can perform a regular RACH procedure to transition to the RRC connected state. The proposed solution reduces the overhead involved in sending PUSCH resources in the RAR message. The gNB can use a pre-defined reference point for the PUSCH (e.g., IE "msgA-PUSCH-Config" or "Rachless-PUSCH-ref") to estimate the offset and assign the offset in the RAR message.

[0138] Traditionally, RAR messages carry complete information about PUSCH resource allocation, such as the time-domain and frequency-domain information of the allocated PUSCH. However, the proposed solution for allocating PUSCH offsets in RAR reduces the resource overhead associated with providing complete information about PUSCH allocation in RAR.

[0139] The example implementation offers several advantages. First, it enables the UE to independently calculate the TA without network involvement. Second, the method allows the UE to allocate PUSCH resources without performing a regular RACH procedure, and this allocation can be done dynamically, eliminating the need to continuously reserve the same resources. By using offsets relative to “msgA-PUSCH-Config” or “Rachless-PUSCH-ref”, the number of bits required to transmit uplink grants is minimized, thereby improving transmission efficiency.

[0140] This method reduces paging response latency by eliminating the need for a regular RACH procedure. In scenarios where the network instructs the UE to transmit data, the PUSCH resource offset can be included in the paging message. By employing the method described in this disclosure, the UE can transmit PUSCH data without initiating a RACH procedure, thereby preventing inefficient resource reservation. When the network paging the UE via the PUSCH resource offset associated with “msgA-PUSCH-Config”, the UE can estimate the TA and determine the PUSCH resources required for uplink data transmission. Subsequently, the UE can utilize these resources to transmit a paging response (such as an RRCSetup message) to establish an RRC connection.

[0141] Figure 8 A flowchart of an example method 800 implemented at a first device according to some example embodiments of the present disclosure is shown.

[0142] At frame 810, the first device receives a paging message from the second device.

[0143] At box 820, the first device determines the target resource based on the reference resource and whether the paging message indicates a resource offset for the first device.

[0144] At box 830, the first device uses the target resource to perform a transmission for connecting to the second device.

[0145] In some example embodiments, method 800 further includes: determining a target resource by applying the indicated resource offset with respect to a reference resource, based on the determined paging message indicating a resource offset for the first device.

[0146] In some example embodiments, the paging message includes at least one paging record corresponding to at least one device identifier, and the paging record corresponding to the device identifier of the first device includes an offset value of the resource offset.

[0147] In some example embodiments, at least one paging record corresponds to another device identifier that is different from the device identifier of the first device, and the other paging record includes another offset value.

[0148] In some example embodiments, method 800 further includes: determining at least a portion of a reference resource as a target resource based on the determination that the paging message does not indicate a resource offset of the first device.

[0149] In some example embodiments, method 800 further includes: receiving system information from a second device; and determining a reference resource based on information elements in the system information.

[0150] In some example embodiments, the reference resources include resources for the transmission of message A in a two-step random access process.

[0151] In some example embodiments, method 800 further includes: receiving information from a second means indicating resources for shared channel transmission without a random access procedure; and determining reference resources based on the indicated resources.

[0152] In some example embodiments, method 800 further includes: determining the size of the target resource based on the size of the transfer to be performed.

[0153] In some example implementations, the resource offset corresponds to the number of physical resource blocks.

[0154] In some example embodiments, the first device is a terminal device or is included in the terminal device, and the second device is a network device or is included in the network device.

[0155] Figure 9 A flowchart of an example method 900 implemented at a second device according to some example embodiments of the present disclosure is shown.

[0156] At box 910, the second device determines the target resource for the first device.

[0157] At frame 920, the second device transmits a paging message to the first device based on whether the target resource is offset relative to the reference resource.

[0158] At box 930, the second device uses the target resource to receive a transmission from the first device for connecting to the second device.

[0159] In some example embodiments, method 900 further includes: sending a paging message to a second device based on determining an offset of the target resource relative to a reference resource, the paging message indicating the resource offset from the target resource to the reference resource for the first device.

[0160] In some example embodiments, the paging message includes at least one paging record corresponding to at least one device identifier, and the paging record corresponding to the device identifier of the first device includes an offset value of the resource offset.

[0161] In some example embodiments, at least one paging record corresponds to another device identifier that is different from the device identifier of the first device, and the other paging record includes another offset value.

[0162] In some example embodiments, method 900 further includes: determining whether the first device meets the criteria for efficient allocation of resources; and determining, based on the determination that the first device meets the criteria, an offset of the target resource for the first device relative to a reference resource.

[0163] In some example embodiments, method 900 further includes: sending a paging message to a second device that does not require a resource offset from the first device, based on the determination that the target resource is not offset relative to a reference resource.

[0164] In some example embodiments, method 900 further includes sending system information to a first device to indicate a reference resource via information elements in the system information.

[0165] In some example embodiments, the reference resources include resources for the transmission of message A in a two-step random access process.

[0166] In some example embodiments, method 900 further includes: identifying resources for shared channel transmission without a random access procedure as reference resources; and sending information indicating the identified resources to a first device.

[0167] In some example embodiments, method 900 further includes reserving target resources for a second device based on an estimated size of the transmission and reference resources.

[0168] In some example implementations, the resource offset corresponds to the number of physical resource blocks.

[0169] In some example embodiments, the first device is a terminal device or is included in a terminal device, and the second device is a network device or is included in a network device.

[0170] In some example embodiments, the first means capable of performing any of the methods 800 may include components for performing the corresponding operation of method 800 and / or the corresponding operation of any of one or more of the example embodiments thereof. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module.

[0171] In some example embodiments, the second means capable of performing any of the methods 900 may include components for performing the corresponding operation of method 900 and / or the corresponding operation of any of one or more of the example embodiments thereof. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module.

[0172] Figure 10 A flowchart of an example method 1000 implemented at a first device according to some example embodiments of the present disclosure is shown.

[0173] At box 1010, the first device receives a random access response to the random access request from the second device.

[0174] At box 1020, the first device determines the target resource based on whether at least one of the reference resource and the random access response or the paging message from the second device indicates a resource offset for the first device.

[0175] At box 1030, in response to a random access response, the first device performs a transmission to the second device using the target resource.

[0176] In some example embodiments, method 1000 further includes: determining a target resource by applying the indicated resource offset with respect to a reference resource, based on determining that at least one of a random access response or a paging message indicates a resource offset for the first device.

[0177] In some example embodiments, a resource offset is indicated in a paging message, which includes at least one paging record corresponding to at least one device identifier, and the paging record corresponding to the device identifier of the first device includes an offset value of the resource offset.

[0178] In some example embodiments, method 1000 further includes: determining at least a portion of a reference resource as a target resource based on the determination that no resource offset is indicated for the first device.

[0179] In some example embodiments, method 1000 further includes: receiving system information from a second device; and determining a reference resource based on information elements in the system information.

[0180] In some example embodiments, the reference resources include resources for the transmission of message A in a two-step random access process.

[0181] In some example embodiments, method 1000 further includes: receiving information from a second device indicating resources for shared channel transmission without a random access procedure; and determining reference resources based on the indicated resources.

[0182] In some example embodiments, method 1000 further includes: determining the size of the target resource based on the size of the transfer to be performed.

[0183] In some example implementations, the resource offset corresponds to the number of physical resource blocks.

[0184] In some example embodiments, the first device is a terminal device or is included in a terminal device, and the second device is a network device or is included in a network device.

[0185] Figure 11 A flowchart of an example method 1100 implemented at a second device according to some example embodiments of the present disclosure is shown.

[0186] At box 1110, the second device determines whether the target resource allocated to the first device is offset relative to the reference resource.

[0187] At box 1120, the second device transmits a random access response to the first device in response to a random access request from the first device, wherein at least one of the random access response or paging message is based on the determined result.

[0188] At frame 1130, the second device uses the target resource to receive a transmission from the first device.

[0189] In some example embodiments, the target resource is offset relative to a reference resource, and at least one of the random access response or paging message indicates the resource offset for the first device from the target resource to the reference resource.

[0190] In some example embodiments, a resource offset is indicated in a paging message, which includes at least one paging record corresponding to at least one device identifier, and the paging record corresponding to the device identifier of the first device includes an offset value of the resource offset.

[0191] In some example embodiments, method 1100 further includes: transmitting system information to a first device to indicate a reference resource via information elements in the system information.

[0192] In some example embodiments, the reference resources include resources for the transmission of message A in a two-step random access process.

[0193] In some example embodiments, method 1100 further includes: determining resources for shared channel transmission without a random access procedure as reference resources; and transmitting information indicating the determined resources to a first device.

[0194] In some example embodiments, method 1100 further includes reserving target resources for a second device based on an estimated size of the transmission and reference resources.

[0195] In some example implementations, the resource offset corresponds to the number of physical resource blocks.

[0196] In some example embodiments, the first device is a terminal device or is included in a terminal device, and the second device is a network device or is included in a network device.

[0197] In some example embodiments, the first means capable of performing any of the methods 1000 may include components for performing the corresponding operations of method 1000 and / or any of the corresponding operations in one or more example embodiments thereof. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module.

[0198] In some example embodiments, the second means capable of performing any of methods 1100 may include components for performing the corresponding operations of method 1100 and / or any of the corresponding operations in one or more example embodiments thereof. This component may be implemented in any suitable form. For example, the component may be implemented in a circuit or software module.

[0199] Figure 12 This is a simplified block diagram of a device 1200 suitable for implementing an example embodiment of the present disclosure. Device 1200 can be used to implement a communication device, for example, such as... Figure 1 The first device 110 or the second device 120 are shown. As shown, device 1200 includes one or more processors 1210, one or more memories 1220 coupled to processor 1210, and one or more communication modules 1240 coupled to processor 1210.

[0200] Communication module 1240 is used for bidirectional communication. Communication module 1240 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interface can represent any interface necessary for communication with other network elements. In some example embodiments, communication module 1240 may include at least one antenna.

[0201] As a non-limiting example, processor 1210 can be any type suitable for a local technology network and can include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture. Device 1200 can have multiple processors, such as application-specific integrated circuit chips, which are time-subordinate to a clock that synchronizes the main processor.

[0202] Memory 1220 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 1224, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disc (CD), digital video disc (DVD), optical disc, laser disc, and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 1222 and other volatile memories that will not persist during power outages.

[0203] Computer program 1230 includes computer-executable instructions that are executed by an associated processor 1210. The instructions of program 1230 may include instructions for performing operations / actions of some example embodiments of this disclosure. Program 1230 may be stored in memory (e.g., ROM 1224). Processor 1210 can perform any suitable actions and processes by loading program 1230 into RAM 1222.

[0204] Example embodiments of this disclosure can be implemented using program 1230, enabling device 1200 to execute as described in the reference. Figures 3 to 11 Any process discussed in this disclosure. Exemplary embodiments of this disclosure may also be implemented by hardware or a combination of software and hardware.

[0205] In some example embodiments, program 1230 may be tangibly contained in a computer-readable medium, which may be included in device 1200 (such as in memory 1220) or other storage device accessible by device 1200. Device 1200 may load program 1230 from the computer-readable medium into RAM 1222 for execution. In some example embodiments, the computer-readable medium may include any type of non-transitory storage medium, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. As used herein, the term "non-transitory" is a limitation of the medium itself (i.e., tangible, not tactile), rather than a limitation of the persistence of data storage (e.g., RAM versus ROM).

[0206] Figure 13An example of a computer-readable medium 1300 is shown, which may be in the form of a CD, DVD, or other optical storage disc. The computer-readable medium 1300 has a program 1230 stored thereon.

[0207] Generally, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, and others can be implemented in firmware or software, which can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are shown and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, as non-limiting examples, the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0208] Some exemplary embodiments of this disclosure also provide at least one computer program product tangibly stored on a computer-readable medium, such as a non-transitory computer-readable medium. The computer program product includes computer-executable instructions, such as those included in a program module, which execute in a device on a target physical or virtual processor to perform any of the methods described above. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a particular task or implement a particular abstract data type. In various embodiments, the functionality of the program modules can be combined or split among program modules as needed. The machine-executable instructions for the program module can execute within a local or distributed device. In a distributed device, the program module can reside on both local and remote storage media.

[0209] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code enables the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0210] In the context of this disclosure, computer program code or related data may be carried by any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, etc.

[0211] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof. More specific examples of computer-readable storage media will include electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0212] Furthermore, although operations are described in a specific order, this should not be construed as requiring that such operations be performed in the specific order shown or sequentially, or that all shown operations be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure, but rather as a description of features that may be specified in particular embodiments. Unless explicitly stated otherwise, certain features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated otherwise, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0213] Although this disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms for implementing the claims.

[0214] Further examples of embodiments according to this disclosure are shown below.

[0215] Example 1. A first device for communication, comprising: At least one processor; and At least one memory storing instructions that, when executed by at least one processor, cause the first device to at least: Receive a random access response to the random access request from the second device; The target resource is determined based on whether at least one of the reference resource and the random access response or the paging message from the second device indicates a resource offset for the first device; and In response to the random access response, a transmission is performed to the second device using the target resource.

[0216] Example 2. According to the first device of Example 1, wherein the first device is made such that: The target resource is determined by applying the indicated resource offset relative to a reference resource, based on at least one of the determined random access response or paging message that indicates the resource offset for the first device.

[0217] Example 3. According to the first device of Example 1, wherein the resource offset is indicated in a paging message, the paging message including at least one paging record corresponding to at least one device identifier, and the paging record corresponding to the device identifier of the first device including the offset value of the resource offset.

[0218] Example 4. According to the first device of Example 1, wherein the first device is such that: Based on the determination that no resource offset is indicated for the first device, at least a portion of the reference resource is identified as the target resource.

[0219] Example 5. According to the first device of Example 1, wherein the first device is further configured such that: Receive system information from the second device; and Reference resources are determined based on the information elements in the system information.

[0220] Example 6. According to the first apparatus of Example 1, wherein the reference resources include resources for the transmission of message A in a two-step random access procedure.

[0221] Example 7. According to the first device of Example 1, wherein the first device is made such that: Receive information from the second device, the information indicating resources for shared channel transmission without a random access procedure; and Based on the indicated resources, determine the reference resources.

[0222] Example 8. According to the first device of Example 5, wherein the first device is made such that: The size of the target resource is determined based on the size of the transfer to be performed.

[0223] Example 9. According to the first apparatus of Example 1, where the resource offset corresponds to the number of physical resource blocks.

[0224] Example 10. The first device according to Example 1, wherein the first device is a terminal device or is included in a terminal device, and the second device is a network device or is included in a network device.

[0225] Example 11. A second means for communication, comprising: At least one processor; and At least one memory storing instructions that, when executed by at least one processor, cause the second device to at least: Determine whether the target resource allocated to the first device is offset relative to the reference resource; Transmitting a random access response to a random access request from the first device to the first device, wherein at least one of the random access response or paging message is based on a deterministic result; and Receive transmissions from the first device using the target resource.

[0226] Example 12. A second apparatus according to Example 11, wherein the target resource is offset relative to a reference resource, and at least one of a random access response or paging message indicates the resource offset from the target resource to the reference resource for the first apparatus.

[0227] Example 13. According to the second apparatus of Example 12, the resource offset is indicated in a paging message, the paging message including at least one paging record corresponding to at least one device identifier, and the paging record corresponding to the device identifier of the first apparatus including the offset value of the resource offset.

[0228] Example 14. The second device according to Example 11, wherein the second device is further configured such that: System information is transmitted to the first device to indicate a reference resource through information elements in the system information.

[0229] Example 15. A second apparatus according to Example 11, wherein the reference resources include resources for the transmission of message A in a two-step random access procedure.

[0230] Example 16. A second device according to Example 11, wherein the second device is further configured such that: Resources used for shared channel transmission without random access procedures are designated as reference resources; and Transmit information indicating the determined resources to the first device.

[0231] Example 17. A second device according to Example 14, wherein the second device is such that: Based on the estimated size of the transmission and reference resources, target resources are reserved for the second device.

[0232] Example 18. A second apparatus according to Example 11, wherein the resource offset corresponds to the number of physical resource blocks.

[0233] Example 19. A second device according to Example 11, wherein the first device is a terminal device or is included in a terminal device, and the second device is a network device or is included in a network device.

[0234] Example 20. A method for communication, comprising: Receive a random access response to the random access request from the second device; The target resource is determined based on whether at least one of the reference resource and the random access response or the paging message from the second device indicates a resource offset for the first device; and In response to the random access response, a transmission is performed to the second device using the target resource.

[0235] Example 21. A method for communication, comprising: Determine whether the target resource allocated to the first device is offset relative to the reference resource; Transmitting a random access response to a random access request from the first device to the first device, wherein at least one of the random access response or paging message is based on a deterministic result; and Receive transmissions from the first device using the target resource.

[0236] Example 22. A first device for communication, comprising: A component for receiving a random access response to a random access request from a second device; Components for determining a target resource based on whether at least one of a reference resource and a random access response or a paging message from a second device indicates a resource offset for a first device; and A component used to perform a transmission to a second device using the target resource in response to a random access response.

[0237] Example 23. A second means for communication, comprising: A component used to determine whether the target resource allocated to the first device is offset relative to a reference resource; Components for transmitting a random access response to a random access request from a first device, wherein at least one of the random access response or a paging message is based on a determined result; and A component used to receive transmissions from a first device using target resources.

[0238] Example 24. A computer-readable medium including instructions stored thereon for causing a device to perform at least the method according to Example 21 or Example 22.

Claims

1. A first device for communication, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the first device to at least: Receive a random access response to the random access request from the second device; The target resource is determined based on whether at least one of the reference resource and the random access response or the paging message from the second device indicates a resource offset for the first device. as well as In response to the random access response, a transmission is performed to the second device using the target resource.

2. The first device according to claim 1, wherein the first device is configured to: The target resource is determined by applying the resource offset relative to the reference resource, based on determining that at least one of the random access response or the paging message indicates the resource offset for the first device.

3. The first apparatus of claim 1, wherein the resource offset is indicated in the paging message, the paging message including at least one paging record corresponding to at least one device identifier, and the paging record corresponding to the device identifier of the first apparatus including an offset value of the resource offset.

4. The first device according to claim 1, wherein the first device is configured to: Based on the determination that the resource offset is not indicated for the first device, at least a portion of the reference resource is identified as the target resource.

5. The first device according to claim 1, wherein the first device is further configured to: Receive system information from the second device; and The reference resource is determined based on the information elements in the system information.

6. The first apparatus of claim 1, wherein the reference resources include resources for transmitting message A during a two-step random access process.

7. The first device according to claim 1, wherein the first device is configured such that: Receive information from the second device, the information indicating resources for shared channel transmission without a random access procedure; and The reference resource is determined based on the indicated resource.

8. The first device according to claim 5, wherein the first device is configured to: The size of the target resource is determined based on the size of the transmission to be performed.

9. The first apparatus of claim 1, wherein the resource offset corresponds to the number of physical resource blocks.

10. The first device according to claim 1, wherein the first device is a terminal device or is included in the terminal device, and the second device is a network device or is included in the network device.

Images