Method and apparatus for a two-step random access procedure

Abstract

Various embodiments of the present disclosure provide a method and apparatus for a two-step random access procedure. A method performed by a terminal device includes: determining a preamble for the two-step random access procedure, determining an RNTI for the two-step random access procedure based on radio network temporary identifier RNTI information, generating a physical uplink shared channel PUSCH message based on the determined RNTI, and sending a request message including a preamble and a PUSCH message in the two-step random access procedure.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communications, and more particularly, to methods and apparatus for a two-step random access procedure. Background Art

[0002] This section introduces aspects that help to better understand the present disclosure. Therefore, the statements in this section should be read from this perspective and should not be understood as an admission that what is included in the prior art or what is not included in the prior art.

[0003] In the New Radio (NR) system, a four-step method can be used for the random access process, such as Figure 1 As shown. In the method, a user equipment (UE) detects synchronization signals (SS) including an NR primary synchronization signal (NR-PSS), an NR secondary synchronization signal (NR-SSS), and an NR physical broadcast channel (PBCH) signal, and decodes the broadcasted system information (e.g., remaining minimum system information (RMSI)). The UE may then send a physical random access channel (PRACH) preamble (message 1) in an uplink (UL). In response to receiving the message 1, a base station (e.g., a next generation Node B (gNB)) replies with a random access response (RAR, message 2). The RAR message is octet aligned and includes a timing advance command, an UL grant, and a temporary cell radio network temporary identifier (TC-RNTI).

[0004] After receiving the RAR message, the UE can send Message 3 including the UE identity and the transport block on the Physical Uplink Shared Channel (PUSCH). The gNB then replies with a Contention Resolution message (Message 4). The timing advance command in the RAR message allows Message 3 to be received with a timing accuracy within the cyclic prefix (CP). Without this timing advance, unless the system is applied in a cell with a very small distance between the UE and the gNB, a very large CP would be required to be able to demodulate and detect Message 3. Since NR will also support larger cells that need to provide timing advance to the UE, the random access procedure requires a four-step approach.

[0005] Message 3 is scheduled by the UL grant in the RAR message. Retransmissions of the transport blocks in Message 3 (if any) are scheduled by DCI format 0_0, where the CRC is scrambled by the TC-RNTI provided in the RAR message. The UE always sends Message 3 without repetitions.

[0006] In 3GPP TS38.321, Table 1 is provided to define the range of RNTI values, as shown below.

[0007] Table 1

[0008]

[0009] The two-step random access procedure has been approved as a work item for NR Release 16. Figure 2 As shown, initial access is done in only two steps. In the first step, the UE sends a message, which may be referred to as message A, which includes a random access preamble and higher layer data (such as a radio resource control (RRC) connection request, possibly with some small payload on PUSCH). In the second step, the gNB sends a response message to the UE, which may be referred to as message B and includes, for example, UE identifier allocation, timing advance information, and contention resolution information. Summary of the invention

[0010] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0011] The present disclosure proposes an improved solution for a two-step random access procedure.

[0012] According to a first aspect of the present disclosure, a method performed by a terminal device is provided. The method comprises: determining a preamble for a two-step random access procedure, determining an RNTI for the two-step random access procedure based on radio network temporary identifier RNTI information, and generating a physical uplink shared channel PUSCH message based on the determined RNTI. The method also comprises sending a request message including a preamble and a PUSCH message in the two-step random access procedure.

[0013] According to an exemplary embodiment, the preamble may be determined from a preamble set, and the RNTI information may indicate an association between the preamble set and the RNTI set.

[0014] According to an exemplary embodiment, the association can be any of the following: a one-to-one mapping between a preamble in a preamble set and an RNTI in an RNTI set, a one-to-many mapping between a preamble in a preamble set and two or more RNTIs in an RNTI set, or a many-to-one mapping between two or more preambles in a preamble set and an RNTI in an RNTI set.

[0015] According to an exemplary embodiment, the RNTI may be determined based on the determined preamble.

[0016] According to an exemplary embodiment, the RNTI information may indicate an association between a physical random access channel PRACH opportunity set and a RNTI set.

[0017] According to an exemplary embodiment, the association can be any of the following: a one-to-one mapping between a PRACH opportunity in a PRACH opportunity set and an RNTI in an RNTI set, a one-to-many mapping between a PRACH opportunity in a PRACH opportunity set and two or more RNTIs in an RNTI set, or a many-to-one mapping between two or more PRACH opportunities in a PRACH opportunity set and an RNTI in an RNTI set.

[0018] According to an exemplary embodiment, the RNTI may be determined based on a PRACH opportunity for the determined preamble.

[0019] According to an exemplary embodiment, the RNTI information may indicate at least one RNTI.

[0020] According to an exemplary embodiment, the RNTI information may indicate a plurality of RNTIs. Further, the RNTI may be randomly determined from the plurality of RNTIs.

[0021] According to an exemplary embodiment, the preamble may be associated with a PUSCH time-frequency resource.

[0022] According to an exemplary embodiment, the RNTI information may be predefined or signaled in a signaling message.

[0023] According to an exemplary embodiment, the preamble may be determined according to preamble information, and the preamble information may be predefined or signaled in a signaling message.

[0024] According to an exemplary embodiment, the signaling message may be a Radio Resource Control, RRC, message.

[0025] According to an exemplary embodiment, the method may further include: in response to sending the request message, receiving a response message including the selected RNTI. Further, the selected RNTI may be used in a subsequent two-step random access procedure.

[0026] According to an exemplary embodiment, the response message may be received on a physical downlink shared channel, PDSCH, or a physical downlink control channel, PDCCH.

[0027] According to a second aspect of the present disclosure, a method performed by a network node is provided. The method comprises: in a two-step random access procedure, receiving a request message including a preamble and a physical uplink shared channel (PUSCH) message, the PUSCH message being based on an RNTI determined according to radio network temporary identifier (RNTI) information.

