Indication of device type

Abstract

According to some example embodiments of the present disclosure, a solution for indicating a device type is provided. In the solution, a terminal device determines information associated with a message for random access. The information may include a transmission configuration associated with the message and / or an LCID to be included in the message. The transmission configuration corresponds to the type of the terminal device. The LCID has a value that is different from another value associated with another terminal device type. The terminal device then sends a message to the network device based on the information. And the network device determines the type of the terminal device based on the transmission configuration and / or the LCID in the message.

Description

Technical Field

[0001] Various exemplary embodiments of this disclosure generally relate to the telecommunications field, and more specifically, to methods, apparatus, and computer-readable storage media for indicating device type. Background Technology

[0002] In the fifth-generation mobile communication technology (5G) New Radio (NR), two contention-based random access (CBRA) procedures are supported: a 4-step random access procedure (RACH) and a 2-step random access procedure. Summary of the Invention

[0003] In a first aspect of this disclosure, an apparatus is provided. The apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: determine information associated with a message for random access, wherein the information includes at least one of: a transport configuration associated with the message and corresponding to a type of apparatus, or a logical channel identifier to be included in the message, the logical channel identifier having a first value different from a second value associated with another terminal device type, wherein the first value indicates the type of apparatus; and send the message to a network device based on the information.

[0004] In a second aspect of this disclosure, an apparatus is provided. The apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: receive a message for random access from a terminal device; and determine the type of the terminal device based on information associated with the message, wherein the information includes at least one of: a transmission configuration associated with the message and corresponding to the type of the terminal device, or a logical channel identifier included in the message, the logical channel identifier having a first value that differs from a second value associated with another terminal device type, wherein the first value indicates the type of the terminal device.

[0005] In a third aspect of this disclosure, a method is provided. The method includes: determining at a terminal device information associated with a message for random access, wherein the information includes at least one of: a transport configuration associated with the message and corresponding to a type of terminal device, or a logical channel identifier to be included in the message, the logical channel identifier having a first value different from a second value associated with another terminal device type, wherein the first value indicates the type of terminal device; and sending the message to a network device based on the information.

[0006] In a fourth aspect of this disclosure, a method is provided. The method includes: receiving a message for random access from a terminal device at a network device; and determining a type of terminal device based on information associated with the message, wherein the information includes at least one of: a transport configuration associated with the message and corresponding to the type of terminal device, or a logical channel identifier included in the message, the logical channel identifier having a first value different from a second value associated with another terminal device type, wherein the first value indicates the type of terminal device.

[0007] In a fifth aspect of this disclosure, an apparatus is provided. The apparatus includes: components for determining information associated with a message for random access, wherein the information includes at least one of: a transmission configuration associated with the message and corresponding to a type of device, or a logical channel identifier to be included in the message, the logical channel identifier having a first value different from a second value associated with another terminal device type, wherein the first value indicates the type of device; and components for sending the message to a network device based on the information.

[0008] In a sixth aspect of this disclosure, an apparatus is provided. The apparatus includes components for receiving a message for random access from a terminal device; and components for determining the type of the terminal device based on information associated with the message, wherein the information includes at least one of: a transmission configuration associated with the message and corresponding to the type of the terminal device, or a logical channel identifier included in the message, the logical channel identifier having a first value different from a second value associated with another terminal device type, wherein the first value indicates the type of the terminal device.

[0009] 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 at least execute the method according to a third aspect.

[0010] 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 at least execute the method according to the fourth aspect.

[0011] 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

[0012] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which: Figure 1 An example communication environment in which example embodiments of this disclosure may be implemented is shown; Figure 2Signaling diagrams for indicating device type are shown according to some example embodiments of this disclosure; Figure 3 Example parameters for the demodulation reference signal (DMRS) are shown according to some example embodiments of the present disclosure; Figure 4A and Figure 4B Example message structures for different device types are shown according to some example embodiments of this disclosure; Figure 5A and Figure 5B Example message structures for different device types are shown according to some example embodiments of this disclosure; Figure 6 Signaling diagrams for indicating device type are shown according to some example embodiments of this disclosure; Figure 7 A flowchart is shown illustrating a method implemented at a terminal device according to some example embodiments of the present disclosure; Figure 8 A flowchart is shown illustrating a method implemented at a network device according to some example embodiments of the present disclosure; Figure 9 A simplified block diagram of a device suitable for implementing example embodiments of the present disclosure is shown; and Figure 10 A block diagram of an example computer-readable medium according to some example embodiments of the present disclosure is shown.

[0013] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

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

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

[0016] 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. Additionally, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is believed that its influence on such feature, structure, or characteristic in conjunction with other embodiments is within the knowledge of those skilled in the art, whether explicitly described or not.

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

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

[0019] As used herein, unless explicitly stated otherwise, the “responding to A” execution step does not indicate that the step is executed immediately after “A” occurs, and may include one or more intermediate steps.

[0020] 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 be further understood that the terms “comprising,” “including,” “having,” “having,” “including,” and / or “containing” as used herein specify the presence of the 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.

[0021] As used in this application, the term "circuit system" may refer to one or more or all of the following: (a) Hardware circuit implementation only (such as implementation only in analog and / or digital circuit systems), and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of analog and / or digital hardware circuitry with software / firmware, and (ii) Any part of a hardware processor with software (including digital signal processors, software, and memory, which work together to enable devices such as mobile phones or servers to perform various functions), and (c) Hardware circuitry and / or processors, such as one or more microprocessors or a portion thereof, that require software (e.g., firmware) for operation, but which may be absent when operation is not required.

[0022] This definition of circuit applies to all uses of the term in this application (including any claim). As another example, as used in this application, the term circuit system also covers only hardware circuitry or a processor (or processors) or a portion of hardware circuitry or a processor and its accompanying software and / or firmware implementation. The term circuit system also covers, for example and if applicable to elements of a particular claim, 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.

[0023] 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 of 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) 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 of communications, there will certainly be future types of communication technologies and systems that embody the future types of this disclosure. This disclosure should not be construed as limiting its scope to the aforementioned systems.

