CN117941451A

CN117941451A - Processing method, communication device and storage medium

Info

Publication number: CN117941451A
Application number: CN202280057889.XA
Authority: CN
Inventors: 朱荣昌; 黄钧蔚
Original assignee: Shenzhen Transsion Holdings Co Ltd
Current assignee: Shenzhen Transsion Holdings Co Ltd
Priority date: 2021-08-23
Filing date: 2022-05-24
Publication date: 2024-04-26
Also published as: WO2023024613A1; CN113423145A

Abstract

The embodiment of the application provides a processing method, communication equipment and a storage medium, which relate to the communication technology, and enable network equipment to know the type of terminal equipment by sending preamble and/or PUSCH (physical uplink shared channel) containing equipment type information.

Description

Processing method, communication device and storage medium

The present application claims priority from the chinese patent office, application number 2021109705582, application name "processing method, communication device and storage medium" filed at month 08 and 23 of 2021, the entire contents of which are incorporated herein by reference.

Technical Field

The present application relates to communication technologies, and in particular, to a processing method, a communication device, and a storage medium.

Background

With the development of 5G technology, the market for Redcap type (Reduced Capability, lightweight capability) devices with low power consumption and low load is becoming wider and wider.

In order to enable the network device to distinguish between the normal device and the Redcap type device, in some implementations, when the device transmits the Msg1, different preambles (preambles) may be set in the Msg1 to distinguish between the normal type device and the Redcap type device, and different RO (PRACH Occasion, random access opportunity) opportunities may be used by the different types of devices, thereby distinguishing between the device types.

In the course of conception and implementation of the present application, the inventors found that at least the following problems exist: the number of preambles carried in one RO opportunity is limited, if a part of preambles is reserved for Redcap types of devices, the available preambles of common devices are reduced, and/or if different types of devices use different schemes of RO opportunities, the available random access opportunities of the common devices are reduced, that is, the schemes cannot guarantee access of a large number of Redcap users.

The foregoing description is provided for general background information and does not necessarily constitute prior art.

Disclosure of Invention

The application provides a processing method, communication equipment and a storage medium, which are used for solving the technical problems of increasing the overhead of a system or reducing available preamble of common equipment.

In a first aspect, the present disclosure provides a processing method, applied to a terminal device, the method including the steps of:

S1: determining or generating a random access preamble and/or a physical uplink shared channel; wherein the determined or generated random access preamble code comprises equipment type identification information; the physical uplink shared channel determined or generated comprises equipment type identification information;

S2: transmitting the random access preamble and/or if transmitting the physical uplink shared channel.

In a second aspect, the present disclosure provides a processing method applied to a terminal device, the method including the steps of:

S1: receiving a system message, and determining a mode of reporting the equipment type according to the system message; reporting the equipment type and/or the equipment type through a random access preamble and/or a physical uplink shared channel;

s2: and reporting the equipment type according to the determined equipment type reporting mode during random access.

In a third aspect, the present disclosure provides a processing method applied to a network device, the method including:

S3: receiving a random access preamble and/or a physical uplink shared channel sent by terminal equipment; wherein the random access preamble and/or the physical uplink shared channel comprises equipment type identification information;

S4: and identifying the type of the terminal equipment according to the random access preamble and/or the physical uplink shared channel.

In a fourth aspect, the present disclosure provides a communication device comprising:

A memory;

A processor;

Wherein the memory has stored therein a computer program which, when executed by the processor, implements the method according to any of the first to third aspects.

According to the processing method, the communication device and the storage medium provided by the embodiment of the application, the network device is enabled to know the type of the terminal device by sending the preamble and/or the Physical Uplink SHARED CHANNEL (PUSCH) comprising the device type information, and the method does not need to reserve a random access preamble or additionally increase the system overhead, so that the purpose of distinguishing the terminal device types can be realized with lower communication cost.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application. In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly described below, and it will be obvious to those skilled in the art that other drawings can be obtained from these drawings without inventive effort.

Fig. 1 is a schematic diagram of a hardware structure of a mobile terminal implementing various embodiments of the present application;

Fig. 2 is a schematic diagram of a communication network system according to an embodiment of the present application;

Fig. 3 is a schematic diagram of a four-step random access procedure shown in an exemplary embodiment;

FIG. 4 is a schematic diagram of a two-step random access procedure shown in an exemplary embodiment;

FIG. 5 is a flow chart of a processing method shown in a first exemplary embodiment of the present disclosure;

fig. 6A is a flowchart illustrating a processing method applied to two-step random access according to a first exemplary embodiment of the present disclosure;

Fig. 6B is a flowchart illustrating a processing method applied to two-step random access according to a second exemplary embodiment of the present disclosure;

Fig. 6C is a flowchart illustrating a processing method applied to two-step random access according to a third exemplary embodiment of the present disclosure;

fig. 7A is a flowchart illustrating a processing method applied to four-step random access according to a first exemplary embodiment of the present disclosure;

Fig. 7B is a flowchart illustrating a processing method applied to four-step random access according to a second exemplary embodiment of the present disclosure;

fig. 7C is a flowchart illustrating a processing method applied to four-step random access according to a third exemplary embodiment of the present disclosure;

8A-8C are schematic diagrams of structures of preambles shown in exemplary embodiments of the present disclosure;

fig. 9A to 9C are schematic structural diagrams of a preamble including device type identification information according to an exemplary embodiment of the present disclosure;

Fig. 10 is a schematic diagram of at least one random access preamble shown in an exemplary embodiment of the present disclosure;

fig. 11 is an association relationship between SSB and RO opportunity shown in the first exemplary embodiment of the present disclosure;

fig. 12 is an association relationship between SSB and RO opportunity shown in a second exemplary embodiment of the present disclosure;

FIG. 13 is a diagram of time-frequency resources shown in an exemplary embodiment of the present disclosure;

fig. 14A is a flowchart illustrating a processing method applied to a four-step random access according to a fourth exemplary embodiment of the present disclosure;

fig. 14B is a flowchart illustrating a processing method applied to two-step random access according to a fourth exemplary embodiment of the present disclosure;

fig. 15 is a flowchart illustrating a processing method applied to a four-step random access according to a fifth exemplary embodiment of the present disclosure;

Fig. 16A is a flowchart illustrating a processing method applied to a four-step random access according to a sixth exemplary embodiment of the present disclosure;

Fig. 16B is a flowchart illustrating a processing method applied to two-step random access according to a fifth exemplary embodiment of the present disclosure;

fig. 17 is a flowchart illustrating a processing method according to a second exemplary embodiment of the present disclosure;

fig. 18 is a flowchart illustrating a processing method according to a third exemplary embodiment of the present disclosure;

Fig. 19 is a flowchart illustrating a processing method according to a fourth exemplary embodiment of the present disclosure;

fig. 20 is a flowchart illustrating a processing method according to a fifth exemplary embodiment of the present disclosure;

fig. 21 is a flowchart illustrating a processing method according to a sixth exemplary embodiment of the present disclosure;

fig. 22 is a flowchart of a processing method shown in a seventh exemplary embodiment of the present disclosure;

fig. 23A is a flowchart illustrating a processing method applied to two-step random access according to a sixth exemplary embodiment of the present disclosure;

fig. 23B is a flowchart illustrating a processing method applied to two-step random access according to a seventh exemplary embodiment of the present disclosure;

fig. 23C is a flowchart illustrating a processing method applied to two-step random access according to an eighth exemplary embodiment of the present disclosure;

Fig. 24A is a flowchart illustrating a processing method applied to a four-step random access according to a seventh exemplary embodiment of the present disclosure;

Fig. 24B is a flowchart illustrating a processing method applied to four-step random access according to an eighth exemplary embodiment of the present disclosure;

Fig. 24C is a flowchart illustrating a processing method applied to a four-step random access according to a ninth exemplary embodiment of the present disclosure;

Fig. 25 is a block diagram of a communication device according to an exemplary embodiment of the present application.

The achievement of the objects, functional features and advantages of the present application will be further described with reference to the accompanying drawings, in conjunction with the embodiments. Specific embodiments of the present application have been shown by way of the above drawings and will be described in more detail below. The drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but rather to illustrate the inventive concepts to those skilled in the art by reference to the specific embodiments.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, the element defined by the phrase "comprising one … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element, and furthermore, elements having the same name in different embodiments of the application may have the same meaning or may have different meanings, the particular meaning of which is to be determined by its interpretation in this particular embodiment or by further combining the context of this particular embodiment.

It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope herein. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "in response to a determination" depending on the context. Furthermore, as used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms "comprises," "comprising," "includes," and/or "including" specify the presence of stated features, steps, operations, elements, components, items, categories, and/or groups, but do not preclude the presence, presence or addition of one or more other features, steps, operations, elements, components, items, categories, and/or groups. The terms "or", "and/or", "including at least one of", and the like, as used herein, may be construed as inclusive, or mean any one or any combination. For example, "including at least one of: A. b, C "means" any one of the following: a, A is as follows; b, a step of preparing a composite material; c, performing operation; a and B; a and C; b and C; a and B and C ", again as examples," A, B or C "or" A, B and/or C "means" any of the following: a, A is as follows; b, a step of preparing a composite material; c, performing operation; a and B; a and C; b and C; a and B and C). An exception to this definition will occur only when a combination of elements, functions, steps or operations are in some way inherently mutually exclusive.

It should be understood that, although the steps in the flowcharts in the embodiments of the present application are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited in order and may be performed in other orders, unless explicitly stated herein. Moreover, at least some of the steps in the figures may include multiple sub-steps or stages that are not necessarily performed at the same time, but may be performed at different times, the order of their execution not necessarily occurring in sequence, but may be performed alternately or alternately with other steps or at least a portion of the other steps or stages.

The words "if", as used herein, may be interpreted as "at … …" or "at … …" or "in response to a determination" or "in response to a detection", depending on the context. Similarly, the phrase "if determined" or "if detected (stated condition or event)" may be interpreted as "when determined" or "in response to determination" or "when detected (stated condition or event)" or "in response to detection (stated condition or event), depending on the context.

It should be noted that, in this document, step numbers such as 501 and 502 are used for the purpose of more clearly and briefly describing the corresponding content, and not to constitute a substantial limitation on the sequence, and those skilled in the art may execute 502 first and then execute 501 when they are implemented, which is within the scope of the present application.

It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.

In the following description, suffixes such as "module", "part" or "unit" for representing elements are used only for facilitating the description of the present application, and have no specific meaning per se. Thus, "module," "component," or "unit" may be used in combination.

In the present application, the communication device may be a terminal device or a network device (such as a base station), which is specifically determined according to the context, and the terminal device may be implemented in various forms. For example, the terminal device described in the present application may include a mobile terminal such as a mobile phone, a tablet computer, a notebook computer, a palm computer, a Personal digital assistant (Personal DIGITAL ASSISTANT, PDA), a Portable media player (Portable MEDIA PLAYER, PMP), a navigation device, a wearable device, a smart bracelet, a pedometer, and a fixed terminal such as a digital TV, a desktop computer, and the like.

The following description will be explained taking a mobile terminal as an example of a terminal device, and those skilled in the art will understand that the configuration according to the embodiment of the present application can be applied to a fixed type terminal in addition to elements particularly used for a mobile purpose.

Referring to fig. 1, which is a schematic diagram of a hardware structure of a mobile terminal implementing various embodiments of the present application, the mobile terminal 100 may include: an RF (Radio Frequency) unit 101, a WiFi module 102, an audio output unit 103, an a/V (audio/time Frequency) input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, a processor 110, and a power supply 111. Those skilled in the art will appreciate that the mobile terminal structure shown in fig. 1 is not limiting of the mobile terminal and that the mobile terminal may include more or fewer components than shown, or may combine certain components, or a different arrangement of components.

The following describes the components of the mobile terminal in detail with reference to fig. 1:

The radio frequency unit 101 may be used for receiving and transmitting signals during the information receiving or communication process, specifically, after receiving downlink information of the base station, processing the downlink information by the processor 110; and, the uplink data is transmitted to the base station. Typically, the radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 101 may also communicate with networks and other devices via wireless communications. The wireless communication may use any communication standard or protocol, including but not limited to GSM (Global System of Mobile communication, global System for Mobile communications), GPRS (GENERAL PACKET Radio Service), CDMA2000 (Code Division Multiple Access, code Division multiple Access 2000), WCDMA (Wideband Code Division Multiple Access ), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access, time Division synchronous code Division multiple Access), FDD-LTE (Frequency Division Duplexing-Long Term Evolution, frequency Division Duplex Long term evolution), TDD-LTE (Time Division Duplexing-Long Term Evolution, time Division Duplex Long term evolution), 5G, and the like.

WiFi belongs to a short-distance wireless transmission technology, and a mobile terminal can help a user to send and receive e-mails, browse web pages, access streaming media and the like through the WiFi module 102, so that wireless broadband Internet access is provided for the user. Although fig. 1 shows a WiFi module 102, it is understood that it does not belong to the necessary constitution of a mobile terminal, and can be omitted entirely as required within a range that does not change the essence of the invention.

The audio output unit 103 may convert audio data received by the radio frequency unit 101 or the WiFi module 102 or stored in the memory 109 into an audio signal and output as sound when the mobile terminal 100 is in a call signal reception mode, a talk mode, a recording mode, a voice recognition mode, a broadcast reception mode, or the like. Also, the audio output unit 103 may also provide audio output (e.g., a call signal reception sound, a message reception sound, etc.) related to a specific function performed by the mobile terminal 100. The audio output unit 103 may include a speaker, a buzzer, and the like.

The a/V input unit 104 is used for receiving audio or time-frequency signals. The a/V input unit 104 may include a graphics processor (Graphics Processing Unit, GPU) 1041 and a microphone 1042, the graphics processor 1041 processing still pictures or time-frequency image data obtained by an image capturing device (e.g. a camera) in a time-frequency capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 106. The image frames processed by the graphics processor 1041 may be stored in the memory 109 (or other storage medium) or transmitted via the radio frequency unit 101 or the WiFi module 102. The microphone 1042 can receive sound (audio data) via the microphone 1042 in a phone call mode, a recording mode, a voice recognition mode, and the like, and can process such sound into audio data. The processed audio (voice) data may be converted into a format output that can be transmitted to the mobile communication base station via the radio frequency unit 101 in the case of a telephone call mode. The microphone 1042 may implement various types of noise cancellation (or suppression) algorithms to cancel (or suppress) noise or interference generated in the course of receiving and transmitting the audio signal.

The mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors. Optionally, the light sensor includes an ambient light sensor and a proximity sensor, optionally, the ambient light sensor may adjust the brightness of the display panel 1061 according to the brightness of ambient light, and the proximity sensor may turn off the display panel 1061 and/or the backlight when the mobile terminal 100 moves to the ear. As one of the motion sensors, the accelerometer sensor can detect the acceleration in all directions (generally three axes), and can detect the gravity and direction when stationary, and can be used for applications of recognizing the gesture of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer gesture calibration), vibration recognition related functions (such as pedometer and knocking), and the like; as for other sensors such as fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc. that may also be configured in the mobile phone, the detailed description thereof will be omitted.