[0028] According to an exemplary embodiment, receiving the request message may include detecting a preamble in the request message, determining a RNTI based on the detected preamble according to the RNTI information, and decoding the PUSCH message based on the determined RNTI.

[0029] According to an exemplary embodiment, receiving the request message may include detecting a preamble in the request message, determining a RNTI based on a PRACH opportunity for the detected preamble according to the RNTI information, and decoding the PUSCH message based on the determined RNTI.

[0030] According to an exemplary embodiment, receiving the request message may include detecting a preamble in the request message, and blindly decoding the PUSCH message based on the multiple RNTIs.

[0031] According to an exemplary embodiment, the method may further include: in response to successfully detecting the preamble in the request message and failing to decode the PUSCH message, generating a random access RA-RNTI based on the detected preamble, and sending a response message based on the RA-RNTI, the response message including the selected RNTI to be used in a subsequent two-step random access process.

[0032] According to an exemplary embodiment, the response message may be sent on a physical downlink shared channel, PDSCH, or a physical downlink control channel, PDCCH.

[0033] According to a third aspect of the present disclosure, a terminal device is provided. The terminal device may include one or more processors and one or more memories including computer program code. The one or more memories and the computer program code may be configured to, together with the one or more processors, cause the terminal device to at least perform any step of the method according to the first aspect of the present disclosure.

[0034] According to a fourth aspect of the present disclosure, there is provided a computer readable medium having computer program code embodied thereon, the computer program code when executed on a computer causes the computer to perform any step of the method according to the first aspect of the present disclosure.

[0035] According to a fifth aspect of the present disclosure, a network node is provided. The network node may include one or more processors and one or more memories including computer program code. The one or more memories and the computer program code may be configured to, together with the one or more processors, cause the network node to at least perform any step of the method according to the second aspect of the present disclosure.

[0036] According to a sixth aspect of the present disclosure, there is provided a computer readable medium having computer program code embodied thereon, the computer program code when executed on a computer causes the computer to perform any step of the method according to the second aspect of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The present disclosure itself, the preferred mode of use and further objects may be best understood by reference to the following detailed description of embodiments when read in conjunction with the accompanying drawings, in which:

[0038] Figure 1 is a diagram illustrating a four-step random access procedure in NR;

[0039] Figure 2 is a diagram illustrating a two-step random access procedure in NR;

[0040] Figure 3 is a flow chart illustrating a method performed by a terminal device according to some embodiments of the present disclosure;

[0041] Figure 4 is a flow chart illustrating a method performed by a network node according to some embodiments of the present disclosure;

[0042] Figure 5 is a block diagram illustrating an apparatus according to some embodiments of the present disclosure;

[0043] Figure 6 is a block diagram illustrating an apparatus according to some embodiments of the present disclosure;

[0044] Figure 7 is a block diagram illustrating an apparatus according to some embodiments of the present disclosure;

[0045] Figure 8 is a block diagram illustrating a telecommunications network connected to a host computer via an intermediate network according to some embodiments of the present disclosure;

[0046] Fig. 9 is a block diagram illustrating a host computer communicating with a UE via a base station over a partial wireless connection according to some embodiments of the present disclosure;

[0047] Fig.10 is a flow chart illustrating a method implemented in a communication system according to an embodiment of the present disclosure;

[0048] Fig.11 is a flow chart illustrating a method implemented in a communication system according to an embodiment of the present disclosure;

[0049] Fig.12 is a flow chart illustrating a method implemented in a communication system according to an embodiment of the present disclosure;

[0050] Fig.13 is a flowchart illustrating a method implemented in a communication system according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0051] Embodiments of the present disclosure are described in detail in conjunction with the accompanying drawings. It should be understood that these embodiments are discussed only to enable those skilled in the art to better understand and thus implement the present disclosure, rather than to imply any limitation on the scope of the present disclosure. Mentioning features, advantages or similar language throughout the specification does not imply that all features and advantages that can be implemented with the present disclosure should be in or in any single embodiment of the present disclosure. On the contrary, the language of mentioning features and advantages is understood to mean that the specific features, advantages or characteristics described in conjunction with the embodiments are included in at least one embodiment of the present disclosure. In addition, the described features, advantages and characteristics of the present disclosure can be combined in any suitable manner in one or more embodiments. Those skilled in the relevant art will recognize that the present disclosure can be practiced without one or more specific features or advantages of a particular embodiment. In other cases, additional features and advantages that may not exist in all embodiments of the present disclosure can be recognized in certain embodiments.

[0052] As used herein, the term "communication network" refers to a network that complies with any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), etc. In addition, the communication between the terminal devices and the network nodes in the communication network can be performed according to any suitable generation of communication protocols, including but not limited to first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), 4G, 4.5G, 5G communication protocols and / or any other currently known or future developed protocols.

[0053] The term "network node" refers to a network device in a communication network, via which a terminal device accesses the network and receives services from the network. A network node or network device may refer to a base station (BS), an access point (AP), a multi-cell / multicast coordination entity (MCE), a controller, or any other suitable device in a wireless communication network. A BS may be, for example, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), a next generation Node B (gNodeB or gNB), an IAB node, a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, a low power node (such as a femto node, a micro node, etc.).

[0054] Further examples of network nodes include multi-standard radio (MSR) radio equipment (such as an MSR BS), a network controller (such as a radio network controller (RNC) or a base station controller (BSC)), a base transceiver station (BTS), a transmission point, a transmission node, a positioning node, etc. However, more generally, a network node may represent any suitable device (or group of devices) that is capable of, configured, arranged and / or operable to enable and / or provide a terminal device with access to a wireless communication network or to provide a certain service to a terminal device that has accessed the wireless communication network.