[0024] 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. Network devices can refer to base stations (BS) or access points (APs), such as Node B (NodeB or NB), evolved Node B (eNode B or eNB), NR NB (also known as gNB), Remote Radio Unit (RRU), Radio Head (RH), Remote Radio Head (RRH), relay, Integrated Access and Backhaul (IAB) node, low-power node (such as femtosecond), picosecond, 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), spacecraft network equipment, etc., depending on the terminology and technology applied. 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 toward its parent node, and the DU portion of the IAB node behaves similarly to a base station toward the next-hop IAB node.

[0025] The term "terminal device" refers to any terminal device capable of wireless communication. By way of example and not 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 can include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, 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 return devices, 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 electronic 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.

[0026] 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 time-domain resources, frequency-domain resources, spatial-domain resources, code-domain resources, or any other resource capable of communication. In the following, unless explicitly stated otherwise, resources in 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.

[0027] In embodiments of this disclosure, the type of terminal device can be determined based on or corresponding to appropriate capabilities, features, characteristics, or release versions of the terminal device. Different types of terminal devices may include, but are not limited to, devices that follow different versions of standards or specifications and / or devices with different capabilities. As used herein, the terms “type,” “device type,” “device type,” “terminal device type,” “UE type,” “UE type,” “category,” and “UE category” are used interchangeably. In an example, a device type may be Rel-18 Reduced Capability (RedCap), meaning that a RedCap device complies with the 3GPP Rel-18 specification; and another device type may be Rel-17 RedCap, meaning that a RedCap device supports the 3GPP Rel-17 specification. In another example, a device type may be a RedCap device with reduced baseband bandwidth, and another device type may be a RedCap device with reduced peak rates. Below, some example embodiments are described with respect to Rel-17 RedCap and Rel-18 RedCap. However, this is for illustrative purposes only and is not intended to be limiting.

[0028] Figure 1 An example communication environment 100 in which exemplary embodiments of the present disclosure may be implemented is shown. The communication environment 100 may include a terminal device 110. Hereinafter, the terminal device 110 may also be referred to as a UE.

[0029] The communication environment 100 may also include a network device 120. Hereinafter, the network device 120 may also be referred to as a gNB or eNB. The network device 120 can communicate with the terminal device 110.

[0030] It should be understood that Figure 1 The number of network devices and terminal devices shown is given for illustrative purposes and does not imply any limitation. The communication environment 100 may include any suitable number of network devices and terminal devices.

[0031] In some example embodiments, the link from network device 120 to terminal device 110 may be referred to as a downlink (DL), while the link from terminal device 110 to network device 120 may be referred to as an uplink (UL). In the DL, network device 120 is a transmitting (TX) device (or transmitter), and terminal device 110 is a receiving (RX) device (or receiver). In the UL, terminal device 110 is a TX device (or transmitter), and network device 120 is an RX device (or receiver).

[0032] Communication in communication environment 100 can be implemented according to any suitable communication protocol, 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), 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.

[0033] In 5G NR, two CBRA procedures are supported: a 4-step random access procedure (i.e., RACH) and a 2-step random access procedure.

[0034] In the 4-step RACH, the UE can use a specific resource called the RACH timing (RO) to send a specific preamble in message 1 (Msg1) to the gNB via the Physical Random Access Channel (PRACH). The gNB can respond to the UE using a Random Access Response (RAR) message (also referred to as message 2 (Msg2)). Msg2 may include the detected preamble ID, timing advance command, Temporary Cell Radio Network Temporary Identifier (TC-RNTI), and UL grant for transmission on the Physical Uplink Shared Channel (PUSCH) for Msg3. The UE can then respond to Msg2 on the scheduled PUSCH using the contention resolution ID for the Radio Resource Control (RRC) request, which can also be referred to as Msg3. The gNB can send a contention resolution message with the contention resolution ID established for the RRC, which can also be referred to as message 4 (Msg4).

[0035] Upon receiving Msg4, if its contention resolution ID is carried by Msg4, the UE can send an ACK on the Physical Uplink Control Channel (PUCCH). This completes the 4-step RACH. Furthermore, prior to Msg1, there are preliminary steps involving the transmission (at the gNB) and reception (at the UE) of the Synchronization Signal Block (SSB), including DL beam scanning, which is not a formal part of the RACH process. As a result of this preliminary step, the UE can select the index of the preferred SSB beam and decode the associated Physical Broadcast Channel (PBCH) for the Master Information Block (MIB), subsequently receiving and decoding the System Information Block (SIB), etc. This index is also used by the UE to identify the appropriate RACH timing (RO) for preamble transmission (i.e., Msg1) based on the SSB-to-RO mapping conveyed by SIB1. The gNB can use the SSB beam index selected by the UE for Msg2 transmission.

[0036] In the two-step random access process, Msg1 and Msg3 are combined in the MSGA and sent out without waiting for feedback from the gNB between them (traditionally Msg2). Similarly, the gNB can combine Msg2 and Msg4 into message B (MSGB).

[0037] During a 4-step RACH or 2-step RACH random access procedure, multiple UEs using the same preamble ID for Msg1 may use the same resources to transmit Msg3, which could lead to decoding failure of Msg3 at the gNB due to interference. Furthermore, even if the gNB successfully decodes one Msg3 and responds with Msg4 including the contention resolution ID contained in Msg3, other UEs may still need to retransmit Msg1, even if their Msg3 has not yet been decoded by the gNB and the contention resolution was detected by Msg4.

[0038] In Rel-17, RedCap devices (also known as Rel-17 RedCap devices or Rel-17 RedCap UEs) are specified to have the following capabilities, as shown in Table 1.

[0039] Table 1. Equipment that reduces capacity

[0040] In Rel-18, another lower-capability device (also referred to as a Rel-18 RedCap device, Rel-18 RedCap UE, or eRedCap device) is introduced as a lower-layer device between large-scale IoT and Rel-17 RedCap devices. Rel-18 RedCap devices can have reduced baseband bandwidth and / or reduced peak data rates. Rel-18 RedCap devices with reduced baseband bandwidth are able to process or transmit only a subset of PRBs used for unicast transmissions (e.g., 25 PRBs for 15 kHz subcarrier spacing and 12 PRBs for 30 kHz subcarrier spacing). The peak data rate supported for the new Rel-18 devices is approximately 10 Mbps. In the solution, Rel-17 RedCap devices can be identified in Msg1 or Msg3 (i.e., early identification or early indication) so that gNBs can handle them appropriately. It is expected that Rel-18 RedCap devices will also support separate early identification in Msg1 or Msg3.