The display unit 106 is used to display information input by a user or information provided to the user. The display unit 106 may include a display panel 1061, and the display panel 1061 may be configured in the form of a Liquid crystal display (Liquid CRYSTAL DISPLAY, LCD), an Organic Light-Emitting Diode (OLED), or the like.

The user input unit 107 may be used to receive input numeric or character information and to generate key signal inputs related to user settings and function control of the mobile terminal. Alternatively, the user input unit 107 may include a touch panel 1071 and other input devices 1072. The touch panel 1071, also referred to as a touch screen, may collect touch operations thereon or thereabout by a user (e.g., operations of the user on the touch panel 1071 or thereabout by using any suitable object or accessory such as a finger, a stylus, etc.) and drive the corresponding connection device according to a predetermined program. The touch panel 1071 may include two parts of a touch detection device and a touch controller. Optionally, the touch detection device detects the touch azimuth of the user, detects a signal brought by touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, and sends the touch point coordinates to the processor 110, and can receive and execute commands sent from the processor 110. Further, the touch panel 1071 may be implemented in various types such as resistive, capacitive, infrared, and surface acoustic wave. The user input unit 107 may include other input devices 1072 in addition to the touch panel 1071. Alternatively, other input devices 1072 may include, but are not limited to, one or more of a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, mouse, joystick, etc., as specifically not limited herein.

Alternatively, the touch panel 1071 may overlay the display panel 1061, and when the touch panel 1071 detects a touch operation thereon or thereabout, the touch panel 1071 is transferred to the processor 110 to determine the type of touch event, and the processor 110 then provides a corresponding visual output on the display panel 1061 according to the type of touch event. Although in fig. 1, the touch panel 1071 and the display panel 1061 are two independent components for implementing the input and output functions of the mobile terminal, in some embodiments, the touch panel 1071 may be integrated with the display panel 1061 to implement the input and output functions of the mobile terminal, which is not limited herein.

The interface unit 108 serves as an interface through which at least one external device can be connected with the mobile terminal 100. For example, the external devices may include wired or wireless headset ports, external power (or battery charger) ports, wired or wireless data ports, memory card ports, ports for connecting devices having identification modules, audio input/output (I/O) ports, time-frequency I/O ports, earphone ports, and the like. The interface unit 108 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the mobile terminal 100 or may be used to transmit data between the mobile terminal 100 and an external device.

Memory 109 may be used to store software programs as well as various data. The memory 109 may mainly include a storage program area and a storage data area, and alternatively, the storage program area may store an operating system, an application program required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, phonebook, etc.) created according to the use of the handset, etc. In addition, memory 109 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.

The processor 110 is a control center of the mobile terminal, connects various parts of the entire mobile terminal using various interfaces and lines, and performs various functions of the mobile terminal and processes data by running or executing software programs and/or modules stored in the memory 109 and calling data stored in the memory 109, thereby performing overall monitoring of the mobile terminal. Processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor and a modem processor, the application processor optionally handling mainly an operating system, a user interface, an application program, etc., the modem processor handling mainly wireless communication. It will be appreciated that the modem processor described above may not be integrated into the processor 110.

The mobile terminal 100 may further include a power source 111 (e.g., a battery) for supplying power to the respective components, and preferably, the power source 111 may be logically connected to the processor 110 through a power management system, so as to perform functions of managing charging, discharging, and power consumption management through the power management system.

Although not shown in fig. 1, the mobile terminal 100 may further include a bluetooth module or the like, which is not described herein.

In order to facilitate understanding of the embodiments of the present application, a communication network system on which the mobile terminal of the present application is based will be described below.

Referring to fig. 2, fig. 2 is a schematic diagram of a communication network system according to an embodiment of the present application, where the communication network system is an LTE system of a general mobile communication technology, and the LTE system includes a UE (User Equipment) 201, an e-UTRAN (Evolved UMTS Terrestrial Radio Access Network ) 202, an epc (Evolved Packet Core, evolved packet core) 203, and an IP service 204 of an operator that are sequentially connected in communication.

Alternatively, the UE201 may be the terminal 100 described above, which is not described here again.

The E-UTRAN202 includes eNodeB2021 and other eNodeB2022, etc. Alternatively, the eNodeB2021 may connect with other enodebs 2022 over a backhaul (e.g., X2 interface), the eNodeB2021 is connected to the EPC203, and the eNodeB2021 may provide access for the UE201 to the EPC 203.

EPC203 may include MME (Mobility MANAGEMENT ENTITY ) 2031, hss (Home Subscriber Server, home subscriber server) 2032, other MMEs 2033, SGW (SERVING GATE WAY ) 2034, pgw (PDN GATE WAY, packet data network gateway) 2035, PCRF (Policy AND CHARGING Rules Function) 2036, and so on. Optionally, MME2031 is a control node that handles signaling between UE201 and EPC203, providing bearer and connection management. HSS2032 is used to provide registers to manage functions such as home location registers (not shown) and to hold user specific information about service characteristics, data rates, etc. All user data may be sent through SGW2034 and PGW2035 may provide IP address allocation and other functions for UE201, PCRF2036 is a policy and charging control policy decision point for traffic data flows and IP bearer resources, which selects and provides available policy and charging control decisions for a policy and charging enforcement function (not shown).

IP services 204 may include the internet, intranets, IMS (IP Multimedia Subsystem ), or other IP services, etc.

Although the LTE system is described above as an example, it should be understood by those skilled in the art that the present application is not limited to LTE systems, but may be applied to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, and future new network systems (e.g., 5G), etc.

Based on the above-mentioned mobile terminal hardware structure and communication network system, various embodiments of the present application are presented.

Currently, more and more types of terminal devices capable of accessing to a network are available, for example, some household appliances, wearable devices and the like can be accessed to the network, and the devices can be a refrigerator, a television, an air conditioner, a smart watch, a mobile bracelet and the like.

The types of the terminal devices may include common devices and light capacity (Redcap) devices, and the processing manners of the network devices to different terminal devices may be different, so that the network devices need to determine the types of the terminal devices.

Alternatively, at random access, the terminal device may send a random access preamble (preamble) corresponding to its device type in Msg1 or MsgA, and the network device distinguishes whether the current terminal is a normal UE or RedcapUE according to the received preamble.

Fig. 3 is a schematic diagram of a four-step random access procedure according to an exemplary embodiment.

As shown in fig. 3, in the four-step random access procedure, when the terminal device sends a Message1 (Message 1, msg 1), a preamble is sent to the network device.

Fig. 4 is a schematic diagram of a two-step random access procedure shown in an exemplary embodiment.

As shown in fig. 4, in the two-step random access procedure, when the terminal device sends a message a (MsgA), the terminal device sends a preamble to the network device.

Optionally, different types of devices can be distinguished by different preambles, and since the protocol specifies that the number of selectable preamble numbers in a random access process of a terminal device is at most 64, if the device type distinction is performed by the existing preamble, a part of the preamble needs to be reserved for Redcap devices, which results in that the available preambles of common devices are reduced.

Optionally, different types of devices may also use different RO opportunities to perform random access, so that the network device distinguishes the types of the terminal devices according to the messages received by the different RO opportunities. But this approach results in less chance of access by the generic device.

In order to solve the technical problem, in the solution provided in the embodiment of the present application, when a terminal device is randomly accessed, the terminal device reports the device type through an improved random access preamble (preamble) and/or an improved Physical Uplink Shared Channel (PUSCH), and this embodiment does not need to occupy the preamble of a common UE, nor occupy the random access opportunity of the common UE, but still can implement reporting of the device type.

Fig. 5 is a flowchart illustrating a processing method according to a first exemplary embodiment of the present disclosure.

The processing method provided by the embodiment of the application is applied to the terminal equipment, and the terminal equipment can be accessed to a network, and can be common equipment or light capacity equipment.

As shown in fig. 5, the processing method provided by the embodiment of the present application includes:

Step 501, a random access preamble and/or a physical uplink shared channel is determined or generated.

Optionally, the determined or generated random access preamble includes device type identification information.

Optionally, the determined or generated physical uplink shared channel includes device type identification information therein.

Alternatively, the present solution may be applied to a random access procedure, where the random access procedure refers to a procedure from when a preamble is sent from a terminal device to when an attempt to access a network is made until a basic signaling connection is established between the terminal device and the network.

Optionally, when random access is performed, the terminal device may determine or generate a preamble, and may add device type identification information to the preamble according to its device type. For example, a resource bit may be reserved in the preamble, and the terminal device may add device type identification information to the reserved resource bit, for example, if the type of the terminal device is a common device, 1 is added to the reserved resource bit of the preamble, and if the type of the terminal device is Redcap devices, 0 is added to the reserved resource bit of the preamble.

Alternatively, the preamble that is determined or generated may be composed of three parts, CP (Cyclic Prefix), SEQ (SEQuence ), GP (Guard Period).

Alternatively, the preamble determined or generated may include only the CP and SEQ portions. If the scheme of the embodiment of the application needs to add the equipment type identification information in the GP part of the preamble, the scheme of the embodiment is not applicable to the preamble which only comprises the CP part and the SEQ part; if the scheme of the embodiment of the application needs to add the equipment type identification information in the CP part of the preamble, the scheme of the embodiment is applicable to the preambles of the two construction types. The device type identification information is used for indicating the type of the device, for example, if the device is a common type device, the preamble of the device includes information corresponding to the common device type, and if the device is a light capability device, the preamble of the device includes information corresponding to the light capability device type.

Optionally, device type identification information may be set in any preamble.

Optionally, the GP portion of the preamble sent by the terminal device has device type identification information, and the network device (e.g., base station) may receive the preamble set with the device type identification information. The specific implementation steps are as follows: the terminal equipment determines or generates a root sequence of the preamble according to the high-level parameters, generates an SEQ part of the preamble according to a generation formula of the preamble given by the protocol, further adds a CP and a GP for the SEQ part, and adds equipment type identification information to designated resources in the GP.

The device type identification information may be added only for one preamble that is ultimately used by the terminal, or may be added for at least one preamble that is potentially used by the terminal.

Optionally, the preamble determined or generated by the terminal device includes device type identification information. The device type identification information may be located in any component of the preamble.

Optionally, device type identification information may be added in the GP of the preamble. At least one resource may be selected in the GP portion with which to indicate the device type. For example, when the device type identification information is not added, the value of each resource in the GP portion of the preamble is 0, if the terminal device is Redcap devices, the value of each resource in the GP portion of the preamble of the terminal device for indicating the device type or the indication bit is 1, and/or if the terminal device is a common device, the value of each resource in the GP portion of the preamble of the terminal device is still 0. Alternatively, the specific indicated bit positions and numbers may be set according to the requirements.

Optionally, device type identification information may be added in the CP of the preamble. For example, the device type identification information is indicated using at least one resource in the CP portion.

Optionally, device type identification information may be added in the preamble of SEQ. For example, the device type identification information is indicated using at least one resource in the SEQ portion.

In the implementation manner, the device type information can be reported through the preamble, and the method does not need to reserve a random access preamble or occupy additional random access opportunities, so that the purpose of distinguishing the terminal device types can be realized with lower communication cost.

Optionally, at random access, the terminal device may also send PUSCH (Physical Uplink SHARED CHANNEL ) to the network device. PUSCH is used to carry uplink traffic and upper layer signaling data. For example, in two-step random access, the PUSCH may be transmitted when the terminal device transmits Msg a. For another example, in the case of four-step random access, PUSCH may be transmitted when the terminal device transmits Msg 3.

Alternatively, the terminal device may determine or generate a PUSCH at random access, where the PUSCH includes device type identification information. For example, the terminal device may determine its device type and add information corresponding to the device type in the PUSCH.

Alternatively, the terminal device may add device type identification information to reserved resource bits in PUSCH for distinguishing the type of the terminal device.

Optionally, the terminal device may add information for distinguishing the type of the terminal device in the PUSCH by using the processed TC-RNTI value; specifically, the terminal device processes the TC-RNTI according to the device type, and then scrambles the PUSCH by the processed TC-RNTI. For example, if the device type of the terminal device is a common device, the TC-RNTI carried in the Msg 2 may be directly used to scramble the PUSCH, and if the device type of the terminal device is Redcap devices, the terminal device may process the TC-RNTI carried in the Msg 2 and then use the processed TC-RNTI value to scramble the PUSCH. The network side can descramble the PUSCH according to the processed TC-RNTI value to distinguish the type of the terminal device.

Optionally, the terminal device may distinguish the type of the terminal device according to the PUSCH scrambling sequence related to the type of the device; specifically, if the device type of the terminal device is a common device, the terminal device uses a first scrambling formula to scramble the PUSCH; if the device type of the terminal device is Redcap devices, the terminal device uses a second scrambling formula, such as (1) or (2), to scramble the PUSCH. Through different scrambling sequences, the network side can rapidly distinguish the types of the terminal equipment. Wherein the values of the formulas (1) and (2) are as follows:

C _init＝n _RNTI·2 ¹⁶+n _ID+delta (1)

C _init＝n _RNTI·2 ¹⁶+n _RAPID·2 ¹⁰+n _ID+delta (2)

Wherein, in the two-step random access, nRNTI is equal to RA-RNTI, and in the four-step random access, nRNTI is equal to TC-RNTI issued by Msg 2.

In the two-step random access, the higher layer parameters msgA-DataScramblingIndex are used for configuring n _ID,n _ID E {0,1, …,1024}, in the four-step random access,I.e. cell ID.

N _RAPID is the index of the random access preamble of Msg a and delta is the preset offset.

In the implementation manner, the device type information can be reported through the PUSCH, and the method does not need to reserve a random access preamble or occupy additional random access opportunities, so that the purpose of distinguishing the terminal device types can be realized with lower communication cost.

Optionally, the preamble determined or generated by the terminal device may include device type identification information, and the PUSCH determined or generated by the terminal device may also include device type identification information, where the network device may identify the type of the terminal device based on the information.

Step 502, a random access preamble and/or a physical uplink shared channel is transmitted.

Optionally, the terminal device may send a preamble including device type identification information and/or send a PUSCH including device type identification information to the network device, thereby reporting the device type. The terminal device can select the device type reported by the preamble, can select the device type reported by the PUSCH, and can also select the device type reported by the preamble and the PUSCH at the same time.

If the terminal device generates a preamble including device type identification information, the terminal device may send the preamble to the network device to report the device type. If the terminal device generates a PUSCH including device type identification information, the terminal device may send the PUSCH to the network device to report the device type.

Alternatively, in the two-step random access, the terminal device may transmit a preamble including device type identification information when transmitting Msg a, and may also transmit a PUSCH including device type identification information when transmitting Msg a.