[0055] The term "terminal device" refers to any terminal device that can access a communication network and receive services therefrom. As an example and not limitation, a terminal device may refer to a user equipment (UE) or other suitable device. A UE may be, for example, a subscriber station, a portable subscriber station, a mobile station (MS), or an access terminal (AT). A terminal device may include, but is not limited to, a portable computer, an image acquisition terminal device (such as a digital camera), a game terminal device, a music storage and playback device, a mobile phone, a cellular phone, a smart phone, a tablet computer, a wearable device, a personal digital assistant (PDA), a vehicle, etc.

[0056] As another specific example, in an Internet of Things (IoT) scenario, a terminal device may also be referred to as an IoT device, and refers to a machine or other device that performs monitoring, sensing, and / or measurement, etc., and sends the results of such monitoring, sensing, and / or measurement, etc. to another terminal device and / or network device. In this case, the terminal device may be a machine-to-machine (M2M) device, which may be referred to as a machine type communication (MTC) device in the context of the Third Generation Partnership Project (3GPP).

[0057] As a specific example, the terminal device may be a UE that implements the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices (such as power meters), industrial machinery, or household or personal appliances (such as refrigerators, televisions, personal wearable devices such as watches, etc.). In other scenarios, the terminal device may represent a vehicle or other device that is capable of monitoring, sensing and / or reporting its operating status or other functions associated with its operation, such as medical instruments.

[0058] As used herein, the terms "first", "second", etc. refer to different elements. The singular forms "one" and "an" are also intended to include the plural forms, unless the context clearly indicates otherwise. As used herein, the terms "comprise", "comprising", "having", "having", "including" and / or "comprising" 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. The term "based on" should be understood as "based at least in part on". The terms "one embodiment" and "embodiment" should be understood as "at least one embodiment". The term "another embodiment" should be understood as "at least one other embodiment". Other definitions (explicit and implicit) may be included below.

[0059] As mentioned above, in Figure 2 In the two-step random access procedure shown, the preamble and PUSCH message will be sent by the UE in one message called message A. However, for the PUSCH message in message A, since no RAR message is received from the gNB, there is no TC-RNTI available for PUSCH processing. Therefore, it is desirable to provide a solution for determining the RNTI for PUSCH in message A of the two-step random access procedure.

[0060] According to some exemplary embodiments, the present disclosure provides an improved solution for a two-step random access procedure. These solutions can be applied to a wireless communication system including a terminal device and a base station. In the two-step random access procedure, the terminal device can determine the RNTI to be used for the PUSCH in the request message (e.g., message A) based on the RNTI information, and then the terminal device can send the request message based on the determined RNTI. With the improved solution, the RNTI for the PUSCH in message A can be determined.

[0061] Note that some embodiments of the present disclosure are primarily described with respect to the 5G specification used as non-limiting examples of certain exemplary network configurations and system deployments. Therefore, the description of the exemplary embodiments given herein specifically refers to terms directly related thereto. Such terms are used only in the context of the non-limiting examples and embodiments presented and do not inherently limit the present disclosure in any way. Instead, any other system configuration or radio technology may be equally utilized as long as the exemplary embodiments described herein are applicable.

[0062] Figure 3 is a flow chart illustrating a method 300 according to some embodiments of the present disclosure. Figure 3 The illustrated method 300 may be performed by an apparatus implemented in a terminal device or communicatively coupled to the terminal device.According to an exemplary embodiment, the terminal device may be a UE.

[0063] according to Figure 3 In the illustrated exemplary method 300, the terminal device determines a preamble for a two-step random access procedure, as shown in box 302. In some embodiments, the preamble may be determined based on preamble information. In one embodiment, the preamble information may indicate a preamble set. The preamble set may be dedicated to the two-step random access procedure. Alternatively, the preamble set may be the same as the preamble set for the four-step random access procedure. In some embodiments, the preamble information may further indicate a time-frequency PRACH opportunity (hereinafter referred to as "PRACH opportunity") set. The terminal device may select a PRACH opportunity in the PRACH opportunity set to send a preamble on the PRACH.

[0064] In some embodiments, the preamble information may be signaled in a signaling message from a network node such as a base station (e.g., a gNB). The signaling message may be a radio resource control (RRC) message. Alternatively, in some embodiments, the preamble information may be predefined in the terminal device.

[0065] In some embodiments, the preamble of the preamble set in the preamble information may be associated with the PUSCH time-frequency resources. Therefore, the PUSCH time-frequency resources may be determined based on the preamble. For example, the terminal device may have a mapping table indicating the association between the preamble set and the PUSCH time-frequency resources. After determining the preamble, the terminal device may determine the PUSCH time-frequency resources to be used for the PUSCH message based on the determined preamble. On the other hand, once the PUSCH time-frequency resources for the two-step random access process are determined, the terminal device may also determine the preamble based on the determined PUSCH time-frequency resources.