[0041] In the solution, the UE type can be identified in Msg1 based on preambles for different UE types, such as Small Data Transmission (SDT), RedCap, Ultra-Reliable Low-Latency Communication (URLLC), RACH Group A, and Group B. However, considering the increase in the number of RACH preamble space partitions, the number of Msg1 collisions may increase with inappropriate partition sizes. When there are Msg1 collisions from multiple UEs selecting the same PRACH preamble, the corresponding UEs also transmit Msg3 from the same resources provided by RAR, leading to Msg3 contention. Therefore, an increase in the number of RACH preamble space partitions may increase the probability of Msg1 collisions and Msg3 contention.

[0042] If a separate Logical Channel Identifier (LCID) is specified for the early indication of Msg3 / MsgA for Rel-18 RedCap devices, similar to Rel-17, they will consume two additional LCIDs from the very scarce resources of the remaining short LCIDs in UL-SCH (only 6 reserved values ​​after Rel-17).

[0043] Therefore, a new solution is needed to address the early identification of Rel-18 Redcap devices, or a way to support other new features that require early identification of UE types.

[0044] According to some example embodiments of this disclosure, a solution for indicating device type is provided. In this solution, a terminal device determines information associated with a message used for random access. For example, the message may be Msg3 or MSGA. This information may include transport configuration associated with the message and / or LCID to be included in the message. The transport configuration corresponds to the type of the terminal device. The LCID has a value that is different from another value associated with another terminal device type. The terminal device then sends a message to a network device based on the information. The network device receives the message. Based on the transport configuration and / or LCID in the message, the network device determines the type of the terminal device. In this way, the network device can identify or know the type of the terminal device in advance. By identifying the device type early, the network device can handle conflicts early.

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

[0046] Now for reference Figure 2 ,Should Figure 2 Signaling diagram 200 for communication is shown according to some example embodiments of the present disclosure. For example... Figure 2 As shown, signaling diagram 200 involves terminal device 110 and network device 120. For discussion purposes, refer to... Figure 1 To describe signaling diagram 200.

[0047] Terminal device 110 determines (210) the information associated with the message used for random access. In some example embodiments, this message may be Msg3 in a 4-step RACH. This may mean Figure 2 The process shown occurs during a 4-step RACH. In some example embodiments, the message may be an MSGA in a 2-step RACH. This could mean Figure 2 The process shown occurs during the 2-step RACH.

[0048] The determined information may include the transport configuration associated with the message, and the transport configuration corresponds to the type of terminal device 110. Alternatively or additionally, the determined information may include an LCID to be included in the message. The LCID has a value that is different from a second value associated with another terminal device type. The first value may indicate the type of terminal device 110. In other words, such information can be used to indicate the type of terminal device 110 to network device 120.

[0049] In some example embodiments, the transport configuration can be defined as a default configuration corresponding to the terminal device type. In other words, the transport configuration can be defined in the technical specifications. For example, different types of terminal devices can use corresponding transport configurations to send Msg3 and / or MSGA.

[0050] Alternatively, in some example embodiments, the transmission configuration can be configured by network device 120. For example... Figure 2 As shown, network device 120 can send (205) transport configurations in a System Information Block (SIB) to terminal device 110. For example, the SIB may include transport configurations corresponding to different device types. Based on the SIB, terminal device 110 can determine which transport configuration to use for Msg3 and / or MSGA.

[0051] Terminal device 110 sends message (215) to network device 120 based on the determined information. For example, in a 4-step RACH, after receiving the UL authorization in the RAR, Msg3 is sent. As another example, in a 2-step RACH, MSGA is sent.

[0052] Network device 120 receives a message from terminal device 110. Based on information associated with the received message, network device 120 determines the type of terminal device 110. For example, network device 120 may identify the type of terminal device based on the transport configuration associated with the message. Alternatively, network device 120 may identify the type of terminal device 110 at least based on the value of the LCID included in the message.

[0053] The general process has been described above. To better understand this solution, some more example embodiments regarding transport configuration and LCID are now described.

[0054] In some example embodiments, the transport configuration may include a reference signal (RS) configuration for sending the DMRS associated with the message. Accordingly, terminal device 110 may use the RS configuration to send the DMRS to network device 120. That is, the RS configuration can be used to distinguish device types.

[0055] As an example, when a transmitted PUSCH is neither scheduled by a downlink control information (DCI) format 0_1 / 0_2 with scrambled cyclic redundancy check (CRC) scrambled by cell-RNTI (C-RNTI), configured scheduling (CS)-RNTI, semi-persistent channel state information (SP-CSI)-RNTI, or modulation and coding scheme-cell (MCS-C)-RNTI, nor corresponds to a configured grant, nor is it used as a PUSCH for a type 2 random access procedure, the UE should use a single-symbol preload DMRS configured for type 1 on DMRS port 0, and the remaining REs in the symbol not used for DMRS are not used for any PUSCH transmission, except for PUSCHs with an allocation duration of 2 or fewer OFDM symbols with transform precoding disabled. Additional DMRS can be transmitted depending on the scheduling type and PUSCH duration.

[0056] In light of the foregoing, in some example embodiments, the RS configuration may include an antenna port for the DMRS associated with the message. The antenna port for the DMRS is also called the DMRS antenna port. That is, different device types may correspond to different DMRS antenna ports. Different types of terminal devices use corresponding DMRS antenna ports for Msg3 or MSGA. Based on the DMRS antenna port of the received Msg3 or MSGA, network device 110 can identify the type of the sending terminal device.

[0057] The configuration of the DMRS antenna ports can be predefined in the technical specifications or broadcast by network device 120 in the System Information Block (SIB). Take, for example, the early identification of a Rel-18 RedCap UE in the MSGA PUSCH during a two-step RACH process. In this example, the early identification based on PRACH for both Rel-17 and Rel-18 RedCap UEs is configured, and different groups of DMRS antenna ports can be configured for, for example, Rel-17 RedCap UEs (e.g., using existing MSGA DMRS configurations) and Rel-18 RedCap UEs (using new MSGA DMRS configurations). In this way, currently supported DMRS antenna ports (with PUSCH DMRS configuration type 1) can be shared between the two UE types.