Alternatively, in the four-step random access, the terminal device may transmit a preamble including device type identification information when transmitting Msg 1, and may also transmit a PUSCH including device type identification information when transmitting Msg 3.

Optionally, if the preamble sent by the terminal device includes device type identification information, after the network device receives the preamble sent by the terminal device, the network device may acquire the device type identification information therein, further determine the type of the terminal device, and perform corresponding processing according to the type of the terminal device. If the PUSCH transmitted by the terminal device includes the device type identification information, the network device may acquire the device type identification information after receiving the PUSCH transmitted by the terminal device, further determine the type of the terminal device, and perform corresponding processing according to the type of the terminal device.

Optionally, the terminal device and the network device may pre-agree on a location of a device type in the preamble and/or PUSCH, or add the device type to the preamble and/or PUSCH, so that after the network device receives the preamble and/or PUSCH, the network device may obtain, based on the pre-agreed location or mode, device type identification information from the preamble and/or PUSCH, so as to determine a type of the terminal device.

According to the processing method provided by the embodiment of the application, the network equipment is enabled to know the type of the terminal equipment by sending the preamble and/or the PUSCH comprising the equipment type information, and the mode does not need to reserve the random access preamble or occupy additional random access opportunities, so that the purpose of distinguishing the type of the terminal equipment can be realized with lower communication cost.

Fig. 6A is a flowchart illustrating a processing method applied to two-step random access according to a first exemplary embodiment of the present disclosure.

The processing method provided by the disclosure can be applied to a two-step random access scene.

As shown in fig. 6A, in the processing method provided in the present disclosure, when two steps of random access are performed, the method may include:

In step 601A, a preamble containing device type identification information is sent in Msg a.

Step 602A, receive Msg B.

Optionally, the terminal device may report the device type through a preamble. Specifically, a preamble including device type identification information may be generated during random access, and the preamble may be sent to a network device through Msg a.

Optionally, after receiving the Msg a, the network device may also send an Msg B to the terminal device, in response to the Msg a, and establish a connection with the terminal device.

Fig. 6B is a flowchart illustrating a processing method applied to two-step random access according to a second exemplary embodiment of the present disclosure.

As shown in fig. 6B, in the processing method provided in the present disclosure, when two steps of random access are performed, the method may include:

in step 601B, msg a is transmitted, and PUSCH including device type identification information is included in Msg a.

Step 602B, receiving Msg B.

Optionally, the terminal device may report the device type through PUSCH. Specifically, a PUSCH including device type identification information may be generated at random access, and transmitted to a network device through Msg a.

Fig. 6C is a flowchart illustrating a processing method applied to two-step random access according to a third exemplary embodiment of the present disclosure.

As shown in fig. 6C, in the processing method provided in the present disclosure, when two steps of random access are performed, the method may include:

in step 601C, msg a is transmitted, the Msg a including a preamble including device type identification information and PUSCH including device type identification information.

Step 602C, receive Msg B.

Optionally, the terminal device may report the device type through preamble and PUSCH, which can improve accuracy of the network device in identifying the type of the terminal device. Specifically, a preamble and a PUSCH including device type identification information may be generated during random access, and the preamble and the PUSCH may be sent to a network device through Msg a. In this implementation, both preamble and PUSCH include device types of the terminal device.

Fig. 7A is a flowchart illustrating a processing method applied to four-step random access according to a first exemplary embodiment of the present disclosure.

The processing method provided by the disclosure can be applied to a four-step random access scene.

As shown in fig. 7A, in the processing method provided in the present disclosure, when four steps of random access are performed, the method may include:

In step 701A, msg 1 is transmitted, where Msg 1 has a preamble containing device type identification information.

In step 702A, msg 2 is received, where Msg 2 includes a preamble ID resolved by a base station, UL Grant authorized by uplink resources of Msg 3, and a terminal temporary identifier tc_rnti and a time advance TA.

In step 703A, transmitting Msg 3, determining that the preamble ID received in Msg 2 is the same as the preamble ID transmitted by Msg 1, and adjusting the PUSCH transmission time according to the TA value carried by Msg 2, so as to perform PUSCH transmission.

In step 704A, msg4 is received.

Optionally, when the terminal device is accessed at random in four steps, the terminal device may report the device type to the network device through the preamble.

Optionally, the terminal device may generate or determine a preamble according to the device type, where the preamble includes device type identification information. And sending the preamble through the Msg 1, thereby reporting the device type. The terminal device sends a random access request to the network device by sending Msg 1 to the network device.

Optionally, the network device may further send Msg2 to the terminal device, where the Msg2 includes a preamble_id, a tc_rnti, and a TA, so as to respond to the random access request of the terminal device.

Optionally, the terminal device may also send Msg 3 to the network device, where PUSCH may be included in Msg 3.

Optionally, the network device may also send Msg 4 to the terminal device, and establish a connection with the terminal device.

Fig. 7B is a flowchart illustrating a processing method applied to four-step random access according to a second exemplary embodiment of the present disclosure.

As shown in fig. 7B, in the processing method provided in the present disclosure, when four steps of random access are performed, the method may include:

In step 701B, msg 1 is sent, where Msg 1 includes a preamble.

In step 702B, msg2 is received, where Msg2 includes a preamble ID resolved by a base station, UL Grant authorized by uplink resources of Msg3, and a terminal temporary identifier tc_rnti and a time advance TA.

In step 703B, msg 3 is sent, it is determined that the preamble ID received in Msg2 is the same as the preamble ID sent by Msg1, and then the PUSCH sending time is adjusted according to the TA value carried by Msg2, so that the PUSCH including the device type identification information is sent in Msg 3.

In step 704B, msg4 is received.

Optionally, when the terminal device is accessed randomly in four steps, the terminal device can report the device type to the network device through the PUSCH.

Optionally, the terminal device may generate a preamble, and send the preamble through Msg1, where the preamble is generated in the same manner as the scheme in the prior art. The terminal device sends a random access request to the network device by sending Msg1 to the network device.

Optionally, the network device may also send Msg 2 to the terminal device, so as to respond to the random access request of the terminal device.

Optionally, the terminal device may further generate or determine a PUSCH according to its own device type, where the generated or determined PUSCH includes device type identification information. And the terminal equipment sends the PUSCH comprising the equipment type identification information to the network equipment through the Msg 3 to report the equipment type.

Fig. 7C is a flowchart illustrating a processing method applied to four-step random access according to a third exemplary embodiment of the present disclosure.

As shown in fig. 7C, in the processing method provided in the present disclosure, when four steps of random access are performed, the method may include:

In step 701C, msg 1 is sent, where Msg 1 has a preamble containing device type identification information.

In step 702C, msg 2 is received, where Msg 2 includes a preamble ID resolved by a base station, UL Grant authorized by uplink resources of Msg 3, and a terminal temporary identifier tc_rnti and a time advance TA.

In step 703C, msg 3 is sent, it is determined that the preamble ID received in Msg2 is the same as the preamble ID sent by Msg1, and then the PUSCH sending time is adjusted according to the TA value carried by Msg2, so that the PUSCH including the device type identification information is sent in Msg 3.

Step 704C, receiving Msg4.

Optionally, when the terminal device is accessed randomly in four steps, the terminal device may report the device type to the network device through the preamble and the PUSCH.

Optionally, the terminal device may further generate or determine a PUSCH according to its device type, where the generated PUSCH includes device type identification information. And the terminal equipment sends the PUSCH comprising the equipment type identification information to the network equipment through the Msg 3 to report the equipment type.

In the implementation manner, the terminal equipment can report the equipment type to the network equipment through the preamble and the PUSCH, and the accuracy of the network equipment in identifying the type of the terminal equipment can be improved.

In any of the above implementations, the terminal device determines whether to select a two-step random access mode or a four-step random access mode to access the network based on a distance from the terminal to a cell site or a received signal strength (RSRP).

Optionally, the preamble determined or generated by the terminal device may include device type identification information, and after the network device receives the preamble, the network device may determine the type of the terminal device according to the device type identification information therein.

Optionally, if the preamble includes device type identification information, the device type identification information may be located in a GP in the preamble. The GP is a guard interval, and the GP in the prior art is not used for carrying signaling data, so, by adding device type identification information to the GP, the structure of the preamble is the same as that of the preamble in the prior art, and further, the terminal device can report the device type identification information without greatly changing the terminal device and the network side device, and since the GP in the prior art is not used for carrying signaling data, setting the device type identification information in the GP does not affect other data carried in the preamble.

Fig. 8A-8C are schematic diagrams of structures of preambles shown in exemplary embodiments of the present disclosure.

As shown in fig. 8A, 8B, 8C, any preamble provided by the present disclosure includes three parts, CP 81, seq 82, GP 83. The device type identification information may be set in the GP 83 therein.

The preambles shown in fig. 8A-8C are only illustrative representations, and other forms of preambles may be provided as desired.

Optionally, the device type identification information is located in a designated resource unit of the GP. The resource unit may be designated in advance in the GP so that the device type identification information is placed using the designated resource unit.

Alternatively, the network device and the terminal device may pre-define a specified resource unit of the GP, so that the terminal device may set device type identification information in the specified resource unit of the GP, and the network device may read the device type identification information from the specified resource unit of the GP.

Fig. 9A to 9C are schematic structural diagrams of a preamble including device type identification information according to an exemplary embodiment of the present disclosure.

As shown in fig. 9A, device type identification information may be set in a first resource unit 831 of the GP of the preamble.

As shown in fig. 9B, device type identification information may be set in the last resource unit 832 of the GP of the preamble.

As shown in fig. 9C, the device type identification information may be set in any one of the resource units 833 between the first and last resource units of the preamble.

It should be noted that, any setting manner of the device type identification information may be applied to any preamble of any type.

For example, the device type identification information may be set in the first resource unit of the GP of the preamble as shown in fig. 8B or 8C.

For example, the device type identification information may be set in the last resource unit of the GP of the preamble as shown in fig. 8A or 8C.

For example, the device type identification information may be set in any one of the resource units between the first and last resource units of the preamble as shown in fig. 8A or 8B.

Optionally, the random access preamble generated by the terminal device includes at least one of:

a first partial random access preamble;

A second part of random access preamble;

The third part randomly accesses the preamble.

Optionally, the first partial preamble is used for contention-based random access.

Optionally, the second partial preamble is used for non-contention based random access.

Optionally, the third partial preamble is used for random access based on other purposes.

Optionally, the number of preambles generated by the terminal device is 64.

The 64 preambles may include at least one of the first partial preamble, the second partial preamble, and the third partial preamble.

Alternatively, the number of preambles generated by the terminal device may be another preset fixed value, specifically, the number of preambles may be determined according to the maximum number of terminals accommodated in the cell, for example, when the maximum number of terminals accommodated in the cell is 128, the number of terminals generating the preamble is 128.

Fig. 10 is a schematic diagram of at least one random access preamble shown in an exemplary embodiment of the present disclosure.

As shown in fig. 10, of the 64 preambles, 0-3, 7-10, 14-17..49-52 preambles function as contention-based random access, 4-6, 11-13, 53-55 preambles function as non-contention-based random access, and 56-63 preambles function as random access for other purposes.

Optionally, any of the 64 preambles corresponds to a corresponding SSB (Synchronization Signal Block ).

When transmitting the preamble, the terminal device may determine the SSB and transmit the preamble corresponding to the SSB.

Alternatively, one PRACH (Physical Random access channel) slot may have a plurality of RO opportunities, one RO opportunity occupying a number of symbols in the time domain and a number of subcarriers in the frequency domain. One RO opportunity represents the time-frequency resource of one preamble transmission.

Alternatively, each RO opportunity may be associated with multiple SSBs, e.g., if the parameters SSB-perRACH-OccasionAndCB-PreamblesPerSSB = N and N >1, then 1 RO opportunity is associated with N SSBs.

Fig. 11 is an association relationship between SSB and RO opportunity shown in the first exemplary embodiment of the present disclosure.

As shown in fig. 11, # is used to characterize the index of RO opportunities, one PRACH configuration period (PRACH configuration period) includes two PRACH slots, and may include 4 RO opportunities in one PRACH slot, where RO #0 occupies the same symbol as RO #1 but occupies a different subcarrier, and RO #2 occupies the same symbol as RO #3 but occupies a different subcarrier. RO#0 occupies a different symbol than RO#2.

Alternatively, RO#0 is associated with SSB 0 and SSB1, RO#1 is associated with SSB 2 and SSB 3, RO#2 is associated with SSB 4 and SSB 5, and RO#3 is associated with SSB 6 and SSB 7.

In this application scenario, which preamble to send may be determined according to the SSB indicated by the network device, for example, which preamble to send may be determined in combination with the correspondence between SSB and preamble shown in fig. 10. The RO opportunity for transmitting the preamble may also be selected according to a correspondence between SSBs and RO opportunities.

Alternatively, one SSB may also be associated with multiple RO opportunities, e.g., parameters SSB-perRACH-OccasionAndCB-PreamblesPerSSB =n and N < =1, then 1 SSB is associated with 1/N RO opportunities.

Fig. 12 is an association relationship between SSB and RO opportunity shown in a second exemplary embodiment of the present disclosure.

As shown in fig. 12, # is an index characterizing RO opportunities, one PRACH configuration period (PRACH configuration period) includes one PRACH slot, in which 8 RO opportunities may be included. In the figure, the frequency domain resources occupied by the RO opportunities in the same row are the same, and the time domain resources occupied by the RO opportunities in the same column are the same.

SSB 0 corresponds to ro#0 and ro#1, SSB 1 corresponds to ro#2 and ro#3, SSB 8 corresponds to ro#4 and ro#5, SSB 9 corresponds to ro#6 and ro#7, SSB 16 corresponds to ro#8 and ro#9, SSB 17 corresponds to ro#10 and ro#11, SSB 24 corresponds to ro#12 and ro#13, SSB 25 corresponds to ro#14 and ro#15, SSB 32 corresponds to ro#16 and ro#17, and SSB 33 corresponds to ro#18 and ro#19.

In this implementation, the RO opportunity for transmitting the preamble may be selected according to the SSB indicated by the network device and the correspondence between the SSB and the RO opportunity.

Optionally, if the determined or generated PUSCH includes device type identification information, then:

the device type identification information may be located in a reserved time-frequency resource of PUSCH;

the device type identification information may also be located in an identity of the terminal device;

The device type identification information may also be included in a scrambling sequence that scrambles the physical uplink shared channel.

Optionally, in any one of the foregoing implementations, if the device type is reported through PUSCH, determining or generating PUSCH when the four-step random access is performed, including at least one of the following:

Adding device type identification information in a reserved time-frequency resource position of the PUSCH;

Adding equipment type identification information into the identity mark in the PUSCH;

The PUSCH is scrambled with a scrambling sequence corresponding to the device type identification information.

For example, in the four-step random access, the device type is reported through the PUSCH, or the device type is reported through the PUSCH and the preamble, which may adopt at least one implementation manner.