[0066] [In step 304, the terminal device determines the RNTI for the two-step random access procedure according to the RNTI information. In some embodiments, the RNTI information may indicate an association between a preamble set and an RNTI set in the preamble information. Therefore, the RNTI may be determined based on the preamble.

[0067] In an embodiment, the association may be a one-to-one mapping between a preamble in a preamble set and an RNTI in an RNTI set. For example, assuming that the preamble information indicates a set of 64 preambles, each preamble is assigned a unique preamble ID ranging from 0 to 63. Each preamble is mapped to an RNTI for PUSCH, as shown in Table 2 below.

[0068] Table 2

[0069] Preamble ID RNTI for PUSCH 0 FF00 1 FF01 2 FF02 … … 61 FF3D 62 FF3E 63 FF3F

[0070] In an embodiment, the association may be a one-to-many mapping between a preamble in a preamble set and two or more RNTIs in an RNTI set. In this case, each preamble is mapped to two or more RNTIs. Based on the determined preamble, the terminal device may randomly select an RNTI from the corresponding two or more RNTIs. Alternatively, in an embodiment, the association may be a many-to-one mapping between two or more preambles in a preamble set and one RNTI in an RNTI set. In this case, two or more preambles are mapped to one RNTI.

[0071] As described above, there may also be an association between the preamble set and the PUSCH time-frequency resources. Therefore, in some embodiments, the RNTI may be determined based on the PUSCH time-frequency resources. For example, when determining the PUSCH time-frequency resources for a two-step random access process, the terminal device may determine the preamble based on the association between the preamble set and the PUSCH time-frequency resources, and then determine the RNTI based on the association between the preamble set and the RNTI set. More directly, there may be an association between the PUSCH time-frequency resources and the RNTI. In this way, when determining the PUSCH time-frequency resources, the corresponding RNTI may be determined.

[0072] Alternatively, in some embodiments, the RNTI information may indicate an association between a PRACH opportunity set and an RNTI set. Thus, the RNTI may be determined based on the PRACH opportunity. After determining the preamble, the terminal device may determine the RNTI based on the PRACH opportunity used for the determined preamble. In an embodiment, the PRACH opportunity set may also be indicated in the preamble information.

[0073] In an embodiment, the association may be a one-to-one mapping between a PRACH opportunity in a PRACH opportunity set and an RNTI in an RNTI set. In this case, each PRACH opportunity is mapped to one RNTI. Alternatively, in one embodiment, the association may be a one-to-many mapping between a PRACH opportunity in a PRACH opportunity set and two or more RNTIs in an RNTI set. In this case, each PRACH opportunity is mapped to two or more RNTIs. Based on the PRACH for the determined preamble, the terminal device may randomly select an RNTI from the corresponding two or more RNTIs. Alternatively, in one embodiment, the association may be a many-to-one mapping between two or more PRACH opportunities in a PRACH opportunity set and an RNTI in an RNTI set. In this case, two or more PRACH opportunities are mapped to one RNTI.

[0074] Alternatively, in some embodiments, the RNTI information may indicate at least one RNTI. In an embodiment, the RNTI information may indicate only one RNTI. In this case, the same RNTI is used for PUSCH for different preambles. In order to mitigate PUSCH conflicts between different terminal devices, different PUSCH time-frequency resources and different PRACH opportunities may be allocated.

[0075] Alternatively, in an embodiment, the RNTI information may indicate multiple RNTIs. In this case, the terminal device may randomly determine one RNTI from the multiple RNTIs. For example, a set of three RNTIs may be indicated in the RNTI information, and the terminal device may randomly select any one of the three RNTIs.

[0076] In some embodiments, the RNTI information may be signaled in a signaling message from a network node such as a base station (e.g., a gNB). The signaling message may be a radio resource control (RRC) message. Alternatively, in some embodiments, the RNTI information may be pre-defined in the terminal device.

[0077] After determining the RNTI in block 304, in block 306, the terminal device generates a PUSCH message based on the determined RNTI. Typically, the RNTI is used for PUSCH scrambling sequence initialization. Then, in block 308, the terminal device sends a request message to the network node in a two-step random access procedure. The request message may include the preamble determined in block 302 and the PUSCH message generated in block 306. The preamble may be sent in a PRACH opportunity, and the PUSCH message may be sent in a PUSCH time-frequency resource.

[0078] In addition, in some embodiments, in response to sending the request message, the terminal device may receive a response message, as shown in box 310. In some embodiments, the response message may include the selected RNTI. If the network node fails to decode the PUSCH message when the preamble in the request message is successfully detected, the network node may select an RNTI for the subsequent two-step random access process and send a response message including the selected RNTI to the terminal device. After receiving the response message, the terminal device may obtain the selected RNTI and use it in the subsequent random access process instead of determining the RNTI based on the RNTI information. In addition, the selected RNTI may be added to the RNTI information stored in the terminal device. In some embodiments, the response message may be received on the physical downlink shared channel PDSCH. Alternatively, the response message may be received as control information on the physical downlink control channel PDCCH.

[0079] Please note that executing Figure 3The order of the steps shown is illustrated only as an example. In some implementations, some steps can be performed in reverse order or in parallel. In some other implementations, some steps can be omitted or combined.

[0080] Figure 4 is a flow chart illustrating a method 400 according to some embodiments of the present disclosure. Figure 4 The illustrated method 400 may be performed by an apparatus implemented in a network node or communicatively coupled to a network node. According to an exemplary embodiment, the network node may be a base station, such as a gNB. Figure 4 In the description of the exemplary embodiment, for the parts that are the same as or similar to those in the aforementioned exemplary embodiment, the detailed description will be appropriately omitted.

[0081] according to Figure 4 In the illustrated exemplary method 400, the network node may receive a request message including a preamble and a PUSCH message in a two-step random access process, as shown in block 402. In some embodiments, the preamble may be determined based on preamble information, and the PUSCH message may be based on an RNTI determined based on RNTI information. The details of the preamble information and the RNTI information have been described above and will not be repeated here.

[0082] In some embodiments where the RNTI information indicates an association between a preamble set in the preamble information and an RNTI set, the network node may detect the preamble in the request message and determine the RNTI based on the detected preamble according to the RNTI information stored in the network node. The network node may then decode the PUSCH message based on the determined RNTI.

[0083] In some embodiments where the RNTI information indicates an association between a PRACH opportunity set in the preamble information and an RNTI set, the network node may detect the preamble in the request message and, based on the RNTI information, determine the RNTI based on the PRACH opportunity for the detected preamble. The network node may then decode the PUSCH message based on the determined RNTI.

[0084] In some embodiments where the RNTI information indicates one RNTI, the network node may detect the preamble in the request message and decode the PUSCH message based on the one RNTI. In some embodiments where the RNTI information indicates multiple RNTIs, the network node may detect the preamble in the request message and blindly decode the PUSCH message based on the multiple RNTIs.

[0085] Further, in some embodiments, if the network node successfully detects the preamble in the request message and fails to decode the PUSCH message, the network node may generate a RA-RNTI based on the detected preamble, as shown in block 404. In some embodiments, the generation of the RA-RNTI may also be based on the PRACH opportunity for the detected preamble. Then in block 406, the network node may send a response message based on the RA-RNTI. The RA-RNTI may be used to scramble the response message. In some embodiments, the response message may include a selected RNTI to be used in a subsequent two-step random access process. In some embodiments, the response message may be sent on a PDCCH or a PDSCH.

[0086] Therefore, it can be seen that, by adopting the solution for the two-step random access process proposed according to the above embodiment, the terminal device can determine the RNTI for the PUSCH in the request message during the two-step random access process.

[0087] exist Figure 3 and Figure 4 The various blocks shown in the figure may be viewed as method steps and / or operations resulting from the operation of computer program code and / or multiple coupled logic circuit elements constructed to perform the associated (one or more) functions. Figure 1 The method of the present invention is generally described as a logical flow chart. Therefore, the order depicted and the steps labeled indicate a specific embodiment of the method presented. Other steps and methods that are equivalent in function, logic or effect to one or more steps or portions thereof of the method illustrated can be envisioned. In addition, the order in which a particular method occurs may or may not strictly follow the order of the corresponding steps shown.

[0088] Figure 5 is a block diagram illustrating an apparatus 500 according to various embodiments of the present disclosure. Figure 5 As shown, the apparatus 500 may include one or more processors (such as processor 501) and one or more memories (such as memory 502 storing computer program code 503). The memory 502 may be a non-transitory machine / processor / computer readable storage medium. According to some exemplary embodiments, the apparatus 500 may be implemented as an integrated circuit chip or module, which may be inserted or installed in a computer program. Figure 3 The terminal device described or Figure 4 In the network node described.

[0089] In some implementations, the one or more memories 502 and the computer program code 503 may be configured to work with the one or more processors 501 to cause the apparatus 500 to at least perform the combined Figure 3Any operation of the method described. In such an embodiment, the apparatus 500 may be implemented as at least a part of a terminal device as described above or be communicatively coupled to a terminal device as described above. As a specific example, the apparatus 500 may be implemented as a terminal device.

[0090] In other implementations, the one or more memories 502 and the computer program code 503 may be configured to work with the one or more processors 501 to cause the apparatus 500 to at least perform the following steps: Figure 4 Any operation of the method described. In such an embodiment, the apparatus 500 may be implemented as at least a part of a network node as described above or be communicatively coupled to a network node as described above. As a specific example, the apparatus 500 may be implemented as a network node.

[0091] Alternatively or additionally, the one or more memories 502 and the computer program code 503 may be configured to, together with the one or more processors 501 , enable the apparatus 500 to at least perform more or fewer operations to implement the method according to the exemplary embodiments of the present disclosure.

[0092] Figure 6 6 is a block diagram illustrating an apparatus 600 according to some embodiments of the present disclosure. Figure 6 As shown, the apparatus 600 may include a determining unit 601, a generating unit 602, and a sending unit 603. In an exemplary embodiment, the apparatus 600 may be implemented in a terminal device such as a UE. The determining unit 601 may be operable to perform the operations in boxes 302 and 304. The generating unit 602 may be operable to perform the operations in box 306, and the sending unit 603 may be operable to perform the operations in box 308. Further, the apparatus 600 may also include a receiving unit 604 operable to perform the operations in box 310. Optionally, the determining unit 601, the generating unit 602, the sending unit 603, and / or the receiving unit 604 may be operable to perform more or less operations to implement the method according to the exemplary embodiments of the present disclosure.

[0093] Figure 7 7 is a block diagram illustrating an apparatus 700 according to some embodiments of the present disclosure. Figure 7As shown, the apparatus 700 may include a receiving unit 701. In an exemplary embodiment, the apparatus 700 may be implemented in a network node such as a base station (e.g., a gNB or an eNB). The receiving unit 701 may be operable to perform the operations in box 402. Further, the apparatus 700 may also include a generating unit 702 and a sending unit 703. The generating unit 702 may be operable to perform the operations in box 404, and the sending unit 706 may be operable to perform the operations in box 406. Optionally, the receiving unit 701, the generating unit 702 and / or the sending unit 703 may be operable to perform more or less operations to implement the method according to the exemplary embodiments of the present disclosure.

[0094] Figure 8 is a block diagram illustrating a telecommunications network connected to a host computer via an intermediary network according to some embodiments of the present disclosure.

[0095] refer to Figure 8 According to an embodiment, a communication system includes a telecommunication network 810 (such as a 3GPP type cellular network), the telecommunication network 810 includes an access network 811 (such as a radio access network) and a core network 814. The access network 811 includes a plurality of base stations 812a, 812b, 812c, such as NBs, eNBs, gNBs or other types of wireless access points, each of which defines a corresponding coverage area 813a, 813b, 813c. Each base station 812a, 812b, 812c may be connected to the core network 814 via a wired or wireless connection 815. A first UE 891 located in the coverage area 813c is configured to be wirelessly connected to or paged by the corresponding base station 812c. A second UE 892 in the coverage area 813a may be wirelessly connected to the corresponding base station 812a. Although multiple UEs 891, 892 are illustrated in this example, the disclosed embodiments are equally applicable to situations where a sole UE is in the coverage area or a sole UE is connected to the corresponding base station 812.

[0096] The telecommunications network 810 itself is connected to a host computer 830, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 830 may be under the ownership or control of a service provider, or may be operated by or on behalf of a service provider. Connections 821 and 822 between the telecommunications network 810 and the host computer 830 may extend directly from the core network 814 to the host computer 830, or may be made via an optional intermediate network 820. The intermediate network 820 may be one of a public, private, or managed network, or a combination of more than one of these networks; the intermediate network 820 (if any) may be a backbone network or the Internet; in particular, the intermediate network 820 may include two or more sub-networks (not shown).

[0097] Figure 8 The communication system as a whole realizes the connectivity between the connected UE 891, 892 and the host computer 830. This connectivity can be described as an over-the-top (OTT) connection 850. The host computer 830 and the connected UE 891, 892 are configured to use the access network 811, the core network 814, any intermediate network 820 and possibly another infrastructure (not shown) as intermediaries to pass data and / or signaling via the OTT connection 850. The OTT connection 850 is transparent in the sense that the participating communication devices through which the OTT connection 850 passes do not know the routes of the uplink and downlink communications. For example, the base station 812 may not or need not be informed of the past routes of the incoming downlink communications of the data originating from the host computer 830 to be forwarded (e.g., handed over) to the connected UE 891. Similarly, the base station 812 does not need to know the future routes of the outgoing uplink communications originating from the UE 891 toward the host computer 830.

[0098] Fig. 9 is a block diagram illustrating a host computer communicating with a UE via a base station over a partially wireless connection according to some embodiments of the present disclosure.

[0099] According to the embodiment, reference will now be made to Fig. 9910 to describe the example implementation of the UE, base station, and host computer discussed in the previous paragraphs. In the communication system 900, the host computer 910 includes hardware 915, which includes a communication interface 916 configured to establish and maintain a wired or wireless connection with different communication devices of the communication system 900. The host computer 910 also includes a processing circuit 918, which may have storage and / or processing capabilities. In particular, the processing circuit 918 may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination thereof (not shown) suitable for executing instructions. The host computer 910 also includes software 911, which is stored in the host computer 910 or can be accessed by the host computer 910 and can be executed by the processing circuit 918. The software 911 includes a host application 912. The host application 912 may be operable to provide services to remote users such as UE 930 via an OTT connection 950 terminated at the UE 930 and the host computer 910. In providing services to remote users, the host application 912 may provide user data that is sent using the OTT connection 950 .

[0100] The communication system 900 also includes a base station 920, which is provided in the telecommunication system and includes hardware 925 that enables it to communicate with the host computer 910 and the UE 930. The hardware 925 may include a communication interface 926 for establishing and maintaining a wired or wireless connection with different communication devices of the communication system 900, and for establishing and maintaining a connection with at least a network located in a coverage area ( Fig. 9 The communication interface 926 may be configured to facilitate a connection 960 to the host computer 910. The connection 960 may be direct, or it may pass through a core network (eg, a wireless network) of the telecommunications system. Fig. 9 The base station 920 may be configured to communicate with the user through a communication channel (not shown) and / or traverse one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 925 of the base station 920 also includes processing circuitry 928, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute the instructions. The base station 920 also has software 921 stored internally or accessible via an external connection.

[0101] The communication system 900 also includes the UE 930 already mentioned. Its hardware 935 may include a radio interface 937 configured to establish and maintain a wireless connection 970 with a base station serving the coverage area where the UE 930 is currently located. The hardware 935 of the UE 930 also includes a processing circuit 938, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination thereof (not shown) suitable for executing instructions. The UE 930 also includes software 931, which is stored in the UE 930 or can be accessed by the UE 930 and can be executed by the processing circuit 938. The software 931 includes a client application 932. The client application 932 may be operable to provide services to human or non-human users via the UE 930 with the support of the host computer 910. In the host computer 910, the execution of the host application 912 can communicate with the execution of the client application 932 via an OTT connection 950 terminated at the UE 930 and the host computer 910. When providing services to users, the client application 932 can receive request data from the host application 912 and provide user data in response to the request data. The OTT connection 950 can transmit the request data and the user data. The client application 932 can interact with the user to generate the user data it provides.

[0102] Notice, Fig. 9 The host computer 910, base station 920 and UE 930 shown in FIG. Figure 8 The host 830, one of the base stations 812a, 812b, 812c, and one of the UEs 891, 892 are similar or identical. That is, the internal working principles of these entities can be as follows Fig. 9 As shown, and independently, the surrounding network topology can be as Figure 8 shown.

[0103] exist Fig. 9 In the figure, the OTT connection 950 has been abstractly drawn to illustrate the communication between the host computer 910 and the UE 930 via the base station 920, without explicitly mentioning any intermediate devices and the precise message routing via these intermediate devices. The network infrastructure can determine the route, which can be configured to be hidden from the UE 930 or from the service provider operating the host computer 910, or both. When the OTT connection 950 is active, the network infrastructure can further make decisions to dynamically change the route (e.g., based on load balancing considerations or reconfiguration of the network).

[0104] The wireless connection 970 between the UE 930 and the base station 920 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE 930 using the OTT connection 950, in which the wireless connection 970 forms the last leg. More specifically, the teachings of these embodiments can improve latency and power consumption, thereby providing advantages such as reduced complexity, reduced time required to access a cell, better responsiveness, and extended battery life.

[0105] A measurement process may be provided for monitoring data rate, latency, and other factors improved by one or more embodiments. There may also be an optional network function for reconfiguring the OTT connection 950 between the host computer 910 and the UE 930 in response to changes in the measurement results. The measurement process and / or network function for reconfiguring the OTT connection 950 may be implemented in the software 911 and hardware 915 of the host computer 910 or in the software 931 and hardware 935 of the UE 930 or in both. In an embodiment, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection 950 passes; the sensor may participate in the measurement process by providing the values ​​of the monitoring quantities exemplified above or providing the values ​​of other physical quantities, and the software 911, 931 may calculate or estimate the monitoring quantities based on these values. The reconfiguration of the OTT connection 950 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not need to affect the base station 920, and it may be unknown or imperceptible to the base station 920. Such processes and functions may be known and practiced in the art. In certain embodiments, the measurements may involve proprietary UE signaling that facilitates measurement of throughput, propagation time, latency, etc., by the host computer 910. The measurements may be implemented because the software 911 and 931 causes messages to be sent using the OTT connection 950, particularly empty or "dummy" messages, while it monitors propagation time, errors, etc.

[0106] Fig.10 is a flow chart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Figure 8 and Fig. 9 For the simplicity of this disclosure, only Fig.10. In step 1010, the host computer provides user data. In sub-step 1011 of step 1010 (which may be optional), the host computer provides the user data by executing a host application. In step 1020, the host computer initiates a transmission to the UE carrying the user data. In step 1030 (which may be optional), in accordance with the teachings of the embodiments described throughout the present disclosure, the base station sends the user data carried in the transmission initiated by the host computer to the UE. In step 1040 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0107] Fig.11 is a flow chart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Figure 8 and Fig. 9 For the simplicity of this disclosure, only Fig.11 . In step 1110 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step 1120, the host initiates a transmission to the UE carrying the user data. According to the teachings of the embodiments described throughout the present disclosure, the transmission may pass through a base station. In step 1130 (which may be optional), the UE receives the user data carried in the transmission.

[0108] Fig.12 is a flow chart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Figure 8 and Fig. 9 For the simplicity of this disclosure, only Fig.12 . In step 1210 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1220, the UE provides user data. In sub-step 1221 of step 1220 (which may be optional), the UE provides user data by executing a client application. In sub-step 1211 of step 1210 (which may be optional), the UE executes a client application that provides user data in response to the received input data provided by the host computer. When providing user data, the executed client application may also consider user input received from the user. Regardless of the specific manner of providing user data, the UE initiates transmission of user data to the host computer in sub-step 1230 (which may be optional). In step 1240 of the method, in accordance with the teachings of the embodiments described throughout the present disclosure, the host computer receives user data sent from the UE.

[0109] Fig.13 is a flow chart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Figure 8 and Fig. 9 For the simplicity of this disclosure, only Fig.13 In step 1310 (which may be optional), the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout the present disclosure. In step 1320 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 1330 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0110] In general, various exemplary embodiments may be implemented in hardware or dedicated chips, circuits, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, but the disclosure is not limited thereto. Although various aspects of the exemplary embodiments of the present disclosure may be illustrated and described as block diagrams, flow charts, or using some other illustrations, it is well understood that, as non-limiting examples, these block diagrams, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof.