[0058] Figure 3 Example parameters for DMRS are shown according to some example embodiments of this disclosure. The parameters are... This indicates the DMRS antenna port, and parameter λ represents the Code Division Multiplexing (CDM) group. ,parameter and Used for precoding and mapping to physical resources. For example, such as Figure 3 As shown, port {0} can be configured for Rel-17 RedCap UE (with existing MSGA DMRS configuration), and ports {1,2,3...} in box 310 can be configured for eRedCap UE (with new MSGA DMRS configuration).

[0059] Figure 4A , Figure 4B , Figure 5A , Figure 5B Example message structures for different device capabilities are shown. Specifically, Figure 4A and Figure 4B The symbol Msg3 of type B 14 is shown, and Figure 5A and Figure 5BThe symbol Msg3 of type A 14 is shown. For example, the Rel-17 RedCap UE can use DMRS antenna port 0, and the structure of Msg3 is as follows. Figure 4A or Figure 5A As shown. The Rel-18 RedCapUE can use DMRS antenna port 2, and the structure of Msg3 is shown as follows. Figure 4B or Figure 5B Therefore, based on the decoding of the DMRS associated with Msg3, network device 120 can distinguish between Rel-17 RedCap UE and Rel-18 RedCap UE.

[0060] In some example implementations, Msg3 / MSGA DMRS port configurations can be broadcast in SIB1. New parameters can be included in SIB1 to indicate rules for binding with UE type or UE characteristics. For example, based on parameters defined in SIB1, port {0} is configured for Rel-17 RedCap UEs (with existing MSGA DMRS configurations), and ports {1,2,3...} are configured for eRedCap UEs (with new MSGA DMRS configurations). For example, parameter “MsgA-PUSCH-Config->msgA-DMRS-Config-r16” is configured for RedCap UEs, and parameter “MsgA-PUSCH-Config->msgA-DMRS-Config-r18” is configured for eRedCap UEs. This separation can be defined by specifying which DMRS CDM groups the eRedCap UE can use. For example, the DMRS CDM groups used by the eRedCap UE can be orthogonal to the DMRS CDM groups specified in existing rules for legacy UEs.

[0061] Alternatively, in some example embodiments, the Msg3 / MSGA DMRS port configuration can be predefined in the technical specification. The UE type or UE characteristic bound to the DMRS antenna port can be defined. For example, the technical specification can define that an eRedCap UE uses DMRS antenna port 2 for Msg3 and / or MSGA, and an eRedCap UE with the SDT characteristic uses DMRS antenna port 3 for Msg3 and / or MSGA. Note that this binding between UE type and DMRS antenna port is exemplary and not limiting.

[0062] In such an example embodiment, an Msg1 collision occurs if different antenna ports associated with different UE types are detected in the same Msg3 resource. Network device 120 can identify the collision and further optimize retransmission. In some example embodiments, the DMRS antenna port can be combined with the partitioning of the PRACH preamble for finer-grained identification and resource saving.

[0063] In the example embodiment described above, the DMRS antenna port is used to distinguish between Rel-17 RedCap UEs and Rel-18 RedCap UEs. Additional or alternative methods of differentiation are possible. These alternatives may rely on different physical layer characteristics to distinguish terminal device types.

[0064] Alternatively or additionally, in some example embodiments, the RS configuration may include a first sequence for generating the DMRS, also referred to as the DMRS sequence. For example, a Rel-17 RedCap UE may use a certain sequence to generate the DMRS associated with Msg3 and / or MSGA, while a Rel-18 RedCap UE may use a different sequence to generate the DMRS. In this way, network device 120 may distinguish between a Rel-17 RedCap UE and a Rel-18 RedCap UE based on the DMRS sequence. In such example embodiments, network device 120 may identify the device type of the transmitting terminal device based on the DMRS sequence of the received DMRS associated with Msg3 and / or MSGA.

[0065] Alternatively or additionally, in some example embodiments, the RS configuration may include a first sequence start point for generating the DMRS. The sequence start point is also known as sequence initialization (C). init Different types of terminal devices can use the same DMRS sequence, but initialize with different sequences. In such an example embodiment, network device 120 can identify the device type of the sending terminal device based on the initialization of the DMRS sequence.

[0066] Alternatively or additionally, in some example embodiments, the transport configuration may include a scrambling configuration for messages. Therefore, messages (e.g., Msg3 and / or MSGA) are scrambled based on the scrambling configuration. The network device 120 can then identify the device type of the sending terminal device based on which descrambling configuration is used to descramble Msg3 and / or MSGA.

[0067] In some example embodiments, the scrambling configuration may include a second sequence for scrambling messages, also referred to as a scrambling sequence. Different types of terminal devices may use different scrambling sequences to scramble Msg3 and / or MSGA. In the example, a Rel-17 RedCap UE may use a RA-RNTI-based scrambling sequence, while a Rel-18 RedCap UE may use a different sequence. In such example embodiments, network device 120 may identify the device type of the sending terminal device based on which descrambling sequence is used to descramble Msg3 and / or MSGA.

[0068] In some example embodiments, the RS configuration may include a second sequence start point for scrambling messages. The sequence start point is also known as sequence initialization (C). init Different types of terminal devices can use the same scrambling sequence, but can be initialized with different sequences using the same scrambling sequence. In such an example embodiment, network device 120 can identify the device type of the transmitting terminal device based on the initialization of the descrambling sequence used to descramble Msg3 and / or MSGA.

[0069] Typically, the distinction described above can benefit from using the Msg1 early indication to inform network devices that this is RedCapUE (even if it is unknown whether it is Rel-17 or Rel-18). This will prevent network devices from having to perform both types of physical layer processing on all Msg3 transmissions.

[0070] In the above example embodiment, the transmission configuration is used to indicate the device type of the terminal device 110.

[0071] Alternatively or additionally, in some example embodiments, the preamble may be used in combination with the LCID value in the message to indicate the device type. Specifically, terminal device 110 may send a preamble for random access to network device 120. The preamble corresponds to multiple terminal device types, including the device type of terminal device 110 and another terminal device type. For example, in a 4-step RACH, the preamble is sent in Msg1. As another example, in a 2-step RACH, the preamble is sent in MSGA. Then, in the message sent to network device 120, the LCID value (also referred to as the first value) differs from another value (also referred to as the second value) associated with another device type.