Optionally, in any one of the foregoing implementations, if the device type is reported through PUSCH, determining or generating PUSCH when two steps are randomly accessed includes at least one of:

For example, in the two-step random access, the device type is reported through the PUSCH, or the device type is reported through the PUSCH and the preamble, which may adopt at least one implementation manner.

Optionally, when the terminal device adds the device type identification information in the reserved time-frequency resource position of the PUSCH, the reserved time-frequency resource position of the PUSCH may be determined specifically according to a preset mapping formula, and then the device type identification information may be added at the reserved time-frequency resource position.

Optionally, the preset mapping formula includes a frequency domain mapping formula and a time domain mapping formula. The frequency domain mapping formula is used for determining the frequency domain position of the device type identification information added in the PUSCH, and the time domain mapping formula is used for determining the time domain position of the device type identification information added in the PUSCH.

Optionally, the terminal device may determine the frequency domain position of the device type identification information in the bandwidth portion occupied by the PUSCH according to a frequency domain mapping formula, and determine the time domain position of the device type identification information in the time slot occupied by the PUSCH according to a time domain mapping formula.

Alternatively, the frequency domain location of the device type identification information may be determined in the bandwidth portion occupied by PUSCH based on the following equation:

Wherein k takes any value from 0 to 11, The number of RBs available in the portion of bandwidth occupied for PUSCH.

If two resource elements are reserved for the equipment type identification information in each resource block occupied by the PUSCH, k in the above formula takes any two values from 0 to 11.

Alternatively, the time domain location of the device type identification information may be determined in the PUSCH-occupied slot based on the following equation:

l=l ₀ +m; m is a random integer, I is less than or equal to 13, and l ₀ is the first symbol index occupied by the PUSCH in the time slot.

If the reported device type identification information occupies 2 different time domain symbols, the mapping formula for determining the time domain position may further include l' =l ₀ +j; j is a random integer different from m; or the symbol deviation between j and m is not more than a preset number of symbols, for example, the symbol deviation between two symbols is not more than 3 symbols; if l0=0 and m=4, the reserved second symbol index is j=4+3=7.

Similarly, if the reported device type identification information occupies a plurality of different time domain symbols, the mapping formula for determining other time domain positions needs to be redefined by rules.

Fig. 13 is a diagram of time-frequency resources shown in an exemplary embodiment of the present disclosure.

As shown in fig. 13, the frequency domain resources are characterized vertically and the time-frequency resources are characterized horizontally. In the figure, one RB in the frequency domain and one symbol in the time domain are taken as an example, and the resource position reserved for the equipment type identification information in each RB occupied by the PUSCH is reserved.

Setting the time domain symbol index occupied by the PUSCH as symbols 2,3,4, 11; the number of RBs occupied by the PUSCH frequency domain is 6. When k=6 and m=6, it can be determined that the frequency domain index is 6, 18, 30, …,66, the symbol index of the time slot where the PUSCH is located is l=l ₀ +m=2+6=8, and the reserved time-frequency resource location 131 for placing the type identification information is determined according to the above time-frequency domain mapping formula.

Optionally, the determined reserved time-frequency resource location cannot overlap with the location of the DMRS (Demodulation REFERENCE SIGNAL ) in the PUSCH, and the determined reserved time-frequency resource location cannot overlap with the location of the SRS (Sounding REFERENCE SIGNAL, channel Sounding reference signal) in the PUSCH.

If the terminal is a common device, performing no operation on the reserved resource position in the PUSCH, which accords with the mapping condition; if the terminal is Redcap equipment, a ZC sequence or PN or Walsh sequence for type identification is placed on a reserved resource position which accords with the mapping condition in the PUSCH.

The method can be applied to an application scene of PUSCH transmission in a four-step random access process, specifically referring to FIG. 14A, and can also be applied to an application scene of PUSCH transmission in a two-step random access process, specifically referring to FIG. 14B.

Fig. 14A is a flowchart illustrating a processing method applied to four-step random access according to a fourth exemplary embodiment of the present disclosure.

As shown in fig. 14A, the processing method provided by the present disclosure includes:

in step 1401A, msg 1 is transmitted.

In step 1402A, a preamble ID parsed by the base station, UL Grant authorized by uplink resources of Msg3, and a terminal temporary identifier tc_rnti and a time advance TA are included in Msg2 received by Msg 2.

Step 1403A, transmitting Msg 3, determining that the preamble ID received in Msg 2 is the same as the preamble ID transmitted by Msg 1, and adjusting the PUSCH transmission time according to the TA value carried by Msg 2; msg 3 has PUSCH containing device type identification information located at reserved time-frequency resource locations of PUSCH.

In step 1404A, msg4 is received.

Optionally, the reserved time-frequency resource position of the PUSCH may be determined according to a preset time-frequency domain mapping formula; ZCs or PN or Walsh sequences for device type identification are placed at reserved time-frequency resource locations.

Optionally, the frequency domain position of the device type identification information may be determined in the bandwidth portion occupied by the PUSCH according to a frequency domain mapping formula, and the time domain position of the device type identification information may be determined in the time slot occupied by the PUSCH according to a time domain mapping formula; determining the position of the reserved time-frequency resource in the PUSCH according to the frequency domain position and the time domain position; the reserved time-frequency resource position is not overlapped with the position of the DMRS in the PUSCH, and the reserved time-frequency resource position is not overlapped with the position of the SRS in the PUSCH.

Fig. 14B is a flowchart illustrating a processing method applied to two-step random access according to a fourth exemplary embodiment of the present disclosure.

As shown in fig. 14B, the processing method provided by the present disclosure includes:

In step 1401B, msg a is transmitted, where Msg a has a PUSCH containing device type identification information, where the device type identification information is located at a reserved time-frequency resource location of the PUSCH.

Step 1402B, msg B is received.

Optionally, when the terminal device adds the device type identification information in the identity identifier in the PUSCH, if the terminal device is a common device in the 4-Step random access process, the value of the device type identification information in the PUSCH is the first identity identifier issued by Msg 2; if the terminal equipment is light capacity equipment, the equipment type identification information in the PUSCH is valued as a second identity. The first identity is TC-RNTI issued by Msg 2, the second identity is the sum of TC-RNTI issued by Msg 2 and delta, the value of delta can be a fixed value or a configuration selectable range value of RRC parameters, and the value of delta is required to be larger than 65522, so that the delta is ensured to be distinguished from other normal equipment.

Optionally, after receiving the PUSCH, the network device may perform descrambling with the first identity, if the descrambling is successful, it may determine that the terminal device is a common device, if the descrambling is unsuccessful, a preset offset parameter delta may be added on the basis of the first identity to obtain a second identity of the terminal device, and the PUSCH is descrambled with the second identity, and if the descrambling is successful, it is determined that the terminal device is Redcap devices.

Optionally, the terminal device may generate the scrambling sequence C _init according to:

C _init＝n _RNTI·2 ¹⁶+n _ID

Optionally, if the terminal device is a normal device, n _RNTI is a first identity identifier allocated in Msg 2 sent to the terminal device by the network device, and if the terminal device is Redcap device, n _RNTI is a second identity identifier.

Alternatively, this implementation may be applied in a four-step random access application scenario, with particular reference to fig. 15.

Fig. 15 is a flowchart illustrating a processing method applied to four-step random access according to a fifth exemplary embodiment of the present disclosure.

As shown in fig. 15, the processing method provided by the present disclosure includes:

step 1501, send Msg 1.

In step 1502, msg 2 is received, where Msg 2 includes a preamble ID resolved by a base station, UL Grant authorized by uplink resources of Msg 3, and a terminal temporary identifier tc_rnti and a time advance TA.

Step 1503, transmitting Msg 3, determining that the preamble ID received in Msg 2 is the same as the preamble ID transmitted by Msg 1, adjusting the PUSCH transmission time according to the TA value carried by Msg 2, and performing PUSCH transmission; the Msg 3 is provided with a PUSCH containing an identity, wherein if the terminal equipment is common equipment, the identity in the PUSCH is TC_RNTI, and if the terminal equipment is light capacity equipment, the identity in the PUSCH is second identity; the second identity is the sum of the tc_rnti and delta.

Step 1504, msg4 is received.

If the terminal equipment is common equipment, a scrambling sequence can be generated by using the TC_RNTI, and then the PUSCH is scrambled by using the scrambling sequence, wherein in the implementation mode, the identity in the PUSCH has equipment type identification information corresponding to the common equipment.

If the terminal device is a light device, the scrambling sequence can be generated by using the second identity identifier, and then the PUSCH is scrambled by using the scrambling sequence. The second identity is the sum of the tc_rnti and delta.

Optionally, when the terminal device utilizes a scrambling sequence corresponding to the device type to scramble the PUSCH, if the terminal device is a common device, the terminal device utilizes the first scrambling sequence to scramble the PUSCH; if the terminal device is Redcap devices, the PUSCH is scrambled by using a second scrambling sequence, where the second scrambling sequence is a sum of the first scrambling sequence and a preset offset.

Optionally, after receiving the PUSCH, the network device descrambles the PUSCH by using the first scrambling sequence, and if the descrambling is successful, determining that the terminal device is a common device; if the descrambling fails, the PUSCH is descrambled by using the second scrambling sequence, and if the descrambling is successful, the terminal equipment is Redcap equipment.

In a four-step random access, the terminal device may determine the scrambling sequence based on the following equation:

When the terminal equipment is common equipment: the first scrambling sequence is C _init＝n _RNTI·2 ¹⁶+n _ID;

When the terminal equipment is Redcap equipment: the second scrambling sequence is C _init＝n _RNTI·2 ¹⁶+n _ID +delta.

N _RNTI = TC-RNTI when four steps of random access, issued by Msg 2; the delta is a preset offset, and the value of the delta can be a fixed value or a configuration selectable range value of the RRC parameter, and the value of the delta is required to be larger than the 16-system number FFF2042B.

Upon two-step random access, the terminal device may determine the scrambling sequence C _init based on:

when the terminal equipment is common equipment: the first scrambling sequence is C _init＝n _RNTI·2 ¹⁶+n _RAPID·2 ¹⁰+n _ID;

When the terminal equipment is Redcap equipment: the second scrambling sequence is C _init＝n _RNTI·2 ¹⁶+n _RAPID·2 ¹⁰+n _ID +delta.

Wherein, n _RNTI =ra-RNTI (random access radio network temporary identity, random access radio network temporary identifier) at two steps of random access, RA-rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id, where s_id is an index of a first OFDM symbol of PRACH occasion, the index value range is 0.ltoreq.s_id <14, t_id is a first slot index of PRACH occasion in one system frame, the value range is 0.ltoreq.t_id <80, f_id is PRACH occasion index in frequency domain, the value range is 0.ltoreq.f_id <8, ul_carrier_id is determined by uplink carrier for random access preamble transmission, if preamble is transmitted in SUL carrier, the value is 1, if null carrier is null carrier, the value is 0.

The method can be applied to an application scene of four-step random access, particularly referring to fig. 16A, and can also be applied to an application scene of two-step random access, particularly referring to fig. 16B.

Fig. 16A is a flowchart illustrating a processing method applied to four-step random access according to a sixth exemplary embodiment of the present disclosure.

As shown in fig. 16A, the processing method provided by the present disclosure includes:

in step 1601A, msg 1 is sent.

In step 1602A, msg 2 is received, where Msg 2 includes a preamble ID resolved by a base station, UL Grant authorized by uplink resources of Msg 3, and a terminal temporary identifier tc_rnti and a time advance TA.

Step 1603A, transmitting Msg 3, determining that the preamble ID received in Msg 2 is the same as the preamble ID transmitted by Msg 1, and adjusting the PUSCH transmission time according to the TA value carried by Msg 2, so as to perform PUSCH transmission; the PUSCH is scrambled with a scrambling sequence; if the terminal equipment is common equipment, the scrambling sequence is a first scrambling sequence, and if the terminal equipment is Redcap equipment, the scrambling sequence is a second scrambling sequence.

At step 1604A, msg4 is received.

Optionally, an identity tc_rnti allocated by the network device to the terminal device may be included in Msg 2.

If the terminal device is a normal device, the terminal device utilizes the first scrambling sequence to scramble the PUSCH. In this implementation, the PUSCH transmitted by the terminal device has device type identification information corresponding to the normal device. The first scrambling sequence may be determined specifically based on the following equation:

C _init＝n _RNTI·2 ¹⁶+n _ID；

If the terminal device is Redcap devices, the terminal device may determine the second scrambling sequence based on the following formula, and then scramble the PUSCH with the second scrambling sequence:

C _init＝n _RNTI·2 ¹⁶+n _ID+delta。

Fig. 16B is a flowchart illustrating a processing method applied to two-step random access according to a fifth exemplary embodiment of the present disclosure.

As shown in fig. 16B, the processing method provided by the present disclosure includes:

Step 1601B, transmitting Msg a with PUSCH scrambled with a scrambling sequence therein; if the terminal equipment is common equipment, the scrambling sequence is a first scrambling sequence, and if the terminal equipment is Redcap equipment, the scrambling sequence is a second scrambling sequence.

At step 1602B, msg B is received.

Alternatively, the terminal device may obtain the identity and generate the scrambling sequence using the identity.

C _init＝n _RNTI·2 ¹⁶+n _RAPID·2 ¹⁰+n _ID；

C _init＝n _RNTI·2 ¹⁶+n _RAPID·2 ¹⁰+n _ID+delta。

Fig. 17 is a flowchart illustrating a processing method according to a second exemplary embodiment of the present disclosure.

As shown in fig. 17, in an alternative implementation, before random access, the terminal device may further receive a system message on the network side, where the system message is used to indicate that the device type is reported through a preamble and/or PUSCH.

Step 1701, a system message is received, and the device type is reported through a random access preamble and/or a physical uplink shared channel according to the system message.

Alternatively, the network side may send a system message to the terminal device, which may be, for example, SIB (System Information Block ) or MIB (Master Information Block, master system information block). And indicating the mode of reporting the device type by the terminal device through the system message. The specific mode may include reporting through a preamble, reporting through a PUSCH, and reporting through both the preamble and the PUSCH.

After receiving the system message, the terminal device can determine the mode of reporting the device type according to the system message. For example, bits for indicating the reporting mode of the device type may be added to the system message, and the terminal device determines the reporting mode of the device type by acquiring information in the corresponding bits.

For example, if the bit for indicating the reporting mode of the device type is 00, the terminal device does not need to report the device type when accessing randomly. If the bit for indicating the reporting mode of the device type is 01, reporting the device type through the preamble. If the bit for indicating the reporting mode of the device type is 10, reporting the device type through the PUSCH. And if the bit for indicating the reporting mode of the equipment type is 11, reporting the equipment type through the preamble and the PUSCH at the same time.

Step 1702, if the system message indicates that the device type is reported through the random access preamble, determining or generating the random access preamble when the device type is randomly accessed; if the system message indicates that the device type is reported through the physical uplink shared channel, the physical uplink shared channel is determined or generated when randomly accessing.