[0111] Therefore, it should be understood that at least some aspects of the exemplary embodiments of the present disclosure can be practiced in various components such as integrated circuit chips and modules. It should be understood that the exemplary embodiments of the present disclosure can be implemented in a device embodied as an integrated circuit, wherein the integrated circuit may include circuits (and possible firmware) for embodying at least one or more of a data processor, a digital signal processor, a baseband circuit, and a radio frequency circuit, which can be configured to operate according to the exemplary embodiments of the present disclosure.

[0112] It should be understood that at least some aspects of the exemplary embodiments of the present disclosure may be embodied in computer executable instructions executed by one or more computers or other devices, such as embodied in one or more program modules. Typically, a program module includes routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types when executed by a processor in a computer or other device. Computer executable instructions may be stored on computer readable media such as hard disks, optical disks, removable storage media, solid-state memory, random access memory (RAM). Those skilled in the art will appreciate that the functions of the program modules may be combined or distributed as desired in various embodiments. In addition, the functions may be embodied in whole or in part in firmware or hardware equivalents, such as integrated circuits, field programmable gate arrays (FPGAs), etc.

[0113] The present disclosure includes any novel feature or feature combination disclosed herein, either explicitly or in any generalization thereof. When read in conjunction with the accompanying drawings, various modifications and adaptations to the aforementioned exemplary embodiments of the present disclosure will become apparent to those skilled in the relevant art in view of the foregoing description. However, any and all modifications will still fall within the scope of the non-limiting and exemplary embodiments of the present disclosure.