[0072] As an example, in a 4-step RACH, the gNB can use the Msg1 early indication and the Msg3 LCID to determine whether the UE is a Rel-18 RedCap UE. The Msg1 early indication, which identifies the device type, can be based on preambles assigned to different device types, such as SDT, REDCAP, URLLC, RACH Group A, and Group B. Specifically, a RedCap UE can select the preamble to be transmitted in Msg1 from a subset of preambles. Therefore, if the gNB receives a preamble from the subset assigned to RedCap UEs, the gNB can determine that the transmitting UE is a RedCap UE, but the gNB does not know whether the transmitting UE is Rel-18 or Rel-17.

[0073] In this scenario, the LCID of a Rel-18 UE can be set by the gNB to a reserved value or another value not used by Rel-17 RedCap UEs. Since Msg1 indicates that this is a RedCap UE, this can be used to determine that the UE is a Rel-18 UE without having to permanently reserve the LCID for a Rel-18 RedCap UE. As an example, and not as a limitation, Table 2 shows the values ​​of the LCID for the UL Shared Channel (SCH). As can be seen from Table 2, code points / indices “35” and “36” are used for Rel-17 RedCap UEs. Then, for a Rel-18 RedCap UE, the LCID values ​​in Msg3 and / or MSGA can be set to any value other than “35” and “36”. Since the message in the UL-SCH is received in the resources that schedule Msg3, the gNB can determine that it is from a RedCap UE that is not a Rel-17 (i.e., a Rel-18 RedCap UE) in Msg3. As an example, code point / index “0” and “52” (i.e., the values ​​associated with CCCH messages for non-RedCap UEs) are reused for Rel-18 RedCap UEs.

[0074] Table 2 LCID values ​​for UL-SCH

[0075] Such example implementations do not require changes to the physical layer processing, but instead rely on higher-level (e.g., MAC) processing (i.e., viewing message content). The method is less complex at the network level.

[0076] The RA process with device type indication will now be illustrated using a 4-step RACH as an example. However, it should be noted that this concept can be applied to a 2-step RACH.

[0077] Figure 6 A signaling diagram 600 is shown to indicate the device type. (See diagram 600.) Figure 6 As shown, signaling diagram 600 involves terminal device 110 and network device 120. For discussion purposes, refer to... Figure 1 Let's describe signaling diagram 600. Diagram 600 can be considered an embedding of diagram 200.

[0078] Terminal device 110 may send a specific preamble in (615) Msg1 to network device 120. In some example embodiments, the preamble may be selected from a subset of preambles corresponding to some device type (e.g., RedCap UE).

[0079] Network device 120 may send (620) Msg2 to terminal device 110. Msg2 may include the detected preamble ID, time advance command, TC-RNTI, and UL authorization for transmitting Msg3 on PUSCH.

[0080] Terminal device 110 determines (625) information associated with Msg3. In some example embodiments, this information may include a transmission configuration associated with Msg3 and corresponding to the type of terminal device 110. The transmission configuration is similar to that described above, and therefore will not be repeated.

[0081] Terminal device 110 sends (630) Msg3 to network device 120 based on the determined information. Upon receiving Msg3, network device 120 determines (635) the device type of terminal device 110 based on the information associated with Msg3. For example, based on the fact that the preamble and LCID values ​​in Msg1 corresponding to a RedCap UE are different from "35" and "36" for a Rel-17 RedCap UE, network device 120 can determine that terminal device 120 is a Rel-18 RedCap UE. As another example, based on the use of DMRS antenna port 2, network device 120 can determine that terminal device 120 is a Rel-18 RedCap UE.

[0082] Then, network device 120 sends (640) Msg4 to terminal device 110. Network device 120 may schedule Msg4 based on the determined device type or characteristics.

[0083] The proposed solution is easily extended to identify UEs with new features. The proposed solution does not require further division of the Msg1 preamble number for UE identification and is compatible with traditional UEs.

[0084] Given an increased partitioning of the RACH preamble space, the number of collisions may increase. This solution can help reduce the RACH load in the network. Furthermore, the gNB UL PHY capacity to process the RACH preamble per RACH timing is limited, thus reducing the overall RACH load is beneficial.

[0085] Figure 7 A flowchart of an example method 700 implemented at a terminal device according to some example embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 1 Angle description method 700 for terminal device 110 in the middle.

[0086] At block 710, terminal device 110 determines information associated with a message for random access. This information includes at least one of the following: a transport configuration associated with the message and corresponding to the type of terminal device 110, or a logical channel identifier to be included in the message. The logical channel identifier has a first value that differs from a second value associated with another terminal device type. The first value may indicate the type of terminal device 110.

[0087] At frame 720, terminal device 110 sends a message to network device 120 based on information.

[0088] In some example embodiments, the transport configuration includes a reference signal configuration for transmitting a demodulation reference signal associated with the message. Terminal device 110 can use the reference signal configuration to transmit the demodulation reference signal to network device 120.

[0089] In some example embodiments, the reference signal configuration includes at least one of the following: an antenna port for the demodulated reference signal, a first sequence for generating the demodulated reference signal, or a first sequence start point for generating the demodulated reference signal.

[0090] In some example embodiments, the transport configuration includes a scrambling configuration for messages, and the transmitted messages are scrambled based on the scrambling configuration.

[0091] In some example embodiments, the scrambling configuration includes at least one of the following: a second sequence for scrambling messages, or a second sequence start point for scrambling messages.

[0092] In some example embodiments, in the sent message, the first value of the logical channel identifier differs from a second value associated with another type. Terminal device 110 may also send a preamble for random access to network device 120. The preamble corresponds to multiple terminal device types, including the type of terminal device 110 and another terminal device type.

[0093] In some example embodiments, the transmission configuration is defined as the default configuration corresponding to the type of terminal device 110.

[0094] In some example embodiments, terminal device 110 may receive transmission configuration from system information blocks from network device 120.

[0095] In some example implementations, the message includes at least one of the following: MSGA in a two-step random access procedure, or Msg3 in a four-step random access procedure.