Optionally, if the system message indicates that the terminal device reports the device type through the preamble, the terminal device generates or determines the preamble including the device type identification information, and if the system message indicates that the terminal device reports the device type through the PUSCH, the terminal device generates or determines the PUSCH including the device type identification information.

Optionally, when the two steps are randomly accessed, if the system information indicates that the terminal equipment reports the equipment type through the preamble, the terminal equipment reports the equipment type through the preamble which comprises the equipment type identification information in the Msg A; if the system information indicates that the terminal equipment reports the equipment type through the PUSCH, the terminal equipment reports the equipment type through the PUSCH which comprises the equipment type identification information in the Msg A; if the system information indicates that the device type is reported through the preamble and the PUSCH at the same time, the terminal equipment reports the device type through sending the preamble including the device type identification information and the PUSCH including the device type identification information in the Msg A.

Optionally, when the four-step random access is performed, if the system message indicates that the equipment type is reported through the preamble, the terminal equipment reports the equipment type through sending the preamble including the equipment type identification information in the Msg 1; if the system information indicates that the equipment type is reported through the PUSCH, the terminal equipment reports the equipment type through the PUSCH which comprises the equipment type identification information in the Msg 3; if the system information indicates that the device type is reported through the preamble and the PUSCH, the terminal device reports the device type through sending the preamble including the device type identification information in the Msg 1 and through sending the PUSCH including the device type identification information in the Msg 3.

Optionally, if the UE reports the device type identification information through the preamble, the network device may send a device type identification result to the UE. For example, the device type identification result may be sent to the UE through Msg B or Msg 2.

The UE determines whether to report the device type identification information again through the PUSCH based on the type identification result of the network device.

Optionally, a type identification field may be added to DCI (Downlink Control Information ) of Msg 2 or Msg B, and the UE analyzes the bit value of the newly added type identification field in the DCI to determine the device type identification result of the network device. For example, if bit in the type identification field is 1, the characterizing network device determines that the UE is Redcap devices, and if bit in the type identification field is 0, the characterizing network device determines that the UE is a normal type device.

Alternatively, the UE can obtain the device type identification result from the Msg 2, for example, the device type identification result may be obtained from DCI of the Msg 2. For another example, the device type identification result may be obtained from DCI of Msg B.

Optionally, if the device type identification result of the network device is consistent with the device type of the UE, the UE will not report the device type identification information again through PUSCH no matter whether the PUSCH type identification reporting mechanism is enabled in the system message or the higher layer signaling, so as to save PUSCH transmission resources and reduce PUSCH resource collision; and/or if the device type identification result of the network device is inconsistent with the device type of the UE and the PUSCH type identification reporting mechanism is enabled in the system message or the higher layer signaling, the UE reports the device type identification information again through the PUSCH, so as to increase the reliability of the network side for UE type identification.

Optionally, when the UE accesses at random in two steps, if the UE reports the device type through the preamble in the Msg a, the network device may add the device type identification result in the Msg B.

For example, the device type reported by the UE through the preamble of the Msg a is a common type, and the device type identification result of the network side is Redcap which is represented by the information carried in the DCI of the Msg B, and then the UE reports the device type identification information again by retransmitting the Msg a.

The equipment type reported by the UE through the preamble of the Msg A is a common type, and the information carried in the DCI of the Msg B characterizes the equipment type identification result of the network side as the common type, so that the UE does not retransmit the Msg A.

The equipment type reported by the UE through the preamble of the Msg A is Redcap type, the equipment type identification result of the network side is Redcap type, and the UE does not retransmit the Msg A.

The equipment type reported by the UE through the preamble of the Msg A is Redcap types, the information carried in the DCI of the Msg B characterizes that the equipment type identification result of the network side is a common type, and the equipment type identification information is reported again by the UE through the mode of retransmitting the Msg A.

In this implementation, when the network device performs random access configuration, two sets of RO opportunities with different time but in effect can be configured for the UE, so as to meet the requirement that the UE can retransmit Msg a.

Optionally, in the four-step random access, if the UE uses the preamble to report the device type, the network device may add the device type identification result to the Msg 2.

For example, if the device type reported by the UE through the preamble is a common type and the device type identification result of the network side is Redcap types, the UE reports the device type identification information again through the PUSCH of Msg 3;

the equipment type reported by the UE through the preamble is a common type, and the information carried in the DCI characterizes that the equipment type identification result of the network side is the common type, so that the equipment type identification information is not reported again by the UE through the PUSCH of the Msg 3;

The equipment type reported by the UE through the preamble is Redcap types, the information carried in the DCI characterizes that the equipment type identification result of the network side is Redcap types, and the equipment type identification information is not reported again by the UE through the PUSCH of the Msg 3;

The equipment type reported by the UE through the preamble is Redcap types, the information carried in the DCI characterizes that the equipment type identification result of the network side is a common type, and the equipment type identification information is reported again by the UE through the PUSCH of the Msg 3.

Step 1703, a random access preamble, and/or a physical uplink shared channel is transmitted.

Optionally, the terminal device may send a preamble and/or PUSCH to the network device, where the preamble and/or PUSCH includes device type identification information, so that the terminal device can report the device type.

Fig. 18 is a flowchart illustrating a processing method according to a third exemplary embodiment of the present disclosure.

In an alternative implementation, as shown in fig. 18, before random access, the terminal device may also receive a system message on the network side, where the system message is used to indicate whether to allow Redcap device access.

Optionally, the embodiments of fig. 17 and 18 may also be combined, where the system message is used to indicate whether Redcap devices are allowed to access, and also to indicate that the device type is reported over a random access preamble, and/or a physical uplink shared channel.

Step 1801, a system message is received, where the system message includes information about whether to allow access to the lightweight capability device.

Alternatively, the network device may broadcast a system message, which the terminal device may receive.

Optionally, the information whether the Redcap device is allowed to access is contained in MIB (Master Information Block, master system information block), or SIB (System Information Block ), or DCI or RRC signaling that schedules the SIB.

Optionally, the information about whether to allow Redcap devices to access can be carried in other higher-layer signaling, and the terminal device can obtain the information about what capability devices are allowed to access by analyzing the signaling. For example, if the indication bit for indicating whether Redcap devices are allowed to access is 1, then Redcap devices are allowed to access, and/or if the indication bit for indicating whether Redcap devices are allowed to access is 0, then Redcap devices are not allowed to access. For another example, the indication bit is 00, the indication bit is 01, the indication common equipment can be accessed, the indication bit is 10, the indication Redcap equipment can be accessed, the indication bit is 11, and the indication common equipment and Redcap equipment can be accessed.

If the terminal device has the capability of the common device and the capability of Redcap devices, and the indication bit indicates that both the common device and the Redcap devices can be accessed, the terminal device can select an access mode according to the specific scene of the current service, such as a smart meter, and access the terminal device in a redcap device type, such as voice call, and access the terminal device in a common device type.

Alternatively, the network device and the terminal device may agree in advance on which resource in the system message is used to indicate whether to allow Redcap device access, so that after the terminal device receives the system message, the indication information may be obtained from the corresponding signaling to determine whether to allow Redcap device access by the network device.

Step 1802, determining or generating a random access preamble and/or a physical uplink shared channel upon random access when at least one of the following is satisfied: if the terminal equipment is light capacity equipment, and the system message characterization allows the light capacity equipment to be accessed; or if the terminal equipment has the capability of the light-weight capability equipment and the capability of the common equipment, the terminal equipment is accessed to the network by the capability of the common equipment, and the system message representation does not allow the light-weight capability equipment to be accessed and allows the common equipment to be accessed; or if the terminal equipment is normal equipment, and the system message characterization allows the normal equipment to be accessed.

Optionally, after receiving the system message, the terminal device may specifically determine whether to access the network according to the system message when the random access procedure is required.

If the terminal equipment determines that the terminal equipment can access the network, the terminal equipment can determine or generate a preamble and/or determine or generate a PUSCH, and if the terminal equipment determines that the terminal equipment can not access the network according to the system message, the terminal equipment does not determine or generate the preamble and does not determine or generate the PUSCH.

In the first case, if the terminal device is Redcap devices and the system message characterization allows Redcap devices to access, the terminal device determines or generates a preamble and/or PUSCH when accessing randomly.

In the second case, if the terminal device has the capability of Redcap devices and the capability of normal devices, the terminal device accesses the network with the capability of normal devices, and the system message characterizes that Redcap devices are not allowed to access and normal devices are allowed to access. In this case, the terminal device accesses the network in the role of a normal device, and the system message allows the normal device to access, so that the terminal device determines or generates a preamble and/or PUSCH at random access.

In the third case, if the terminal device is a normal device and the system message characterization allows the normal device to access, the terminal device determines or generates a preamble and/or PUSCH when accessing randomly.

In any of the foregoing implementations, the preamble and/or PUSCH of the terminal device includes device type identification information of the terminal device, which may specifically be device type identification information corresponding to a common device.

In the scheme provided by the disclosure, if the system message representation does not allow Redcap devices to access, and the terminal device is Redcap devices, the terminal device will not generate or determine a preamble and/or PUSCH.

Step 1803, a random access preamble is sent and/or if a physical uplink shared channel is sent.

Optionally, if the system message characterizes that the terminal device can access the network, the terminal device may determine or generate a preamble and/or PUSCH and send the preamble and/or PUSCH to the network device; the preamble and/or PUSCH include device type identification information of the terminal device, so that the device type can be reported in this way.

Fig. 19 is a flowchart illustrating a processing method according to a fourth exemplary embodiment of the present disclosure.

The processing method provided by the disclosure can be applied to terminal equipment with the capability of light-weight capability equipment and the capability of common equipment, and the terminal equipment can select which role to access the network based on service requirements when being accessed randomly. The scheme provided in this embodiment may be applied to any of the above embodiments.

As shown in fig. 19, the processing method provided by the present disclosure includes:

Step 1901, determining or generating a random access preamble and/or a physical uplink shared channel, the random access preamble and/or the physical uplink shared channel comprising a device type determined according to traffic requirements.

Optionally, when determining or generating the preamble and/or the PUSCH, the terminal device may determine the device type according to the service requirement. Specifically, which type of access network device is used can be determined according to the service requirement to be processed, and a preamble and/or PUSCH corresponding to the type of the device can be determined or generated. For example, if the terminal device determines to access the network device with the common device type, the device type identification information corresponding to the common device is included in the preamble and/or PUSCH determined or generated by the terminal device. If the terminal device determines that the network device is accessed in the type of Redcap devices, the preamble and/or PUSCH determined or generated by the terminal device includes device type identification information corresponding to Redcap devices.

Optionally, the device type of the terminal device is unchanged in the process of accessing the network once, but the device type of the terminal device can be changed in the process of accessing the network many times based on service requirements. For example, the first access network flow is different from the device type selected in the second access network flow.

Step 1902, a random access preamble is transmitted and/or a physical uplink shared channel is transmitted.

Fig. 20 is a flowchart illustrating a processing method according to a fifth exemplary embodiment of the present disclosure.

As shown in fig. 20, the processing method provided in the present disclosure includes:

Step 2001, receiving a system message, and determining a mode of reporting the device type according to the system message; the method comprises reporting the device type through a random access preamble and/or reporting the device type through a physical uplink shared channel.

Alternatively, the network device may broadcast a system message for indicating in which way the terminal device reports the device type. The system message may be, for example, a SIB (System Information Block ) or a MIB (Master Information Block, master system information block). The manner in which the terminal device reports the device type may be indicated by a system message.

The specific mode can include reporting through a preamble, reporting through a PUSCH, and reporting through both the preamble and the PUSCH.

For example, if the bit for indicating the reporting mode of the device type is 00, the terminal device does not need to report the device type when accessing randomly. If the bit for indicating the reporting mode of the device type is 01, reporting the device type through the preamble. If the bit for indicating the reporting mode of the device type is 10, reporting the device type through the PUSCH. And if the bit for indicating the reporting mode of the equipment type is 11, reporting the equipment type through the preamble and the PUSCH.

Step 2002, reporting the equipment type according to the determined reporting equipment type mode when random access is performed.

If the system information indicates that the device type is reported through the preamble, the terminal device generates or determines the preamble comprising the device type identification information and sends the preamble to the network device when the device is randomly accessed, so that the device type is reported.

If the system information indicates that the device type is reported through the PUSCH, the terminal device generates or determines the PUSCH including the device type identification information when the device type is accessed randomly, and sends the PUSCH to the network device, so that the device type is reported.

If the system information indicates that the device type is reported through the preamble and the PUSCH, the terminal device generates or determines the preamble including the device type identification information and the PUSCH including the device type identification information when in random access, and sends the preamble and the PUSCH to the network device, so that the device type is reported.

Fig. 21 is a flowchart illustrating a processing method according to a sixth exemplary embodiment of the present disclosure.

As shown in fig. 21, the processing method provided by the present disclosure includes:

Step 2101, obtaining preset indication information in a system message, and determining the reporting device type through a random access preamble and/or the reporting device type through a physical uplink shared channel according to the preset indication information.

Optionally, a bit may be preset in the system message, for carrying preset indication information. The network device may issue a system message, and after the terminal device receives the system message, the terminal device may obtain preset indication information from preset bits of the system message, so as to determine, according to the preset indication information, a device type reported by a preamble and/or a PUSCH reporting device type.

Optionally, 2 bits may be set in the system message for carrying the preset indication information. The preset indication information may be, for example, 00, 01, 10, 11, etc.

Step 2102, a random access preamble and/or physical uplink shared channel is determined or generated.

Optionally, if the device type is reported through the preamble according to the preset indication information, the terminal device may generate the preamble including the device type identification information, and if the device type is reported through the PUSCH according to the preset indication information, the terminal device may generate the PUSCH including the device type identification information. If the device type is reported through the preamble and the PUSCH according to the preset indication information, the terminal device may generate the preamble and the PUSCH including the device type identification information.

For example, in the two-step random access, a preamble and a PUSCH may be generated when the Msg a is transmitted, and the generated preamble and/or PUSCH may carry device type identification information. When the four-step random access is performed, a preamble can be generated when the Msg 1 is transmitted, a PUSCH can be generated when the Msg 3 is transmitted, and the generated preamble and/or the PUSCH can carry equipment type identification information.

Step 2103, if the random access preamble is determined or generated, transmitting the random access preamble and/or, if the physical uplink shared channel is determined or generated, transmitting the physical uplink shared channel.

Optionally, if the terminal device determines or generates a preamble including device type identification information, the preamble may be sent to the network device, so as to report the device type. If the terminal device determines or generates a PUSCH including device type identification information, the PUSCH may be transmitted to the network device to report the device type.

The scheme provided by the disclosure can be applied to an application scene of four-step random access and an application scene of two-step random access.

Optionally, at the time of two-step random access, if the random access preamble is determined or generated, the random access preamble is sent through a message a, and/or if the physical uplink shared channel is determined or generated, the physical uplink shared channel is sent through a message a;