Claims

1. A method (300) performed by a terminal device, comprising: Determining (302) a preamble for a two-step random access procedure; Determining (304) an RNTI for the two-step random access procedure according to the radio network temporary identifier RNTI information; Based on the determined RNTI, generating (306) a scrambling sequence for a physical uplink shared channel, PUSCH, message; In the two-step random access procedure, sending (308) a request message including the preamble and the PUSCH message to a network node; as well as In response to sending the request message, receiving (310) a response message from the network node, the response message including an RNTI selected by the network node upon successful detection of the preamble in the request message and failure to decode the PUSCH message, wherein the selected RNTI is used to generate a scrambling sequence for the PUSCH in a subsequent two-step random access procedure.

2. The method (300) according to claim 1, wherein: The preamble is determined from a preamble set, and the RNTI information indicates an association between the preamble set and the RNTI set.

3. The method (300) of claim 2, wherein: The association is any one of: a one-to-one mapping between a preamble in the preamble set and an RNTI in the RNTI set, a one-to-many mapping between a preamble in the preamble set and two or more RNTIs in the RNTI set, or a many-to-one mapping between two or more preambles in the preamble set and the RNTIs in the RNTI set.

4. The method (300) according to claim 2 or 3, wherein: The RNTI is determined based on the determined preamble.