[0096] Figure 8 A flowchart of an example method 800 implemented at a network device according to some example embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 1 The angular description method of network device 120 in 800.

[0097] In box 810, network device 120 receives messages for random access from terminal device 110.

[0098] At box 820, network device 120 determines the type of terminal device 110 based on information associated with a message. The information includes at least one of the following: a transport configuration associated with the message and corresponding to the type of terminal device 110, or a logical channel identifier included in the message, which has a first value that differs from a second value associated with another terminal device type. The first value may indicate the type of terminal device 120.

[0099] In some example embodiments, the transmission configuration includes a reference signal configuration for receiving a demodulation reference signal associated with a message.

[0100] In some example embodiments, the reference signal configuration includes at least one of the following: for the antenna port of the demodulated reference signal, for decoding a first sequence of the demodulated reference signal, or for decoding the first sequence start point of the demodulated reference signal.

[0101] In some example embodiments, the transport configuration includes a scrambling configuration for the message, and the message is descrambled based on the scrambling configuration.

[0102] In some example embodiments, the scrambling configuration includes at least one of the following: a second sequence for descrambling messages, or a second sequence start point for descrambling messages.

[0103] In some example embodiments, network device 120 may receive a preamble for random access from a terminal device; based on determining that the preamble corresponds to multiple terminal device types, network device 120 may determine whether a first value of a logical channel identifier is different from a second value associated with another terminal device type; and based on determining that the first value of the logical channel identifier is different from the second value associated with another type, network device 120 may determine the type of terminal device 110.

[0104] In some example embodiments, the transmission configuration is defined as the default configuration corresponding to the type of terminal device 110.

[0105] In some example embodiments, network device 120 may send the transmission configuration in the system information block to terminal device 110.

[0106] In some example implementations, the message includes at least one of the following: MSGA in a two-step random access procedure, or Msg3 in a four-step random access procedure.

[0107] In some example embodiments, the means capable of performing any of the methods in method 700 (e.g., Figure 1 The terminal device 110 may include components for performing the corresponding operations of method 700. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module. The device may be implemented as or included in... Figure 1 In terminal device 110.

[0108] In some example embodiments, the apparatus includes: a component for determining information associated with a message for random access, wherein the information includes at least one of the following: a transmission configuration associated with the message and corresponding to a type of terminal device, or a logical channel identifier to be included in the message, the logical channel identifier having a first value different from a second value associated with another type of terminal device, wherein the first value indicates the type of terminal device; and a component for sending the message to a network device based on the information.

[0109] In some example embodiments, the transport configuration includes a reference signal configuration for transmitting a demodulation reference signal associated with a message. The apparatus includes components for transmitting the demodulation reference signal to a network device using the reference signal configuration.

[0110] In some example embodiments, the reference signal configuration includes at least one of the following: for the antenna port of the demodulated reference signal, for generating a first sequence of the demodulated reference signal, or for generating a first sequence start point of the demodulated reference signal.

[0111] In some example embodiments, the transport configuration includes a scrambling configuration for messages, and the transmitted messages are scrambled based on the scrambling configuration.

[0112] In some example embodiments, the scrambling configuration includes at least one of the following: a second sequence for scrambling messages, or a second sequence start point for scrambling messages.

[0113] In some example embodiments, in the transmitted message, a first value of the logical channel identifier differs from a second value associated with another terminal device type. The apparatus includes components for transmitting a preamble for random access to a network device, wherein the preamble corresponds to multiple terminal device types, including a terminal device type and another terminal device type.

[0114] In some example embodiments, the transport configuration is defined as the default configuration corresponding to the terminal device type.

[0115] In some example embodiments, the apparatus includes components for receiving transmission configurations from a system information block of a network device.

[0116] In some example implementations, the message includes at least one of the following: MSGA in a two-step random access procedure, or Msg3 in a four-step random access procedure.

[0117] In some example embodiments, the apparatus further includes components for performing other operations in some example embodiments of method 700 or terminal device 110. In some example embodiments, the components include: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform.

[0118] In some example embodiments, the means capable of performing any of the methods in method 800 (e.g., Figure 1 The network device 120 in the method 800 may include components for performing corresponding operations of the method. These components may be implemented in any suitable form. For example, the device may be implemented in a circuit system or a software module. The device may be implemented as or included in... Figure 1 Among the network devices in 120.

[0119] In some example embodiments, the apparatus includes: components for receiving a message for random access from a terminal device; and components for determining the type of the terminal device based on information associated with the message, wherein the information includes at least one of the following: a transmission configuration associated with the message and corresponding to the type of the terminal device, or a logical channel identifier included in the message, the logical channel identifier having a first value that is different from a second value associated with another terminal device type, wherein the first value indicates the type of the terminal device.

[0120] In some example embodiments, the transmission configuration includes a reference signal configuration for receiving a demodulation reference signal associated with a message.

[0121] In some example embodiments, the reference signal configuration includes at least one of the following: for the antenna port of the demodulated reference signal, for decoding a first sequence of the demodulated reference signal, or for decoding the first sequence start point of the demodulated reference signal.

[0122] In some example embodiments, the transport configuration includes a scrambling configuration for the message, and the message is descrambled based on the scrambling configuration.

[0123] In some example embodiments, the scrambling configuration includes at least one of the following: a second sequence for descrambling messages, or a second sequence start point for descrambling messages.

[0124] In some example embodiments, the apparatus includes: components for receiving a preamble for random access from a terminal device; components for determining whether a first value of a logical channel identifier is different from a second value associated with another terminal device type based on determining that the preamble corresponds to multiple terminal device types; and components for determining the type of the terminal device based on determining that the first value of the logical channel identifier is different from the second value associated with another type.

[0125] In some example embodiments, the transport configuration is defined as the default configuration corresponding to the type of terminal device.

[0126] In some example embodiments, the apparatus includes components for transmitting transmission configurations in a system information block to a terminal device.

[0127] In some example implementations, the message includes at least one of the following: MSGA in a two-step random access procedure, or Msg3 in a four-step random access procedure.

[0128] In some example embodiments, the apparatus also includes components for performing other operations in some example embodiments of method 800 or network device 120. In some example embodiments, the components include: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform.

[0129] Figure 9 This is a simplified block diagram of a device 900 suitable for implementing an example embodiment of the present disclosure. Device 900 can be provided to implement a communication device, such as... Figure 1 The terminal device 110 or network device 120 shown. As shown, device 900 includes one or more processors 910, one or more memories 920 coupled to processor 910, and one or more communication modules 940 coupled to processor 910.

[0130] Communication module 940 is used for bidirectional communication. Communication module 940 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 940 may include at least one antenna.

[0131] As a non-limiting example, processor 910 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 900 can have multiple processors, such as application-specific integrated circuit chips that are time-dependent on a clock of a synchronous main processor.

[0132] Memory 920 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) 924, electrically programmable read-only memory (EPROM), flash memory, hard disk, optical disc (CD), digital video disc (DVD), optical disc, laser disc, and other magnetic and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 922 and other volatile memories that will not persist during power-off periods.

[0133] Computer program 930 includes computer-executable instructions that are executed by an associated processor 910. The instructions of program 930 may include instructions for performing operations / actions of some example embodiments of this disclosure. Program 930 may be stored in memory, such as ROM 924. Processor 910 can perform any suitable actions and processes by loading program 930 into RAM 922.

[0134] Example embodiments of this disclosure can be implemented using program 930, enabling device 900 to perform as described in the reference. Figures 2 to 8 Any process discussed in this disclosure. Exemplary embodiments of this disclosure may also be implemented in hardware or a combination of software and hardware.

[0135] In some example embodiments, program 930 may be tangibly contained in a computer-readable medium, which may be included in device 900 (such as in memory 920) or other storage devices accessible to device 900. Device 900 may load program 930 from the computer-readable medium into RAM 922 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" refers to a limitation on the medium itself (i.e., tangible, not tactile), rather than a limitation on the persistence of data storage (e.g., RAM versus ROM).

[0136] Figure 10 An example of a computer-readable medium 1000, which may be in the form of a CD, DVD, or other optical storage disc, is shown. A program 930 is stored on the computer-readable medium 1000.

[0137] Generally, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while others may be implemented in firmware or software executable 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 may be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0138] 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 that executes on a device on a target entity 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 a program module can be combined or split among program modules as needed. The machine-executable instructions for a 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.