optionally, at four-step random access, if the random access preamble is determined or generated, the random access preamble is transmitted through message 1 and/or if the physical uplink shared channel is determined or generated, the physical uplink shared channel is transmitted through message 3.

The processing method provided by the disclosure can be applied to a two-step random access scene, and optionally, the terminal equipment can select a two-step random access mode or a four-step random access mode to access the network according to the configuration information of the network equipment.

The processing method provided by the disclosure can be applied to a two-step random access scene, and specifically can comprise the following steps:

And sending the Msg A, wherein the Msg A has a preamble containing the equipment type identification information.

Receiving Msg B. Optionally, the terminal device may report the device type through a preamble. Specifically, a preamble including device type identification information may be generated during random access, and the preamble may be sent to a network device through Msg a.

The processing method provided by the disclosure can be applied to a two-step random access scene, and specifically can comprise the following steps: :

a physical uplink shared channel is determined or generated, the physical uplink shared channel including device type identification information therein.

And transmitting the Msg A, wherein the Msg A is provided with a PUSCH containing the equipment type identification information.

Receiving Msg B.

The processing method provided by the disclosure can be applied to a two-step random access scene, and specifically comprises the following steps:

The method comprises the step of sending the Msg A, wherein the Msg A comprises a preamble containing device type identification information and a PUSCH containing device type identification information.

Receiving Msg B.

The processing method provided by the disclosure can be applied to a four-step random access scene, and specifically comprises the following steps:

The transmission Msg 1 includes a preamble containing device type identification information in the Msg 1.

And receiving the Msg 2, wherein the Msg 2 comprises a preamble ID analyzed by a base station, an UL Grant authorized by uplink resources of the Msg 3, and a terminal temporary identifier TC_RNTI and a time advance TA. .

And transmitting the Msg3, firstly determining that the preamble ID received in the Msg2 is the same as the preamble ID transmitted by the Msg 1, and then adjusting the transmission time of the PUSCH according to the TA value carried by the Msg2 to perform PUSCH transmission.

Msg4 is received.

And sending Msg 1, wherein the Msg 1 comprises a preamble.

And receiving the Msg2, wherein the Msg2 comprises a preamble ID analyzed by a base station, an UL Grant authorized by uplink resources of the Msg3, and a terminal temporary identifier TC_RNTI and a time advance TA.

And transmitting the Msg 3, firstly determining that the preamble ID received in the Msg2 is the same as the preamble ID transmitted by the Msg1, then adjusting the transmission time of the PUSCH according to the TA value carried by the Msg2, and further transmitting the PUSCH containing the equipment type identification information in the Msg 3.

Msg4 is received.

Alternatively, the terminal device may generate a preamble, and send the preamble through Msg1, where the preamble is generated in a manner similar to the scheme in the prior art. The terminal device sends a random access request to the network device by sending Msg1 to the network device.

Optionally, the terminal device may further generate or determine a PUSCH according to its device type, where the generated PUSCH includes device type identification information. The terminal device transmits the PUSCH including the device type identification information to the network device through Msg 3.

And receiving the Msg 2, wherein the Msg 2 comprises a preamble ID analyzed by a base station, an UL Grant authorized by uplink resources of the Msg 3, and a terminal temporary identifier TC_RNTI and a time advance TA.

And transmitting the Msg 3, determining that the preamble ID received in the Msg2 is the same as the preamble ID transmitted by the Msg1, adjusting the transmission time of the PUSCH according to the TA value carried by the Msg2, and transmitting the PUSCH containing the equipment type identification information in the Msg 3.

Msg4 is received.

Any preamble provided by the present disclosure includes three parts, CP, SEQ, GP. The device type identification information may be set in the GP therein.

The device type identification information may be set in a first resource unit of the GP of the preamble.

The device type identification information may be set in the last resource unit of the GP of the preamble.

The device type identification information may be set in any one of the resource units between the first and last resource units of the preamble.

a first partial random access preamble;

A second part of random access preamble;

The third part randomly accesses the preamble.

The first partial preamble is used for contention-based random access.

The second partial preamble is used for non-contention based random access.

The third partial preamble is used for random access based on other purposes.

Optionally, the number of preambles generated by the terminal device is 64.

Optionally, of the 64 preambles, 0-3, 7-10, 14-17..49-52 preambles function as contention-based random access, 4-6, 11-13, 53-55 preambles function as non-contention-based random access, and 56-63 preambles function as random access for other purposes.

Optionally, each of the 64 preambles corresponds to a respective SSB (Synchronization Signal Block ).

Alternatively, each RO opportunity may be associated with multiple SSBs, with 1 RO opportunity being associated with N SSBs if the parameter SSB-perRACH-OccasionAndCB-PreamblesPerSSB = N (N > 1).

One PRACH configuration period (PRACH configuration period) includes two PRACH slots, and may include 4 RO opportunities in one PRACH slot, where ro#0 occupies the same symbol as ro#1 but occupies a different subcarrier, and ro#2 occupies the same symbol as ro#3 but occupies a different subcarrier. RO#0 occupies a different symbol than RO#2. # is used to characterize the index of RO opportunities.

Alternatively, RO#0 is associated with SSB 0 and SSB 1, RO#1 is associated with SSB 2 and SSB 3, RO#2 is associated with SSB 4 and SSB 5, and RO#3 is associated with SSB 6 and SSB 7.

In this application scenario, which preamble to send may be determined according to the SSB indicated by the network device, for example, which preamble to send may be determined by combining the correspondence between the SSB and the preamble. The RO opportunity for transmitting the preamble may also be selected according to a correspondence between SSBs and RO opportunities.

Optionally, one PRACH configuration period (PRACH configuration period) includes one PRACH slot, in which 8 RO opportunities may be included.

Wherein k takes any value from 0 to 11; the number of RBs available in the portion of bandwidth occupied for PUSCH.

If the reported device type identification information occupies 2 different time domain symbols, the mapping formula for determining the time domain position may further include l' =l ₀ +j; j is a random integer different from m. Or the symbol deviation between j and m is not more than a preset number of symbols, for example, the symbol deviation between two symbols is not more than 3 symbols; if l0=0 and m=4, the reserved second symbol index is j=4+3=7.

The method can be applied to an application scene of PUSCH transmission in a four-step random access process, and can also be applied to an application scene of PUSCH transmission in a two-step random access process.

The disclosure provides a processing method for four-step random access, which specifically comprises the following steps:

And sending Msg 1.

The received Msg2, the Msg2 contains the preamble ID resolved by the base station, the UL Grant authorized by the uplink resource of Msg3, and the terminal temporary identifier tc_rnt I and the time advance TA.

Transmitting Msg 3, determining that the preamble ID received in Msg 2 is the same as the preamble ID transmitted by Msg 1, and adjusting the transmission time of the PUSCH according to the TA value carried by Msg 2; msg 3 has PUSCH containing device type identification information located at reserved time-frequency resource locations of PUSCH.

Msg4 is received.

The processing method applied to the two-step random access provided by the disclosure comprises the following steps:

And transmitting the Msg A, wherein the Msg A has a PUSCH containing device type identification information, and the device type identification information is positioned at a reserved time-frequency resource position of the PUSCH.

Receiving Msg B.

Optionally, when the terminal device adds the device type identification information in the identity identifier in the PUSCH, if the terminal device is a common device in the 4-Step random access process, the value of the device type identification information in the PUSCH is the first identity identifier issued by Msg 2; if the terminal equipment is light capacity equipment, the equipment type identification information in the PUSCH is valued as a second identity. The first identity is TC-RNTI issued by Msg 2, the second identity is the sum of TC-RNTI issued by Msg 2 and delta, the value of delta can be a fixed value or a configuration selectable range value of RRC parameters, and the value of delta is required to be larger than 65522, so that the delta is ensured to be distinguished from other normal users.

Optionally, after receiving the PUSCH, the network device may perform descrambling with the first identity, if the descrambling is successful, it may determine that the terminal device is a common device, if the descrambling is unsuccessful, a preset offset parameter may be added on the basis of the first identity to obtain a second identity of the terminal device, and the PUSCH is descrambled with the second identity, and if the descrambling is successful, it is determined that the terminal device is Redcap devices.

C _init＝n _RNTI·2 ¹⁶+n _ID

Alternatively, this implementation may be applied in a four-step random access application scenario.

The processing method applied to the four-step random access provided by the disclosure comprises the following steps:

And sending Msg 1.

Transmitting Msg 3, determining that the preamble ID received in Msg 2 is the same as the preamble ID transmitted by Msg 1, adjusting the transmission time of the PUSCH according to the TA value carried by Msg 2, and performing PUSCH transmission; the Msg 3 is provided with a PUSCH containing an identity, wherein if the terminal equipment is common equipment, the identity in the PUSCH is TC_RNTI, and if the terminal equipment is light capacity equipment, the identity in the PUSCH is second identity; the second identity is the sum of the tc_rnti and delta.

Msg4 is received.

The method can be applied to an application scene of four-step random access and can also be applied to an application scene of two-step random access.

And sending Msg 1.

Transmitting Msg 3, determining that the preamble ID received in Msg2 is the same as the preamble ID transmitted by Msg 1, adjusting the transmission time of the PUSCH according to the TA value carried by Msg2, and performing PUSCH transmission; the PUSCH is scrambled with a scrambling sequence; if the terminal equipment is common equipment, the scrambling sequence is a first scrambling sequence, and if the terminal equipment is Redcap equipment, the scrambling sequence is a second scrambling sequence.

Msg4 is received.

C _init＝n _RNTI·2 ¹⁶+n _ID

C _init＝n _RNTI·2 ¹⁶+n _ID+delta。

Transmitting Msg A, wherein the Msg A is provided with a PUSCH which is scrambled by a scrambling sequence; if the terminal equipment is common equipment, the scrambling sequence is a first scrambling sequence, and if the terminal equipment is Redcap equipment, the scrambling sequence is a second scrambling sequence.

Receiving Msg B.

C _init＝n _RNTI·2 ¹⁶+n _RAPID·2 ¹⁰+n _ID

C _init＝n _RNTI·2 ¹⁶+n _RAPID·2 ¹⁰+n _ID+delta。

In an alternative implementation, the system message received by the terminal device is also used to indicate whether Redcap devices are allowed access. The system message may be MIB, or SIB, or DCI or RRC signaling of the scheduling SIB contains information whether Redcap devices are allowed to access.

Optionally, the random access preamble and/or the physical uplink shared channel is determined or generated upon random access when at least one of the following is satisfied: if the terminal equipment is light capacity equipment, and the system message characterization allows the light capacity equipment to be accessed; or if the terminal equipment has the capability of the light-weight capability equipment and the capability of the common equipment, the terminal equipment is accessed to the network by the capability of the common equipment, and the system message representation does not allow the light-weight capability equipment to be accessed and allows the common equipment to be accessed; if the terminal equipment is normal equipment, and the system message characterization allows the normal equipment to be accessed.

The terminal device may transmit a random access preamble and/or if a physical uplink shared channel is transmitted.

The processing method provided by the disclosure can also be applied to terminal equipment with the capability of light-weight capability equipment and the capability of common equipment, and the terminal equipment can select which role to access the network based on service requirements when the terminal equipment is accessed randomly. The scheme provided in this embodiment may be applied to any of the above embodiments.

When the terminal equipment is accessed randomly, a random access preamble and/or a physical uplink shared channel is determined or generated, wherein the random access preamble and/or the physical uplink shared channel comprise equipment types determined according to service requirements.

The terminal device may send a random access preamble and/or if a physical uplink shared channel is sent to report the device type.

Fig. 22 is a flowchart of a processing method shown in a seventh exemplary embodiment of the present disclosure.

As shown in fig. 22, the processing method provided by the present disclosure includes:

step 2201, receiving a random access preamble and/or a physical uplink shared channel sent by a terminal device; wherein the random access preamble and/or the physical uplink shared channel comprises device type identification information.

Alternatively, the methods provided by the present disclosure may be performed by a network device. The network device may be, for example, a gNB (the next generation NodeB, base station).

Optionally, when the terminal device is randomly accessed, the device type may be reported through a preamble and/or a PUSCH. Specifically, the preamble and/or PUSCH sent by the terminal device to the network device carries device type identification information.

Optionally, when the terminal device is randomly accessed, the preamble may be determined or generated, and the terminal device may add device type identification information to the preamble according to its device type. For example, a resource bit may be reserved in the preamble, and the terminal device may add device type identification information to the reserved resource bit, for example, if the type of the terminal device is a common device, 1 is added to the reserved resource bit of the preamble, and if the type of the terminal device is Redcap devices, 0 is added to the reserved resource bit of the preamble. Accordingly, after the network device receives the preamble, the device type identification information may be obtained therefrom.

Alternatively, the device type identification information may be set in a GP portion in the preamble, specifically in a designated resource bit of the GP.

Alternatively, the terminal device may determine or generate a PUSCH at random access, where the PUSCH includes device type identification information corresponding to the device type. For example, the terminal device may determine its own device type and add device type identification information corresponding to the device type in the PUSCH. Accordingly, after the network device receives the PUSCH, the device type identification information may be obtained therefrom.

Alternatively, the resource bit may be reserved in the PUSCH, and the terminal device may add the device type identification information to the reserved resource bit of the PUSCH.

C _init＝n _RNTI·2 ¹⁶+n _ID+delta (1)

C _init＝n _RNTI·2 ¹⁶+n _RAPID·2 ¹⁰+n _ID+delta (2)

N _RAPID is the index of the random access preamble of msgA and delta is a preset offset.

Optionally, the preamble determined or generated by the terminal device may include device type identification information, and the PUSCH determined or generated by the terminal device may also include device type identification information.

Alternatively, the information corresponding to the device type may be device type identification information, and the network device may identify the type of the terminal device based on the information.

Step 2202, identifying the type of the terminal device based on the random access preamble and/or the physical uplink shared channel.

Optionally, after receiving the preamble sent by the terminal device, the network device may acquire device type identification information therein, further determine the type of the terminal device, and perform corresponding processing according to the type of the terminal device. If the PUSCH transmitted by the terminal device includes the device type identification information, the network device may acquire the device type identification information after receiving the PUSCH transmitted by the terminal device, further determine the type of the terminal device, and perform corresponding processing according to the type of the terminal device.

Optionally, the processing method provided by the disclosure may be applied in a two-step random access scenario, and optionally, the terminal device may select a two-step random access mode or a four-step random access mode to access the network according to configuration information of the network device.

Fig. 23A is a flowchart illustrating a processing method applied to two-step random access according to a sixth exemplary embodiment of the present disclosure.

As shown in fig. 23A, the processing method provided by the present disclosure includes:

In step 2301A, a preamble in Msg a is received, where the preamble includes device type identification information.

In step 2302A, msg B is sent.