5. The method (300) of claim 1, wherein: The RNTI information indicates an association between a physical random access channel PRACH opportunity set and an RNTI set.

6. The method (300) of claim 5, wherein: The association is any one of the following: a one-to-one mapping between the PRACH opportunities in the PRACH opportunity set and the RNTI in the RNTI set, a one-to-many mapping between the PRACH opportunities in the PRACH opportunity set and two or more RNTIs in the RNTI set, or a many-to-one mapping between two or more PRACH opportunities in the PRACH opportunity set and the RNTI in the RNTI set.

7. The method (300) according to claim 5 or 6, wherein: The RNTI is determined based on a PRACH opportunity for the determined preamble.

8. The method (300) of claim 1, wherein: The RNTI information indicates at least one RNTI.

9. The method (300) of claim 8, wherein: The RNTI information indicates a plurality of RNTIs, and The RNTI is randomly determined from the multiple RNTIs.

10. The method (300) of claim 1, wherein: The preamble is associated with the PUSCH time-frequency resources.

11. The method (300) of claim 1, wherein: The RNTI information is predefined or signaled in a signaling message.

12. The method (300) of claim 1, wherein: The preamble is determined according to preamble information, and the preamble information is predefined or signaled in a signaling message.

13. The method (300) according to claim 11 or 12, wherein: The signaling message is a Radio Resource Control (RRC) message.