[0139] The 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.

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

[0141] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, 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.

[0142] Furthermore, although operations are described in a specific order, this should not be construed as requiring such operations to be performed in the specific order shown or in a sequential order, or to perform all shown operations to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure, but rather as a description of features that may be specific to 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.

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

Claims

1. An apparatus comprising: At least one processor; as well as At least one memory stores instructions that, when executed by the at least one processor, cause the device to at least: Determine information associated with the message used for random access, wherein the information includes at least one of the following: The transmission configuration associated with the message and corresponding to the type of the device, or A logical channel identifier to be included in the message, the logical channel identifier having a first value, the first value being different from a second value associated with another terminal device type, wherein the first value indicates the type of the device; and The message is sent to the network device based on the information.

2. The apparatus of claim 1, wherein the transmission configuration includes a reference signal configuration for transmitting a demodulation reference signal associated with the message, and The at least one memory stores instructions that, when executed by the at least one processor, also cause the device to perform the following operations: The demodulation reference signal is configured to be sent to the network device using the reference signal configuration.

3. The apparatus of claim 2, wherein the reference signal configuration includes at least one of the following: For the antenna port of the demodulation reference signal, The first sequence used to generate the demodulated reference signal, or The first sequence starting point is used to generate the demodulated reference signal.

4. The apparatus according to any one of claims 1 to 3, wherein the transmission configuration includes a scrambling configuration for the message, and the transmitted message is scrambled based on the scrambling configuration.

5. The apparatus of claim 4, wherein the scrambling configuration comprises at least one of the following: A second sequence used to scramble the message, or The second sequence starting point is used to scramble the message.

6. The apparatus according to any one of claims 1 to 5, wherein in the transmitted message, the first value of the logical channel identifier is different from the second value associated with the other terminal device type, and the at least one memory stores instructions that, when executed by the at least one processor, also cause the apparatus to perform the following operations: Send a preamble for the random access to the network device, wherein the preamble corresponds to multiple terminal device types, including the type of the device and the other terminal device type.

7. The apparatus according to any one of claims 1 to 6, wherein the transmission configuration is defined as a default configuration corresponding to the type of the apparatus.

8. The apparatus according to any one of claims 1 to 6, wherein the at least one memory stores instructions that, when executed by the at least one processor, also cause the apparatus to perform the following operations: The transmission configuration is received from the system information block of the network device.

9. The apparatus according to any one of claims 1 to 8, wherein the message comprises at least one of the following: MSGA in a two-step random access process, or Msg3 in the four-step random access process.

10. An apparatus comprising: At least one processor; as well as At least one memory stores instructions that, when executed by the at least one processor, cause the device to at least: Receive messages for random access from the terminal device; as well as Based on information associated with the message, the type of the terminal device is determined, wherein the information includes at least one of the following: The transmission configuration associated with the message and corresponding to the type of the terminal device, or A logical channel identifier included in the message, the logical signal identifier having a first value that is different from a second value associated with another terminal device type, wherein the first value indicates the type of the terminal device.

11. The apparatus of claim 10, wherein the transmission configuration includes a reference signal configuration for receiving a demodulation reference signal associated with the message.

12. The apparatus of claim 11, wherein the reference signal configuration comprises at least one of the following: For the antenna port of the demodulation reference signal, The first sequence used for decoding the demodulated reference signal, or The first sequence start point used for decoding the demodulated reference signal.

13. The apparatus according to any one of claims 10 to 13, wherein the transmission configuration includes a scrambling configuration for the message, and the message is descrambled based on the scrambling configuration.

14. The apparatus of claim 13, wherein the scrambling configuration comprises at least one of the following: A second sequence used to descramble the message, or The second sequence starting point is used to descramble the message.

15. The apparatus according to any one of claims 10 to 14, wherein the at least one memory stores instructions that, when executed by the at least one processor, cause the apparatus to perform the following operations: Receive a preamble for the random access from the terminal device; Based on determining that the preamble corresponds to multiple terminal device types, it is determined whether the first value of the logical channel identifier is different from the second value associated with the other terminal device type; and The type of the terminal device is determined based on the fact that the first value of the logical channel identifier is different from the second value associated with the other type.