Optionally, when two steps of random access are performed, the terminal device may report the device type through the preamble. Specifically, a preamble including device type identification information may be generated during random access, and the preamble may be sent to a network device through Msg a. In such an application scenario, the network device may receive the preamble in Msg a.

Optionally, after receiving the Msg a, the network device may acquire device type identification information from the GP portion of the preamble, and may further determine the type of the terminal device according to the type identification information.

Fig. 23B is a flowchart illustrating a processing method applied to two-step random access according to a seventh exemplary embodiment of the present disclosure.

As shown in fig. 23B, the processing method provided by the present disclosure includes:

in step 2301B, a PUSCH in MsgA is received, where the PUSCH includes device type identification information.

In step 2302B, msg B is sent.

Optionally, when two steps are randomly accessed, the terminal device may report the device type through PUSCH. Specifically, a PUSCH including device type identification information may be generated at random access, and transmitted to a network device through Msg a.

Optionally, after receiving the Msg a, the network device may acquire device type identification information from the reserved time-frequency resource of the PUSCH, or descramble the PUSCH, and determine the device type identification information of the terminal device according to the descrambling result.

Fig. 23C is a flowchart illustrating a processing method applied to two-step random access according to an eighth exemplary embodiment of the present disclosure.

As shown in fig. 23C, the processing method provided by the present disclosure includes:

In step 2301C, a preamble and a PUSCH in Msg a are received, where the preamble and the PUSCH each include device type identification information.

At step 2302C, msg B is sent.

Optionally, during two-step random access, the terminal device can report the device type through preamble and PUSCH, and in this way, the accuracy of the network device in identifying the type of the terminal device can be improved. Specifically, a preamble and a PUSCH including device type identification information may be generated during random access, and the preamble and the PUSCH may be sent to a network device through Msg a. In this implementation, both preamble and PUSCH include device type identification information.

Optionally, after the network device receives the preamble and the PUSCH in the Msg a, the type identification information may be obtained from the preamble and the PUSCH, and by obtaining the type identification information from two positions, accuracy of type identification of the terminal device may be improved.

Optionally, after receiving the message a, the network device may also send a message B to the terminal device, in response to the message a, and establish a connection with the terminal device.

Fig. 24A is a flowchart illustrating a processing method applied to four-step random access according to a seventh exemplary embodiment of the present disclosure.

As shown in fig. 24A, the processing method provided by the present disclosure includes:

In step 2401A, a preamble in Msg 1 is received, where the preamble includes device type identification information.

Step 2402A, msg 2 is sent.

Step 2403A, receiving Msg 3.

Step 2404A, msg4 is sent.

Optionally, after the network device receives the preamble, the device type identification information may be obtained from the GP of the preamble.

Fig. 24B is a flowchart illustrating a processing method applied to four-step random access according to an eighth exemplary embodiment of the present disclosure.

As shown in fig. 24B, the processing method provided by the present disclosure includes:

In step 2401B, a preamble in Msg 1 is received.

Step 2402B, send Msg 2.

In step 2403B, PUSCH in Msg 3 is received, and the PUSCH includes device type identification information.

Step 2404B, msg4 is sent.

Optionally, the terminal device may generate or determine the PUSCH according to the device type, so that the PUSCH carries the device type identification information, and send the PUSCH to the network device through Msg 3, thereby reporting the device type to the network device.

Optionally, after the network device receives the PUSCH, the device type identification information may be obtained from the reserved time-frequency resource location of the PUSCH; or acquiring equipment type identification information from the identity in the PUSCH; or descrambling the object PUSCH, and determining the equipment type identification information according to the descrambling result.

Fig. 24C is a flowchart illustrating a processing method applied to four-step random access according to a ninth exemplary embodiment of the present disclosure.

As shown in fig. 24C, the processing method provided by the present disclosure includes:

In step 2401C, a preamble in Msg 1 is received, where the preamble includes device type identification information.

Step 2402C, send Msg 2.

In step 2403C, PUSCH in Msg 3 is received, and the PUSCH includes device type identification information.

Step 2404C, send Msg4.

Optionally, after receiving the Msg1, the network device may acquire the preamble from the Msg1, and then acquire the device type identification information from the GP of the preamble.

Optionally, the terminal device may further generate or determine a PUSCH according to the device type, so that the PUSCH carries device type identification information, and send the PUSCH to the network device through the message 3, thereby reporting the device type to the network device.

Optionally, after receiving Msg 3, the network device may acquire a PUSCH therein, and may acquire device type identification information from a reserved time-frequency resource location of the PUSCH; or acquiring equipment type identification information from the identity in the PUSCH; or descrambling the object PUSCH, and determining the equipment type identification information according to the descrambling result.

By acquiring the device type identification information from the preamble and the PUSCH, the accuracy of device type identification can be further improved.

In any of the above implementations, when the device type identification information is obtained from the preamble, the device type identification information may be specifically obtained from a specified resource unit of the GP of the preamble.

Alternatively, the device type identification information may be obtained from the first resource unit of the GP of the preamble.

Alternatively, the device type identification information may be obtained from the last resource unit of the GP of the preamble.

Alternatively, the device type identification information may be obtained from any one of the resource units between the first resource unit and the last resource unit of the preamble.

Optionally, in any of the foregoing embodiments, when the device type identification information is obtained from the reserved time-frequency resource location of the PUSCH, the reserved time-frequency resource location of the physical uplink shared channel may be determined according to a preset mapping formula, and then the device type identification information may be obtained from the reserved time-frequency resource location.

Optionally, the network device may determine the frequency domain location of the device type identification information in the bandwidth portion occupied by the PUSCH according to a frequency domain mapping formula, and determine the time domain location of the device type identification information in the time slot occupied by the PUSCH according to a time domain mapping formula, and optionally may determine the frequency domain location of the device type identification information in the bandwidth portion occupied by the PUSCH based on the following formula:

Optionally, when determining the equipment type identification information in the PUSCH according to the identity of the terminal equipment, the physical uplink shared channel may be descrambled by using the first identity sent to the terminal equipment, and if the descrambling is successful, it is determined that the terminal equipment is common equipment; descrambling the physical uplink shared channel by using the second identity, and if the descrambling is successful, determining that the terminal equipment is light capacity equipment; the second identity is equal to the sum of the first identity and a preset offset parameter.

This implementation can be applied in the application scenario of four-step random access.

Optionally, the network device issues a first identity identifier to the terminal device by using the Msg 2, and if the terminal device is a common device, the value of the device type identification information in the PUSCH is the first identity identifier issued by the Msg 2; if the terminal equipment is light capacity equipment, the equipment type identification information in the PUSCH is valued as a second identity. The first identity is TC-RNTI issued by Msg 2, the second identity is TC-RNTI+delta issued by Msg 2, the value of delta can be a fixed value or a configuration selectable range value of RRC parameters, and the value of delta is required to be larger than 65522, so that the delta is ensured to be distinguished from other normal users.

Optionally, the network device may generate scrambling sequence C _init according to:

C _init＝n _RNTI·2 ¹⁶+n _ID

Alternatively, this implementation can be applied in the application scenario of four-step random access

Optionally, descrambling the physical uplink shared channel, and determining that the terminal device is a common device if the physical uplink shared channel is successfully descrambled by using the first scrambling sequence when determining the device type identification information according to the descrambling result; if the physical uplink shared channel is successfully descrambled by using the second scrambling sequence, determining that the terminal equipment is light capacity equipment; the second scrambling sequence is the sum of the first scrambling sequence and a preset offset.

Upon four-step random access, the network may determine the scrambling sequence based on the following:

The first scrambling sequence is C _init＝n _RNTI·2 ¹⁶+n _ID;

The second scrambling sequence is C _init＝n _RNTI·2 ¹⁶+n _ID +delta.

N _RNTI = TC-RNTI when four steps of random access is the identifier issued by Msg2 to the terminal device; the delta is a preset offset, and the value of the delta can be a fixed value or a configuration selectable range value of the RRC parameter, and the value of the delta is required to be larger than the 16-system number FFF2042B.

This approach can be applied in a four-step random access application scenario.

After receiving the PUSCH, the network equipment descrambles the PUSCH by using the generated first scrambling sequence, and if the descrambling is successful, the network equipment determines that the terminal equipment is common equipment; if the descrambling fails, a second scrambling sequence is generated, then the PUSCH is descrambled by using the second scrambling sequence, and if the descrambling is successful, the terminal equipment is Redcap equipment.

Optionally, before the terminal device random access, the network device may further issue a system message to the terminal device, where the system message is used to instruct the terminal device to report the device type through the random access preamble and/or the physical uplink shared channel; and/or a system message to indicate whether to allow access to the lightweight capability device.

In one implementation, the system message is used to instruct the terminal device in what way to report the device type.

In one implementation, a system message is used to indicate whether lightweight capability devices are allowed access.

In one implementation, the system message is used to instruct the terminal device in what way to report the device type, and also to instruct whether to allow the lightweight capability device to access.

Alternatively, the network side may send a system message to the terminal device, which may be, for example, SIB (System Information Block ) or MIB (Master Information Block, master system information block). And indicating the mode of reporting the device type by the terminal device through the system message.

The specific mode may include reporting through a preamble, reporting through a PUSCH, and reporting through both the preamble and the PUSCH.

Optionally, if the system message indicates that the terminal device reports the device type through the preamble, the terminal device needs to generate or determine the preamble including the device type identification information, and if the system message indicates that the terminal device reports the device type through the PUSCH, the terminal device needs to generate or determine the PUSCH including the device type identification information.

Optionally, when the two steps are randomly accessed, if the system information indicates that the terminal equipment reports the equipment type through the preamble, the terminal equipment reports the equipment type through the preamble which comprises the equipment type information in the Msg A; if the system information indicates that the terminal equipment reports the equipment type through the PUSCH, the terminal equipment reports the equipment type through the PUSCH which comprises the equipment type identification information in the Msg A. And when the two steps of random access are performed, if the system information indicates the terminal equipment to report the equipment type through the preamble and the PUSCH at the same time, the terminal equipment adds equipment type identification information into the preamble and the PUSCH of the Msg A to report the equipment type.

Optionally, when the four-step random access is performed, if the system message indicates that the terminal device reports the device type through the preamble, the terminal device may report the device type by sending the preamble including the device type identification information in the Msg 1. And when the four-step random access is performed, if the system information indicates that the terminal equipment reports the equipment type through the PUSCH, the terminal equipment can report the equipment type through the PUSCH which comprises the equipment type identification information in the Msg 3. When the four-step random access is performed, if the system information indicates that the terminal equipment reports the equipment type through the preamble and the PUSCH, the terminal equipment can report the equipment type by sending the preamble including the equipment type identification information in the Msg 1 and by sending the PUSCH including the equipment type identification information in the Msg 3.

Optionally, the information about whether to allow Redcap devices to access can be carried in other higher-layer signaling, and the terminal device can obtain the information about what capability devices are allowed to access by analyzing the signaling. For example, if the indication bit for indicating whether to allow Redcap devices to access is 1, the token allows Redcap devices to access, and/or if the indication bit for indicating whether to allow Redcap devices to access is 0, the token does not allow Redcap devices to access, and further for example, indicates that no type of device can access, indicates that the bit is 01, indicates that normal devices can access, indicates that the bit is 10, indicates that Redcap devices can access, indicates that the bit is 11, indicates that normal devices and Redcap devices can both access.

Optionally, a type identification field may be added to DCI (Downlink Control Information ) of Msg 2 or Msg B, and the UE analyzes the bit value of the newly added type identification field in the DCI to determine the device type identification result of the network device. For example, if bit in the type identification field is 1, the characterizing network device determines that the UE is Redcap devices, and/or if bit in the type identification field is 0, the characterizing network device determines that the UE is a normal type device.

Alternatively, the UE can obtain the device type identification result from the Msg2, for example, the device type identification result may be obtained from DCI of the Msg 2. For another example, the identification result of the category type may be obtained from DCI of Msg B

Optionally, if the device type identification result of the network device is consistent with the device type of the UE, the UE will not report the device type identification information again through PUSCH no matter whether the PUSCH type identification reporting mechanism is enabled in the system message or the higher layer signaling, so as to save PUSCH transmission resources and reduce PUSCH resource collision; if the device type identification result of the network device is inconsistent with the device type of the UE and a PUSCH type identification reporting mechanism is enabled in the system message or the high-layer signaling, the UE reports the device type identification information again through the PUSCH, so that the reliability of the network side for UE type identification is increased.

As shown in fig. 25, the communication apparatus provided in this embodiment includes:

A memory 2501;

a processor 2502; and

Computer program.

Optionally, the computer program is stored in the memory 2501 and configured to be executed by the processor 2502 to implement the processing methods illustrated in the embodiments as described above.

The present embodiment also provides a computer-readable storage medium, having stored thereon a computer program,

The computer program is executed by a processor to implement the processing method shown in the embodiment as any one of the above.

The present embodiment also provides a computer program product comprising a computer program which, when executed by a processor, implements the processing method shown in any of the embodiments described above.

The embodiment of the application also provides a communication device, which comprises a memory and a processor, wherein the memory stores a processing program, and the processing program is executed by the processor to realize the steps of the processing method in any embodiment.

The embodiment of the application also provides a computer readable storage medium, and a processing program is stored on the computer readable storage medium, and when the processing program is executed by a processor, the steps of the processing method in any embodiment are implemented.

The embodiments of the communication device and the computer readable storage medium provided in the embodiments of the present application may include all the technical features of any one of the embodiments of the processing method, and the expansion and explanation contents of the description are substantially the same as those of each embodiment of the method, which are not repeated herein.

Embodiments of the present application also provide a computer program product comprising computer program code which, when run on a computer, causes the computer to perform the method as in the various possible embodiments described above.

The embodiment of the application also provides a chip, which comprises a memory and a processor, wherein the memory is used for storing a computer program, and the processor is used for calling and running the computer program from the memory, so that the device provided with the chip executes the method in the various possible implementation manners.

It can be understood that the above scenario is merely an example, and does not constitute a limitation on the application scenario of the technical solution provided by the embodiment of the present application, and the technical solution of the present application may also be applied to other scenarios. For example, as one of ordinary skill in the art can know, with the evolution of the system architecture and the appearance of new service scenarios, the technical solution provided by the embodiment of the present application is also applicable to similar technical problems.

The foregoing embodiment numbers of the present application are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.

The steps in the method of the embodiment of the application can be sequentially adjusted, combined and deleted according to actual needs.

The units in the device of the embodiment of the application can be combined, divided and deleted according to actual needs.

In the present application, the same or similar term concept, technical solution and/or application scenario description will be generally described in detail only when first appearing and then repeatedly appearing, and for brevity, the description will not be repeated generally, and in understanding the present application technical solution and the like, reference may be made to the previous related detailed description thereof for the same or similar term concept, technical solution and/or application scenario description and the like which are not described in detail later.

In the present application, the descriptions of the embodiments are emphasized, and the details or descriptions of the other embodiments may be referred to.