14. The method (300) of claim 1, wherein: The response message is received on a physical downlink shared channel PDSCH or a physical downlink control channel PDCCH.

15. A method (400) performed by a network node, comprising: In a two-step random access procedure, receiving (402) a request message including a preamble and a physical uplink shared channel (PUSCH) message from a terminal device, wherein a scrambling sequence used for the PUSCH message is based on an RNTI determined according to radio network temporary identifier (RNTI) information; In response to successfully detecting the preamble in the request message and failing to decode the PUSCH message, generating (404) a random access RA-RNTI based on the detected preamble; as well as A response message is sent (406) based on the RA-RNTI, the response message comprising a RNTI selected by the network node, wherein the selected RNTI is to be used by the terminal device to generate a scrambling sequence for a PUSCH message in a subsequent two-step random access procedure.

16. The method (400) of claim 15, wherein: The preamble is determined from a preamble set, and the RNTI information indicates an association between the preamble set and the RNTI set.

17. The method (400) of claim 16, wherein: The association is any one of: a one-to-one mapping between a preamble in the preamble set and an RNTI in the RNTI set, a one-to-many mapping between a preamble in the preamble set and two or more RNTIs in the RNTI set, or a many-to-one mapping between two or more preambles in the preamble set and the RNTIs in the RNTI set.

18. The method (400) according to claim 16 or 17, wherein: Receiving the request message includes: detecting the preamble in the request message; According to the RNTI information, determining the RNTI based on the detected preamble; and Based on the determined RNTI, the PUSCH message is decoded.

19. The method (400) of claim 15, wherein: The RNTI information indicates an association between a physical random access channel PRACH opportunity set and an RNTI set.

20. The method (400) of claim 19, wherein: The association is any one of the following: a one-to-one mapping between the PRACH opportunities in the PRACH opportunity set and the RNTI in the RNTI set, a one-to-many mapping between the PRACH opportunities in the PRACH opportunity set and two or more RNTIs in the RNTI set, or a many-to-one mapping between two or more PRACH opportunities in the PRACH opportunity set and the RNTI in the RNTI set.

21. The method (400) according to claim 19 or 20, wherein: Receiving the request message includes: detecting the preamble in the request message; determining the RNTI based on a PRACH opportunity for the detected preamble according to the RNTI information; and Based on the determined RNTI, the PUSCH message is decoded.

22. The method (400) of claim 15, wherein: The RNTI information indicates at least one RNTI.

23. The method (400) of claim 22, wherein: The RNTI information indicates a plurality of RNTIs, and Wherein, receiving the request message includes: detecting the preamble in the request message; and Based on the multiple RNTIs, the PUSCH message is blindly decoded.

24. The method (400) of claim 15, wherein: The preamble is associated with the PUSCH time-frequency resources.

25. The method (400) of claim 15, wherein: The RNTI information is predefined or signaled in a signaling message.

26. The method (400) of claim 15, wherein: The preamble is determined according to preamble information, and the preamble information is predefined or signaled in a signaling message.

27. The method (400) according to claim 25 or 26, wherein: The signaling message is a Radio Resource Control (RRC) message.

28. The method (400) of claim 15, wherein: The response message is sent on a physical downlink shared channel PDSCH or a physical downlink control channel PDCCH.

29. A terminal device (500), comprising: one or more processors (501); as well as one or more memories (502) including computer program code (503), The one or more memories (502) and the computer program code (503) are configured to, together with the one or more processors (501), cause the terminal device (500) to: determining a preamble for a two-step random access procedure; Determining, according to the radio network temporary identifier RNTI information, an RNTI for the two-step random access procedure; Based on the determined RNTI, generating a scrambling sequence for a physical uplink shared channel (PUSCH) message; In the two-step random access procedure, sending a request message including the preamble and the PUSCH message to a network node; and In response to sending the request message, receiving (310) a response message from the network node, the response message including an RNTI selected by the network node upon successful detection of the preamble in the request message and failure to decode the PUSCH message, wherein the selected RNTI is used to generate a scrambling sequence for the PUSCH in a subsequent two-step random access procedure.

30. The terminal device (500) according to claim 29, wherein: The one or more memories (502) and the computer program code (503) are also configured to, together with the one or more processors (501), cause the terminal device (500) to execute the method according to any one of claims 2-14.

31. A base station (500), comprising: one or more processors (501); as well as one or more memories (502) including computer program code (503), The one or more memories (502) and the computer program code (503) are configured to, together with the one or more processors, cause the base station (500) to: In a two-step random access procedure, receiving a request message including a preamble and a physical uplink shared channel (PUSCH) message from a terminal device, wherein a scrambling sequence used for the PUSCH message is based on an RNTI determined according to radio network temporary identifier (RNTI) information; In response to successfully detecting the preamble in the request message and failing to decode the PUSCH message, generating (404) a random access RA-RNTI based on the detected preamble; as well as A response message is sent (406) based on the RA-RNTI, the response message comprising a RNTI selected by the base station, wherein the selected RNTI is to be used by the terminal device to generate a scrambling sequence for a PUSCH message in a subsequent two-step random access procedure.

32. The base station (500) of claim 31, wherein: The one or more memories (502) and the computer program code (503) are further configured to, together with the one or more processors (501), cause the base station (500) to perform a method according to any one of claims 16-28.

33. A computer readable medium having computer program code embodied thereon, which when executed on a computer causes the computer to perform the method according to any one of claims 1-14.

34. A computer readable medium having computer program code embodied thereon, which when executed on a computer causes the computer to perform the method according to any one of claims 15-28.

Images