16. The apparatus according to any one of claims 10 to 15, wherein the transmission configuration is defined as a default configuration corresponding to the type of the terminal device.

17. The apparatus according to any one of claims 10 to 15, wherein the at least one memory stores instructions that, when executed by the at least one processor, cause the apparatus to perform the following operations: The transmission configuration in the system information block is sent to the terminal device.

18. The apparatus according to any one of claims 10 to 17, wherein the message comprises at least one of the following: MSGA in a two-step random access process, or Msg3 in the four-step random access process.

19. A method comprising: At the terminal device, information associated with the message used for random access is determined, wherein the information includes at least one of the following: The transmission configuration associated with the message and corresponding to the type of the terminal device, or A logical channel identifier to be included in the message, the logical channel identifier having a first value, the first value being different from a second value associated with another terminal device type, wherein the first value indicates the type of the terminal device; and The message is sent to the network device based on the information.

20. The method of claim 19, wherein the transmission configuration includes a reference signal configuration for transmitting a demodulation reference signal associated with the message, and the method includes: The demodulation reference signal is configured to be sent to the network device using the reference signal configuration.

21. The method of claim 20, wherein the reference signal configuration comprises at least one of the following: For the antenna port of the demodulation reference signal, The first sequence used to generate the demodulated reference signal, or The first sequence starting point is used to generate the demodulated reference signal.

22. The method of any one of claims 19 to 21, wherein the transmission configuration includes a scrambling configuration for the message, and the transmitted message is scrambled based on the scrambling configuration.

23. The method of claim 22, wherein the scrambling configuration comprises at least one of the following: A second sequence used to scramble the message, or The second sequence starting point is used to scramble the message.

24. The method of any one of claims 19 to 23, wherein in the transmitted message, the first value of the logical channel identifier is different from the second value associated with the other type, and the method comprises: Send a preamble for the random access to the network device, wherein the preamble corresponds to multiple terminal device types, including the type of the terminal device and another terminal device type.

25. The method according to any one of claims 19 to 24, wherein the transmission configuration is defined as a default configuration corresponding to the type of the terminal device.

26. The method according to any one of claims 19 to 24, further comprising: The transmission configuration is received from the system information block of the network device.

27. The method according to any one of claims 19 to 26, wherein the message comprises at least one of the following: MSGA in a two-step random access process, or Msg3 in the four-step random access process.

28. A method comprising: Receive messages for random access from terminal devices at the network device; as well as Based on information associated with the message, the type of the terminal device is determined, wherein the information includes at least one of the following: The transmission configuration associated with the message and corresponding to the type of the terminal device, or A logical channel identifier included in the message, the logical channel identifier having a first value that is different from a second value associated with another terminal device type, wherein the first value indicates the type of the terminal device.

29. The method of claim 28, wherein the transmission configuration includes a reference signal configuration for receiving a demodulation reference signal associated with the message.

30. The method of claim 29, wherein the reference signal configuration comprises at least one of the following: For the antenna port of the demodulation reference signal, The first sequence used for decoding the demodulated reference signal, or The first sequence start point used for decoding the demodulated reference signal.

31. The method of any one of claims 28 to 30, wherein the transmission configuration includes a scrambling configuration for the message, and the message is descrambled based on the scrambling configuration.

32. The method of claim 31, wherein the scrambling configuration comprises at least one of the following: A second sequence used to descramble the message, or The second sequence starting point is used to descramble the message.

33. The method according to any one of claims 28 to 32, wherein determining the type of the terminal device comprises: Receive a preamble for the random access from the terminal device; Based on determining that the preamble corresponds to multiple terminal device types, it is determined whether the first value of the logical channel identifier is different from the second value associated with the other terminal device type; and The type of the terminal device is determined based on the fact that the first value of the logical channel identifier is different from the second value associated with the other type.

34. The method according to any one of claims 28 to 33, wherein the transmission configuration is defined as a default configuration corresponding to the type of the terminal device.

35. The method according to any one of claims 28 to 33, further comprising: The transmission configuration in the system information block is sent to the terminal device.

36. The method according to any one of claims 28 to 35, wherein the message comprises at least one of the following: MSGA in a two-step random access process, or Msg3 in the four-step random access process.

37. An apparatus comprising: A component for determining information associated with a message used for random access, wherein said information includes at least one of the following: The transmission configuration associated with the message and corresponding to the type of the device, or A logical channel identifier to be included in the message, the logical channel identifier having a first value, the first value being different from a second value associated with another terminal device type, wherein the first value indicates the type of the device; and A component used to send the message to a network device based on the information.

38. An apparatus comprising: Components used to receive messages for random access from terminal devices; as well as A component for determining the type of the terminal device based on information associated with the message, wherein the information includes at least one of the following: The transmission configuration associated with the message and corresponding to the type of the terminal device, or A logical channel identifier included in the message, the logical channel identifier having a first value that is different from a second value associated with another terminal device type, wherein the first value indicates the type of the terminal device.

39. An apparatus comprising components for performing the method according to any one of claims 19 to 27.

40. An apparatus comprising components for performing the method according to any one of claims 28 to 36.

41. A computer-readable medium comprising instructions stored thereon, the instructions being configured to cause a device to at least: Determine information associated with the message used for random access, wherein the information includes at least one of the following: The transmission configuration associated with the message and corresponding to the type of the device, or A logical channel identifier to be included in the message, the logical channel identifier having a first value, the first value being different from a second value associated with another terminal device type, wherein the first value indicates the type of the device; and The message is sent to the network device based on the information.

42. A computer-readable medium comprising instructions stored thereon, the instructions being configured to cause a device to at least: Receive messages for random access from the terminal device; and Based on information associated with the message, the type of the terminal device is determined, wherein the information includes at least one of the following: The transmission configuration associated with the message and corresponding to the type of the terminal device, or A logical channel identifier included in the message, the logical channel identifier having a first value that is different from a second value associated with another terminal device type, wherein the first value indicates the type of the terminal device.

43. A computer-readable medium comprising instructions stored thereon for causing a device to perform at least the method according to any one of claims 19 to 27.

44. A computer-readable medium comprising instructions stored thereon for causing a device to perform at least the method according to any one of claims 28 to 36.

Images