The technical features of the technical scheme of the application can be arbitrarily combined, and all possible combinations of the technical features in the above embodiment are not described for the sake of brevity, however, as long as there is no contradiction between the combinations of the technical features, the application shall be considered as the scope of the description of the application.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) as above, comprising instructions for causing a terminal device (which may be a mobile phone, a computer, a server, a controlled terminal, or a network device, etc.) to perform the method of each embodiment of the present application.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line), or wireless (e.g., infrared, wireless, microwave, etc.). Computer readable storage media can be any available media that can be accessed by a computer or data storage devices, such as servers, data centers, etc., that contain an integration of one or more available media. Usable media may be magnetic media (e.g., floppy disks, storage disks, magnetic tape), optical media (e.g., DVD), or semiconductor media (e.g., solid state storage disk Solid STATE DISK (SSD)), etc.

The foregoing description is only of the preferred embodiments of the present application, and is not intended to limit the scope of the application, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.

Claims

A processing method, characterized by being applied to a terminal device, the method comprising the steps of:

S1: determining or generating a random access preamble and/or a physical uplink shared channel; wherein the determined or generated random access preamble code comprises equipment type identification information; the physical uplink shared channel determined or generated comprises equipment type identification information;

S2: transmitting the random access preamble and/or if transmitting the physical uplink shared channel.
The method according to claim 1, characterized in that the method comprises at least one of the following:

In the two-step random access, the step S2 includes: transmitting the random access preamble through a message a if the random access preamble is determined or generated, and/or transmitting the physical uplink shared channel through a message a if the physical uplink shared channel is determined or generated;

In the four-step random access, the step S2 includes: the random access preamble is transmitted through message 1 if the random access preamble is determined or generated and/or the physical uplink shared channel is transmitted through message 3 if the physical uplink shared channel is determined or generated.
The method according to claim 1, characterized in that the method comprises:

The device type identification information is used to indicate that the terminal device is a lightweight capability device or a general device.
A method according to claim 3, characterized in that the method comprises at least one of the following:

If the determined or generated random access preamble code comprises equipment type identification information, the equipment type identification information is positioned in a guard interval in the random access preamble code;

If the determined or generated physical uplink shared channel includes device type identification information, then: the equipment type identification information is positioned in the reserved time-frequency resource of the physical uplink shared channel, and/or the equipment type identification information is positioned in the identity of the terminal equipment, and/or the equipment type identification information is contained in a scrambling sequence for scrambling the physical uplink shared channel;

Upon four-step random access, the determining or generating a physical uplink shared channel includes at least one of: adding the equipment type identification information in a reserved time-frequency resource position of the physical uplink shared channel, adding the equipment type identification information in an identity mark in the physical uplink shared channel, and scrambling the physical uplink shared channel by using a scrambling sequence corresponding to the equipment type identification information;

Upon two-step random access, the determining or generating a physical uplink shared channel includes at least one of: and adding the equipment type identification information in the reserved time-frequency resource position of the physical uplink shared channel, and scrambling the physical uplink shared channel by using a scrambling sequence corresponding to the equipment type identification information.
The method of claim 4, wherein the method comprises at least one of:

The equipment type identification information is located in a designated resource unit of the guard interval;

The adding the device type identification information in the reserved time-frequency resource position of the physical uplink shared channel comprises the following steps: determining the reserved time-frequency resource position of the physical uplink shared channel according to a preset mapping formula; adding the equipment type identification information at the reserved time-frequency resource position;

The step of adding the equipment type identification information to the identity in the physical uplink shared channel comprises the following steps of; if the terminal equipment is common equipment, the received first identity is added in a physical uplink shared channel, or if the terminal equipment is light capacity equipment, a preset offset parameter is added on the basis of the received first identity to obtain a second identity, and the second identity is added in the physical uplink shared channel;

The scrambling the physical uplink shared channel with a scrambling sequence corresponding to the device type, comprising: and if the terminal equipment is common equipment, scrambling the physical uplink shared channel by using a preset scrambling sequence, or if the terminal equipment is light capacity equipment, scrambling the physical uplink shared channel according to the preset scrambling sequence and a preset offset.
The method of claim 5, wherein the predetermined mapping formula comprises a frequency domain mapping formula and a time domain mapping formula; the determining the reserved time-frequency resource position of the physical uplink shared channel according to a preset mapping formula includes:

determining a frequency domain position of the equipment type identification information in a bandwidth part occupied by the physical uplink shared channel according to the frequency domain mapping formula, and determining a time domain position of the equipment type identification information in a time slot occupied by the physical uplink shared channel according to the time domain mapping formula;

And determining the reserved time-frequency resource position in the physical uplink shared channel according to the frequency domain position and the time domain position.
The method according to any one of claims 1 to 6, further comprising at least one of:

Receiving a system message, determining that the equipment type is reported through a random access preamble and/or a physical uplink shared channel according to the system message, wherein the step S1 comprises the following steps: if the system information indicates that the equipment type is reported through a random access preamble, determining or generating the random access preamble when the equipment type is accessed randomly, or if the system information indicates that the equipment type is reported through a physical uplink shared channel, determining or generating the physical uplink shared channel when the equipment type is accessed randomly;

Receiving a system message, wherein the system message comprises information about whether the light capacity equipment is allowed to be accessed, and executing the step S1 when at least one of the following is met: if the terminal equipment is light capacity equipment and the system message representation allows the light capacity equipment to be accessed, or if the terminal equipment has the capacity of the light capacity equipment and the capacity of common equipment, the terminal equipment is accessed to a network by the common equipment capacity, the system message representation does not allow the light capacity equipment to be accessed and allows the common equipment to be accessed, and if the terminal equipment is the common equipment, the system message representation allows the common equipment to be accessed;

If the terminal device has the capability of a light-weight capability device and the capability of a common device, the method further comprises: the type of the light capacity device or the type of the common device is determined to access the network according to the service requirement.
A processing method, characterized by being applied to a terminal device, the method comprising the steps of:

S1: receiving a system message, and determining a mode of reporting the equipment type according to the system message; reporting the equipment type and/or the equipment type through a random access preamble and/or a physical uplink shared channel;

s2: and reporting the equipment type according to the determined mode of reporting the equipment type during random access.
The method of claim 8, wherein the method comprises at least one of:

The step S1 comprises the following steps: acquiring preset indication information in the system message, and determining to report the equipment type through a random access preamble and/or report the equipment type through a physical uplink shared channel according to the preset indication information;

The step S2 comprises the following steps: s21: determining or generating a random access preamble and/or a physical uplink shared channel; s22: the random access preamble is transmitted if the random access preamble is determined or generated, and/or the physical uplink shared channel is transmitted if the physical uplink shared channel is determined or generated.
The method according to claim 9, characterized in that the method comprises at least one of the following:

At the time of two-step random access, the step S22 includes: transmitting the random access preamble through a message a if the random access preamble is determined or generated, and/or transmitting the physical uplink shared channel through a message a if the physical uplink shared channel is determined or generated;

In the four-step random access, the step S22 includes: if the random access preamble is determined or generated, the random access preamble is transmitted through message 1 and/or if the physical uplink shared channel is determined or generated, the physical uplink shared channel is transmitted through message 3.
The method according to claim 9, characterized in that the method comprises at least one of the following:

The random access preamble code determined or generated comprises equipment type identification information;

the physical uplink shared channel determined or generated comprises equipment type identification information;

The device type is used for indicating that the terminal device is a light capacity device or a common device
The method of claim 11, wherein the method comprises at least one of:

If the determined or generated random access preamble code comprises equipment type identification information, the equipment type identification information is positioned in a guard interval in the random access preamble code;

If the determined or generated physical uplink shared channel includes device type identification information, then: the equipment type identification information is positioned in reserved time-frequency resources of the physical uplink shared channel; and/or the equipment type identification information is located in the identity of the terminal equipment; and/or the device type identification information is contained in a scrambling sequence that scrambles the physical uplink shared channel;

Upon four-step random access, the determining or generating a physical uplink shared channel includes at least one of: adding the device type identification information in a reserved time-frequency resource location of the physical uplink shared channel; adding the equipment type identification information into the identity mark in the physical uplink shared channel; scrambling the physical uplink shared channel with a scrambling sequence corresponding to the device type;

Upon two-step random access, the determining or generating a physical uplink shared channel includes at least one of: adding the device type identification information in a reserved time-frequency resource location of the physical uplink shared channel; the physical uplink shared channel is scrambled with a scrambling sequence corresponding to the device type.
The method of claim 11, wherein the method comprises at least one of:

The adding the device type identification information in the reserved time-frequency resource position of the physical uplink shared channel comprises the following steps: determining the reserved time-frequency resource position of the physical uplink shared channel according to a preset mapping formula; adding the equipment type identification information at the reserved time-frequency resource position;

The step of adding the equipment type identification information to the identity in the physical uplink shared channel comprises the following steps of; if the terminal equipment is common equipment, adding the received first identity identification into a physical uplink shared channel; if the terminal equipment is light capacity equipment, adding a preset offset parameter on the basis of the received first identity to obtain a second identity, and adding the second identity in the physical uplink shared channel;

The scrambling the physical uplink shared channel with a scrambling sequence corresponding to the device type, comprising: if the terminal equipment is common equipment, scrambling the physical uplink shared channel by using a preset scrambling sequence; and if the terminal equipment is common equipment, scrambling the physical uplink shared channel according to the preset scrambling sequence and the preset offset.
The method of claim 12, wherein the predetermined mapping formula comprises a frequency domain mapping formula and a time domain mapping formula; the determining the reserved time-frequency resource position of the physical uplink shared channel according to a preset mapping formula includes:

Determining the frequency domain position of the equipment type identification information in the bandwidth part occupied by the physical uplink shared channel according to the frequency domain mapping formula, and determining the time domain position of the equipment type identification information in the time slot occupied by the physical uplink shared channel according to the time domain mapping formula;

And determining the reserved time-frequency resource position in the physical uplink shared channel according to the frequency domain position and the time domain position.
The method according to any one of claims 8-14, characterized in that the method comprises at least one of the following:

The system message also comprises information about whether to allow the light capacity equipment to be accessed;

The step S1 is performed when at least one of the following is satisfied:

If the terminal equipment is light capacity equipment and the system message characterization allows the light capacity equipment to be accessed;

If the terminal equipment has the capability of the light-weight capability equipment and the capability of the common equipment, the terminal equipment is accessed to a network by the capability of the common equipment, and the system message characterizes that the light-weight capability equipment is not allowed to be accessed and the common equipment is allowed to be accessed;

if the terminal equipment is common equipment and the system message characterization allows the access of the common equipment;

If the terminal device has the capability of a light-weight capability device and the capability of a common device, the method further comprises:

Determining the type of light capacity equipment or the type of common equipment to access the network according to the service requirement;

the step S2 includes:

Determining or generating a random access preamble and/or a physical uplink shared channel; the random access preamble and/or physical uplink shared channel comprises a device type determined according to traffic requirements

The random access preamble is transmitted if the random access preamble is determined or generated and/or the physical uplink shared channel is transmitted if the physical uplink shared channel is determined or generated.
A method of processing, for application to a network device, the method comprising:

S3: receiving a random access preamble and/or a physical uplink shared channel sent by terminal equipment; wherein the random access preamble and/or the physical uplink shared channel comprises equipment type identification information;

S4: and identifying the type of the terminal equipment according to the random access preamble and/or the physical uplink shared channel.
The method of claim 16, wherein the method comprises at least one of:

In the two-step random access, the step S3 includes: receiving the random access preamble in message a, and/or a physical uplink shared channel;

in the four-step random access, the step S3 includes: receiving the random access preamble in message1 and/or receiving the physical uplink shared channel in message 3;

The device type identification information is used to indicate that the terminal device is a lightweight capability device or a general device.
The method of claim 16, wherein the method comprises at least one of:

If the random access preamble includes the equipment type identification information, S4 includes: acquiring the equipment type identification information from the guard interval of the random access preamble;

If the physical uplink shared channel includes equipment type identification information, then:

in the four-step random access, the step S4 includes at least one of the following:

acquiring the equipment type identification information from the reserved time-frequency resource position of the physical uplink shared channel;

Determining equipment type identification information in the physical uplink shared channel according to the identity of the terminal equipment;

descrambling the physical uplink shared channel, and determining the equipment type identification information according to a descrambling result;

At the time of two-step random access, the step S4 includes at least one of the following:

acquiring the equipment type identification information from the reserved time-frequency resource position of the physical uplink shared channel;

And descrambling the physical uplink shared channel, and determining the equipment type identification information according to a descrambling result.
The method of claim 16, wherein the method comprises at least one of:

The acquiring the equipment type identification information from the guard interval of the random access preamble includes: acquiring the equipment type identification information from a designated resource unit of a guard interval of the random access preamble;

The obtaining the device type identification information from the reserved time-frequency resource position of the physical uplink shared channel comprises the following steps: determining the reserved time-frequency resource position of the physical uplink shared channel according to a preset mapping formula; acquiring the equipment type identification information from the reserved time-frequency resource position;

The determining the equipment type identification information in the physical uplink shared channel according to the identity of the terminal equipment comprises the following steps: descrambling the physical uplink shared channel by using a first identity identifier sent to the terminal equipment, and if the descrambling is successful, determining that the terminal equipment is common equipment; descrambling the physical uplink shared channel by using a second identity, and if the descrambling is successful, determining that the terminal equipment is light capacity equipment; the second identity is equal to the sum of the first identity and a preset offset parameter;

The descrambling is performed on the physical uplink shared channel, and the equipment type identification information is determined according to the descrambling result, including: if the physical uplink shared channel is successfully descrambled by using a first scrambling sequence, determining that the terminal equipment is common equipment; if the physical uplink shared channel is successfully descrambled by using a second scrambling sequence, determining that the terminal equipment is light capacity equipment; wherein the second scrambling sequence is the sum of the first scrambling sequence and a preset offset.
The method of claim 18, wherein the predetermined mapping formula comprises a frequency domain mapping formula and a time domain mapping formula;

the determining the reserved time-frequency resource position of the physical uplink shared channel according to a preset mapping formula includes:

Determining a frequency domain position in a bandwidth part occupied by the physical uplink shared channel according to the frequency domain mapping formula, and determining a time domain position in a time slot occupied by the physical uplink shared channel according to the time domain mapping formula;

And determining the reserved time-frequency resource position in the physical uplink shared channel according to the frequency domain position and the time domain position.
The method according to any one of claims 16-20, further comprising:

Issuing a system message to the terminal equipment, wherein the system message is used for indicating the terminal equipment to report the equipment type through a random access preamble and/or a physical uplink shared channel; and/or the system message is used to indicate whether to allow access to the lightweight capability device.
A communication device, comprising:

A memory;

A processor;

Wherein the memory has stored therein a computer program which, when executed by the processor, implements the method of any of claims 1 to 20.
A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the method according to any of claims 1 to 20.