CN113423145A

CN113423145A - Processing method, communication device, and storage medium

Info

Publication number: CN113423145A
Application number: CN202110970558.2A
Authority: CN
Inventors: 朱荣昌; 黄钧蔚
Original assignee: Shenzhen Transsion Holdings Co Ltd
Current assignee: Shenzhen Transsion Holdings Co Ltd
Priority date: 2021-08-23
Filing date: 2021-08-23
Publication date: 2021-09-21
Also published as: CN117941451A; WO2023024613A1

Abstract

The application provides a processing method, a communication device and a storage medium, wherein the processing method comprises the following steps: determining or generating a random access preamble when randomly accessing; the random access preamble comprises a device type identifier; and sending a random access lead code to report the equipment type identification. According to the processing method, the communication equipment and the storage medium, the network equipment is made to know the type of the terminal equipment by sending the random access lead code comprising the equipment type identification, and the mode does not need to reserve the random access lead code or increase the system overhead additionally, so that the purpose of distinguishing the type of the terminal equipment can be achieved with low communication cost.

Description

Processing method, communication device, and storage medium

Technical Field

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

Background

With the development of 5G technology, more and more terminal devices can access to the network, and in some implementations, a Redcap type (Reduced Capability) device can also access to the network.

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

In the course of conceiving and implementing the present application, the inventors found that at least the following problems existed: the number of preambles carried in one RO opportunity is limited, which may result in less preambles available to common devices if a part of the preambles is reserved for a Redcap type device, and/or may increase the overhead of the system if different types of devices use different schemes of RO opportunities.

The foregoing description is provided for general background information and is not admitted to be prior art.

Disclosure of Invention

The present application provides a processing method, a communication device, and a storage medium, so as to solve the above technical problem of increasing the overhead of the system or causing the available preamble of the common device to become less.

A first aspect of the present application provides a processing method, applied to a terminal device, the method including:

determining or generating a random access preamble when randomly accessing; optionally, the random access preamble includes a device type identifier;

and sending the random access lead code to report the equipment type identification.

A second aspect of the present application provides a processing method, applied to a terminal device, the method including:

determining a sending strategy of the random access lead code according to the network side scheduling information and the type of the terminal equipment;

and sending the random access lead code according to the sending strategy to report the equipment type identification.

A third aspect of the present application provides a processing method applied to a network device, where the method includes:

receiving a random access lead code sent by terminal equipment; optionally, the random access preamble includes a device type identifier;

and acquiring the equipment type identifier in the random access lead code, and determining the type of the terminal equipment according to the equipment type identifier.

A fourth aspect of the present application provides a processing apparatus, which is applied to a terminal device, and the apparatus includes:

a code determining unit, configured to determine or generate a random access preamble when performing random access; optionally, the random access preamble includes a device type identifier;

a sending unit, configured to send the random access preamble to report the device type identifier.

A fifth aspect of the present application is to provide a processing apparatus, applied to a terminal device, the apparatus including:

a strategy determining unit, configured to determine a sending strategy of the random access preamble according to the network side scheduling information and the type of the terminal device;

and the sending unit is used for sending the random access lead code according to the sending strategy and reporting the equipment type identifier.

A sixth aspect of the present application provides a processing apparatus applied to a network device, the apparatus including:

a receiving unit, configured to receive a random access preamble sent by a terminal device; optionally, the random access preamble includes a device type identifier;

an obtaining unit, configured to obtain a device type identifier in the random access preamble;

and the type determining unit is used for determining the type of the terminal equipment according to the equipment type identifier.

A seventh aspect of the present application is to provide a communication apparatus comprising:

a memory;

a processor;

wherein the memory has stored therein a computer program which, when executed by the processor, implements any of the above-described processing methods.

An eighth aspect of the present application is to provide a computer-readable storage medium having a computer program stored thereon, the computer program, when executed by a processor, implementing any one of the processing methods described above.

A ninth aspect of the present application provides a computer program product comprising a computer program which, when executed by a processor, implements any of the processing methods described above.

The processing method, the communication device and the storage medium provided by the application determine or generate the random access lead code when the random access is performed; optionally, the random access preamble includes a device type identifier; and sending a random access lead code to report the equipment type identification. According to the processing method, the communication equipment and the storage medium, the network equipment is made to know the type of the terminal equipment by sending the random access lead code comprising the equipment type identification, and the mode does not need to reserve the random access lead code or increase the system overhead additionally, so that the purpose of distinguishing the type of the terminal equipment can be achieved with low communication cost.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present 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 needed to be used in the description of the embodiments will be briefly described below, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.

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

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

fig. 3 is a diagram illustrating a four-step random access procedure in accordance with an exemplary embodiment;

fig. 4 is a diagram illustrating a two-step random access procedure in an exemplary embodiment;

FIG. 5 is a schematic flow chart diagram illustrating a processing method according to a first exemplary embodiment of the present application;

FIG. 6 is a schematic flow chart diagram of a processing method shown in a second exemplary embodiment of the present application;

fig. 7A-7C are schematic diagrams illustrating structures of random access preamble codes according to exemplary embodiments of the present application;

fig. 8A-8C are schematic structural diagrams of a random access preamble including a device type identifier according to an exemplary embodiment of the present application;

fig. 9 is a diagram illustrating at least one random access preamble according to an exemplary embodiment of the present application;

FIG. 10 is a schematic flow chart diagram illustrating a processing method according to a third exemplary embodiment of the present application;

FIG. 11 is a schematic flow chart diagram illustrating a processing method according to a fourth exemplary embodiment of the present application;

fig. 12 is a schematic flow chart of a processing method according to a fifth exemplary embodiment of the present application;

fig. 13 is a schematic flow chart of a processing method according to a sixth exemplary embodiment of the present application;

fig. 14 is a schematic structural diagram of a processing apparatus according to a first exemplary embodiment of the present application;

fig. 15 is a schematic structural diagram of a processing apparatus according to a second exemplary embodiment of the present application;

fig. 16 is a schematic structural diagram of a processing apparatus according to a third exemplary embodiment of the present application;

fig. 17 is a schematic structural view of a processing apparatus according to a fourth exemplary embodiment of the present application;

fig. 18 is a schematic structural view of a processing apparatus according to a fifth exemplary embodiment of the present application;

fig. 19 is a schematic structural view of a processing apparatus according to a sixth exemplary embodiment of the present application;

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

The implementation, functional features and advantages of the objectives of the present application will be further explained with reference to the accompanying drawings. With the above figures, there are shown specific embodiments of the present application, which will be described in more detail below. These drawings and written description are not intended to limit the scope of the inventive concepts in any manner, but rather to illustrate the inventive concepts to those skilled in the art by reference to specific embodiments.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended 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 recitation of an element by the phrase "comprising an … …" does not exclude the presence of additional like elements in the process, method, article, or apparatus that comprises the element, and further, where similarly-named elements, features, or elements in different embodiments of the disclosure may have the same meaning, or may have different meanings, that particular meaning should be determined by their interpretation in the embodiment or further by context with the embodiment.

It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to 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 "when … …" or "in response to a determination", depending on the context. Also, 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," when used in this specification, specify the presence of stated features, steps, operations, elements, components, items, species, and/or groups, but do not preclude the presence, or addition of one or more other features, steps, operations, elements, components, species, and/or groups thereof. The terms "or," "and/or," "including at least one of the following," and the like, as used herein, are to be construed as inclusive or mean any one or any combination. For example, "includes at least one of: A. b, C "means" any of the following: a; b; c; a and B; a and C; b and C; a and B and C ", again for example," A, B or C "or" A, B and/or C "means" any of the following: a; b; c; 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 inherently mutually exclusive in some way.

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, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown 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 multiple stages that are not necessarily performed at the same time, but may be performed at different times, in different orders, and may be performed alternately or at least partially with respect to other steps or sub-steps of other steps.

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 phrases "if determined" or "if detected (a stated condition or event)" may be interpreted as "when determined" or "in response to a determination" or "when detected (a stated condition or event)" or "in response to a detection (a stated condition or event)", depending on the context.

It should be noted that step numbers such as 501 and 502 are used herein for the purpose of more clearly and briefly describing the corresponding content, and do not constitute a substantial limitation on the sequence, and those skilled in the art may perform step number 502 and then step number 501 in the specific implementation, but these shall be within the protection scope of the present application.

It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for the convenience of description of the present application, and have no specific meaning in themselves. Thus, "module", "component" or "unit" may be used mixedly.

In this application, the communication device may be a terminal device or a network device (e.g., a base station), and the specific requirement is determined according to the context, and in addition, the terminal device may be implemented in various forms. For example, the terminal devices described in the present application may include mobile terminals such as a mobile phone, a tablet computer, a notebook computer, a palmtop computer, a Personal Digital Assistant (PDA), a Portable Media Player (PMP), a navigation device, a wearable device, a smart band, a pedometer, and the like, and fixed terminals such as a Digital TV, a desktop computer, and the like.

The following description will be given 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 mobile purposes.

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

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

the radio frequency unit 101 may be configured to receive and transmit signals during information transmission and reception or during a call, and specifically, receive downlink information of a base station and then process the downlink information to the processor 110; in addition, the uplink data is transmitted to the base station. Typically, 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 can also communicate with a network and other devices through wireless communication. The wireless communication may use any communication standard or protocol, including but not limited to GSM (Global System for Mobile communications), GPRS (General Packet Radio Service), CDMA2000 (Code Division Multiple Access 2000 ), WCDMA (Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division duplex-Long Term Evolution), TDD-LTE (Time Division duplex-Long Term Evolution, Time Division Long Term Evolution), 5G, and so on.

WiFi belongs to short-distance wireless transmission technology, and the mobile terminal can help a user to receive and send e-mails, browse webpages, access streaming media and the like through the WiFi module 102, and provides wireless broadband internet access for the user. Although fig. 1 shows the WiFi module 102, it is understood that it does not belong to the essential constitution of the mobile terminal, and may be omitted entirely as needed within the scope not changing 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 call 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 related to a specific function performed by the mobile terminal 100 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 103 may include a speaker, a buzzer, and the like.

The a/V input unit 104 is used to receive audio or video signals. The a/V input Unit 104 may include a Graphics Processing Unit (GPU) 1041 and a microphone 1042, the Graphics processor 1041 Processing image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video 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 graphic 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 may receive sounds (audio data) via the microphone 1042 in a phone call mode, a recording mode, a voice recognition mode, or the like, and may be capable of processing such sounds into audio data. The processed audio (voice) data may be converted into a format output transmittable to a mobile communication base station via the radio frequency unit 101 in case of a phone 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 audio signals.

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 that may adjust the brightness of the display panel 1061 according to the brightness of ambient light, and a proximity sensor that may turn off the display panel 1061 and/or the backlight when the mobile terminal 100 is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally, three axes), can detect the magnitude and direction of gravity when stationary, and can be used for applications of recognizing the posture of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer and tapping), and the like; as for other sensors such as a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which can be configured on the mobile phone, further description is omitted here.

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 (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 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 a touch operation performed by a user on or near the touch panel 1071 (e.g., an operation performed by the user on or near the touch panel 1071 using a finger, a stylus, or any other suitable object or accessory), and drive a 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 a touch orientation of a user, detects a signal caused by a touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 110, and can receive and execute commands sent by the processor 110. In addition, the touch panel 1071 may be implemented in various types, such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may include other input devices 1072. Optionally, 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, a mouse, a joystick, and the like, and are not limited thereto.

Alternatively, the touch panel 1071 may cover the display panel 1061, and when the touch panel 1071 detects a touch operation thereon or nearby, the touch panel 1071 transmits the touch operation to the processor 110 to determine the type of the touch event, and then the processor 110 provides a corresponding visual output on the display panel 1061 according to the type of the touch event. Although the touch panel 1071 and the display panel 1061 are shown in fig. 1 as two separate components to implement the input and output functions of the mobile terminal, in some embodiments, the touch panel 1071 and the display panel 1061 may be integrated to implement the input and output functions of the mobile terminal, and is not limited herein.

The interface unit 108 serves as an interface through which at least one external device is connected to the mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 108 may be used to receive input (e.g., data information, power, etc.) from external devices 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 external devices.

The memory 109 may be used to store software programs as well as various data. The memory 109 may mainly include a program storage area and a data storage area, and optionally, the program storage area may store an operating system, an application program (such as a sound playing function, an image playing function, and the like) required by at least one function, and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the 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 operating 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, optionally, the application processor mainly handles operating systems, user interfaces, application programs, etc., and the modem processor mainly handles wireless communications. 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 supply 111 (e.g., a battery) for supplying power to various components, and preferably, the power supply 111 may be logically connected to the processor 110 via a power management system, so as to manage charging, discharging, and power consumption management functions via 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 in detail 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 is described below.

Referring to fig. 2, fig. 2 is an architecture diagram of a communication Network system according to an embodiment of the present disclosure, where the communication Network system is an LTE system of a universal mobile telecommunications 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) 203, and an IP service 204 of an operator, which are in communication connection in sequence.

Optionally, the UE201 may be the terminal 100 described above, and is not described herein again.

The E-UTRAN202 includes eNodeB2021 and other eNodeBs 2022, among others. Alternatively, the eNodeB2021 may be connected with other enodebs 2022 through a backhaul (e.g., X2 interface), the eNodeB2021 is connected to the EPC203, and the eNodeB2021 may provide the UE201 access to the EPC 203.

The EPC203 may include an MME (Mobility Management Entity) 2031, an HSS (Home Subscriber Server) 2032, other MMEs 2033, an SGW (Serving gateway) 2034, a PGW (PDN gateway) 2035, and a PCRF (Policy and Charging Rules Function) 2036, and the like. Optionally, the MME2031 is a control node that handles signaling between the UE201 and the EPC203, providing bearer and connection management. HSS2032 is used to provide registers to manage functions such as home location register (not shown) and holds subscriber specific information about service characteristics, data rates, etc. All user data may be sent through SGW2034, PGW2035 may provide IP address assignment for UE201 and other functions, and PCRF2036 is a policy and charging control policy decision point for traffic data flow and IP bearer resources, which selects and provides available policy and charging control decisions for a policy and charging enforcement function (not shown).

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

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

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

At present, the types of terminal devices capable of accessing to a network are increasing, for example, some household appliances, wearable devices and the like can all access to the network, and specifically, the terminal devices include devices such as a refrigerator, a television, an air conditioner, a smart watch and a sports bracelet.

The types of the terminal devices may include common devices and light-duty capability (Redcap) devices, and the network device may process different terminal devices in different manners, so the network device needs to determine the types of the terminal devices.

Optionally, when the terminal device performs random access, a random access preamble (preamble) corresponding to the type device may be set in the sent message, so that the network device may distinguish the normal type device from the Redcap device according to the preamble.

Fig. 3 is a diagram illustrating a four-step random access procedure in an exemplary embodiment.

As shown in fig. 3, in the four-step random access process, a preamble may be sent when the terminal device sends a Message1 (Message 1, Msg 1) to the network device.

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

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

There are 64 preambles defined in one RO opportunity, so if the normal type device and the Redcap device are distinguished by the preamble, it is necessary to reserve a part of the preamble to the Redcap device, which results in less available preamble for the common device.

Optionally, different types of devices may also use different RO opportunities for random access, so that the network device distinguishes the type of the terminal device according to messages received by different RO opportunities. However, this approach may add additional overhead to the system.

In order to solve the above technical problem, in the scheme provided in this embodiment of the present application, when a terminal device performs random access, a random access preamble sent to a network device includes a device type identifier, and the network device may directly determine the type of the device according to the device type identifier in the received random access preamble.

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

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-duty equipment.

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

step 501, determining or generating a random access lead code when randomly accessing; optionally, the random access preamble includes a device type identifier.

Optionally, the random access procedure refers to a procedure from when the terminal device sends a preamble to attempt to access the network to before a basic signaling connection is established with the network.

Optionally, the terminal device may determine or generate a preamble at the time of random access.

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

Optionally, the determined or generated preamble may include both CP and SEQ portions. If the solution of the embodiment of the present application needs to add a device type identifier to a GP portion of a preamble, the solution of the embodiment is not applicable to the preamble that includes only the CP and SEQ. The device type identifier is used to indicate a type of the device, for example, if the device is a normal type device, the preamble of the device includes an identifier corresponding to the normal device, and if the device is a light-weight-capability device, the preamble of the device includes an identifier corresponding to the light-weight-capability device.

Optionally, a device type identifier may be set in any preamble.

Optionally, the GP part in the preamble sent by the terminal has a device type identifier, and the network device (e.g., a base station) may receive the preamble with the device type identifier. The specific implementation steps are as follows: the terminal 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 generating formula of the preamble given by a protocol, adds CP and GP to the SEQ part, and adds the equipment type identifier in the designated resource in the GP.

The adding of the device type identifier may be performed only for one preamble that is finally used by the terminal, or may be performed for at least one preamble that is possibly used by the terminal.

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

Optionally, a device type identifier may be added in the GP of the preamble. At least one resource may be selected in the GP segment with which to indicate the device type. For example, when the device type identifier is not added, the values of all resources of the GP portion of the preamble are 0, if the terminal device is a Redcap device, the value or the indication bit of the resource for indicating the device type in the GP portion of the preamble of the terminal device is 1, and/or if the terminal device is a common device, the values of all resources of the GP portion of the preamble of the terminal device are still 0. Optionally, the bit positions and the number of the specific indications may be set according to requirements.

Optionally, a device type identifier may be added to the CP of the preamble. For example, the device type identifier is indicated by at least one resource in the CP part.

Optionally, a device type identifier may be added in SEQ of the preamble. For example, the device type identifier is indicated by at least one resource in the SEQ part.

Step 502, a random access preamble is sent to report the device type identifier.

Optionally, the terminal device may send the preamble including the device type identifier to the network device. For example, at random access, the preamble may be sent to the network device.

Optionally, after receiving the preamble sent by the terminal device, the network device may obtain the device type identifier therein, 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 agree in advance on the location of the device type identifier in the preamble, so that after receiving the preamble, the network device may obtain the device type identifier from the corresponding location.

In this embodiment, it is not necessary to reserve a partial preamble for the Redcap device, and the network device can also distinguish the normal device from the Redcap device without increasing the system overhead.

The processing method provided by the embodiment of the application enables the network device to acquire the type of the terminal device by sending the random access preamble code including the device type identifier, and the method does not need to reserve the random access preamble code and increase the system overhead, so that the purpose of distinguishing the type of the terminal device can be realized with lower communication cost.

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

The processing method provided by 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-duty equipment.

As shown in fig. 6, the processing method provided by the present application includes:

step 601, receiving network side scheduling information, wherein the network side scheduling information includes information whether to allow the light capacity device to access.

Alternatively, the network device may broadcast the network-side scheduling information, and the terminal device may receive the network-side scheduling information.

Optionally, the Information on whether to allow the lightweight capable device to access is contained in a MIB (Master Information Block), or SIB1 (System Information Block), or DCI or RRC signaling of the scheduling SIB 1.

Optionally, the information on whether the lightweight capability device is allowed to access may be carried in other high-level signaling, and the terminal device may analyze the signaling to obtain the information on what capability device is allowed to access. For example, if the value of the resource indicating whether the lightweight device is allowed to access or the indication bit is 1, then the lightweight device is characterized to be allowed to access, and/or if the value of the resource indicating whether the lightweight device is allowed to access or the indication bit is 0, then the lightweight device is characterized to not be allowed to access.

Optionally, the network device and the terminal device may agree in advance which resource in the network side scheduling information is used to indicate whether the light capacity device is allowed to access, so that after receiving the network side scheduling information, the terminal device may obtain the indication information from the corresponding signaling to determine whether the network device is allowed to access the light capacity device.

Step 602, during random access, determining whether to determine or generate a random access preamble according to the network side scheduling information.

Optionally, after receiving the network side scheduling information, the terminal device may specifically determine whether to perform random access according to the network side scheduling information when a random access procedure is required.

If the terminal equipment needs to perform random access, the terminal equipment determines that the terminal equipment can perform random access according to the network side scheduling information, the terminal equipment can determine or generate a preamble, and if the terminal equipment determines that the terminal equipment cannot perform random access according to the network side scheduling information, the terminal equipment does not determine or generate the preamble.

Optionally, if the preamble is determined or generated, the device type identifier is included in the determined or generated preamble.

In the first case, if the terminal device is a light-weight device and the network side scheduling information representation does not allow the light-weight device to access, the preamble is not determined or generated.

Optionally, if the current terminal device is a light-capacity device and the network side scheduling information represents that the light-capacity device is not allowed to access, it may be considered that the network device does not allow the terminal device to access, and optionally, the terminal device is not determined or does not generate a preamble.

In the second case, if the terminal device is a light-weight device and the network side scheduling information represents that the light-weight device is allowed to access, a preamble is determined or generated when random access is required.

Optionally, if the current terminal device is a light-weight device and the scheduling information representation of the network side allows the light-weight device to access, it may be considered that the network device allows the terminal device to access, and optionally, the terminal device may determine or generate a preamble when random access is required.

Optionally, in the application scenario, the type of the terminal device is a light-capacity device, and therefore, the device type identifier in the preamble determined or generated by the terminal device is an identifier corresponding to the light-capacity device.

In the third case, if the type of the terminal device is a common device, no matter whether the representation of the network side scheduling information allows the access of the light-duty device, as long as the representation of the network side scheduling information allows the access of the common device, the terminal device may determine or generate a preamble when the terminal device needs to perform random access.

Optionally, in the application scenario, the type of the terminal device is a common device, and therefore, the device type identifier in the preamble determined or generated by the terminal device is an identifier corresponding to the common device.

In the fourth case, there are some terminal devices that have both the capability of a light-weight device and the capability of a normal device.

Optionally, for a device with normal capability and light capability, if the device accesses a network with the normal device capability, if the scheduling information of the network side indicates that the light capability device is allowed to access but the normal device is not allowed to access, the device is not determined or does not generate a preamble during the random access process; and/or if the device accesses the network by the capacity of the common device, and the scheduling information representation of the network side allows the access of the common capacity device but not the access of the light device, the device can determine or generate a preamble in the random access process; and/or if the device accesses the network by the ordinary device capability, and the network side scheduling information representation allows the ordinary capability device to access and the light device to access, the device serving as the ordinary capability device can determine or generate a preamble in the random access process.

Optionally, for a device with normal capability and light capability, if the device accesses the network with the light device capability, if the scheduling information of the network side indicates that the light-capability device is allowed to access but the normal device is not allowed to access, the device determines or generates a preamble in a random access process; and/or if the device accesses the network by the capacity of the light device, and the scheduling information representation of the network side allows the access of the common capacity device but not the access of the light device, the device is uncertain or does not generate a preamble in the random access process; and/or if the device accesses the network by the light device capacity, and the network side scheduling information representation allows the access of the common capacity device and the access of the light device, the device serving as the light capacity device can determine or generate a preamble in the random access process.

Alternatively, the terminal device may determine what capability it accesses the network based on traffic demand.

Optionally, the terminal device may determine which type to access the network device according to a function that needs to be implemented currently or a service that needs to be processed, and determine or generate a preamble corresponding to the device type. For example, if the terminal device determines that the network device is accessed by a common device type, the device type identifier in the preamble determined or generated by the terminal device is an identifier corresponding to the common device; and/or if the terminal device determines to access the network device by the type of the light-capacity device, the device type identifier in the preamble determined or generated by the terminal device is the identifier corresponding to the light-capacity device.

Optionally, the device type of the terminal device is not changed during one network access process, but may be changed during multiple network access processes based on the service requirement. For example, the device type identifier used when the network procedure is accessed for the first time is different from the device type identifier used when the network procedure is accessed for the second time.

Optionally, if the terminal device determines or generates a preamble, the method provided by the present application may further include:

step 603, sending a random access preamble through a random access channel to report the device type identifier.

Optionally, the terminal device may send the preamble through a random access channel. For example, in four-step random access, the preamble may be sent through message1 (MSG 1). In two random accesses, the preamble may be sent via message a (msga).

Optionally, the device type identifier is located in a guard interval in the preamble.

Fig. 7A-7C are schematic diagrams illustrating structures of random access preambles according to exemplary embodiments of the present application.

As shown in fig. 7A, 7B, and 7C, any preamble provided herein includes three parts, CP71, SEQ72, and GP 73. The device type identification may be set in the GP73 therein.

The preambles shown in fig. 7A-7C are only schematic representations, and other forms of preambles may also be set as needed.

Optionally, the device type identifier is located in a designated resource unit of the GP. Resource units may be specified in the GP in advance, so that the device type identifier is placed by using the specified resource units.

Optionally, the network device and the terminal device may subscribe a designated resource unit of the GP in advance, so that the terminal device may set the device type identifier in the designated resource unit of the GP, and the network device reads the device type identifier from the designated resource unit of the GP.

Fig. 8A-8C are diagrams illustrating structures of a random access preamble including device type identifiers according to exemplary embodiments of the present application.

As shown in fig. 8A, a device type identifier may be set in a first resource unit 731 of a GP of a preamble.

As shown in fig. 8B, a device type identifier may be set in the last resource element 732 of the GP of the preamble.

As shown in fig. 8C, a device type identifier may be set in any one of the resource units 733 between the preamble first resource unit and the last resource unit.

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

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

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

For example, the device type identifier may be set in any resource unit between the preamble first resource unit and the last resource unit as shown in fig. 7A or fig. 7B.

In the transmitted communication signal, the smallest resource granularity in the time domain is one OFDM (Orthogonal Frequency Division Multiplexing) symbol, and the smallest granularity in the Frequency domain is one subcarrier, and one OFDM symbol and one subcarrier constitute one resource unit.

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

a first portion of random access preamble codes;

a second portion of random access preamble;

a third portion of the random access preamble.

Optionally, the terminal device may generate at least one preamble, which may be divided into three parts.

Alternatively, the effect of different partial preambles may be different. The network device and the terminal device may pre-agree on the function of each preamble, so that after receiving the preamble, the network device may select a suitable preamble group for corresponding processing according to the process in which the terminal device is located.

For example, the terminal device may utilize the first portion of preamble for contention-based random access.

In CBRA (Contention Based Random Access), a terminal device randomly selects one preamble from a preamble pool shared with other terminal devices, which means that the terminal device has the potential risk of selecting the same preamble as another terminal device and may then experience a collision or dispute.

For another example, the terminal device may utilize the second partial preamble to perform non-contention based random access.

In non-Contention based Random Access (CFRA), a preamble is allocated by a network device, and such a preamble is referred to as a dedicated Random Access preamble. The dedicated sequence is provided to the terminal device through Radio Resource Control (RRC) signaling (the allocation sequence may be specified in an RRC message) or through Physical Downlink Control (PDCCH) signaling. Therefore, there is no preamble collision.

For example, the terminal device may use the third preamble to perform random access for other purposes.

For example, when other system information needs to be acquired, the terminal device is triggered to determine or generate the preamble, and in this case, the terminal device may send the preamble belonging to the third part to the network device, so that the network device feeds back the system information.

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

The 64 preambles may include the first partial preamble, the second partial preamble, and the third partial preamble.

Fig. 9 is a diagram illustrating at least one random access preamble according to an exemplary embodiment of the present application.

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

Optionally, each of the 64 preambles has a corresponding SSB (Synchronization Signal Block). For example, the 0 th to 6 th preambles correspond to SSB #0, and the 7 th to 13 th preambles correspond to SSB #1, and the 49 th to 55 th preambles correspond to SSB #7, respectively, in ….

When sending the preamble, the terminal device may determine the SSB, and then send the preamble corresponding to the SSB.

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

As shown in fig. 10, the processing method provided by the present application includes:

step 1001, determining a sending strategy of the random access preamble according to the network side scheduling information and the type of the terminal device.

When the terminal device needs to send the preamble to the network device, the terminal device may first determine a sending policy of the preamble. Optionally, at least one sending policy may be preset, and the terminal device may determine the sending policy from the preset at least one sending policy according to the network-side scheduling information and the type of the terminal device. Optionally, the terminal device may determine the current transmission policy by combining the network-side scheduling information and its own type.

Optionally, the network-side scheduling information may be broadcast by the network device, so that the terminal device can receive the network-side scheduling information. The network-side scheduling information may include device access information, for example, information on whether to allow access to a light-capability device, and for example, information on whether to allow access to a general device.

Optionally, the terminal device may determine the sending policy according to the device access information and the type information of the terminal device included in the network side scheduling information. For example, if the network side scheduling information represents that the lightweight capability device is not allowed to access the network device, and the type of the terminal device is the lightweight capability device, the sending policy determined by the terminal device is that the preamble is not sent. For another example, if the network side scheduling information represents that the light-capacity device is allowed to access the network device, and the type of the terminal device is the light-capacity device, the sending policy determined by the terminal device is to determine or generate a preamble during random access, and send the preamble.

Step 1002, sending a random access preamble according to a sending policy, and reporting the device type identifier.

Optionally, after determining the sending policy of the preamble, the terminal device may send the preamble according to the sending policy, and report the device type identifier through the preamble.

Optionally, if the sending policy determined by the terminal device is that the preamble is not sent, the terminal device may not determine or generate the preamble, and the preamble is not sent to the network device.

Optionally, if the sending policy determined by the terminal device is to determine or generate a preamble, and send the preamble, the terminal device may determine or generate the preamble during random access; optionally, the preamble includes a device type identifier.

Optionally, if the sending policy determined by the terminal device is to determine or generate a preamble, and send the preamble, the sending policy may further specifically include a rule for generating the preamble.

Optionally, if the terminal device determines or generates the preamble, the determined or generated preamble includes the type of the terminal device. For example, if the type of the terminal device is a light-duty device, the preamble includes an identifier of the light-duty device; and/or if the type of the terminal equipment is the common equipment, the preamble comprises the identification of the common equipment.

Optionally, the terminal device may process the root sequence issued by the upper layer according to a formula used for determining or generating the preamble in the protocol, so as to obtain the preamble. Alternatively, the terminal device may generate the SEQ in the preamble by cyclically shifting the root sequence until the generated SEQ reaches 64.

The terminal device may add a device type identifier to the generated preamble according to the device type of the terminal device. For example, a device type identifier may be added to each generated preamble.

Optionally, the terminal device may send the preamble including the device type identifier to the network device. For example, the terminal device may send the preamble to the network device when randomly accessing.

The processing method provided by the embodiment of the application determines a sending strategy of the random access lead code according to the network side scheduling information and the type of the terminal equipment, sends the random access lead code according to the sending strategy, and reports the equipment type identification. The method does not need to reserve the random access lead code, and does not additionally increase the scheduling overhead of the network side, thereby realizing the purpose of distinguishing the types of the terminal equipment with lower communication cost.

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

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

step 1101, receiving network side scheduling information, wherein the network side scheduling information includes information whether to allow the lightweight capability device to access.

Alternatively, the network device may broadcast the network-side scheduling information, and the terminal device may receive the network-side scheduling information. For example, the DCI or RRC signaling of the MIB, or SIB1, or scheduling SIB1 includes information about whether to allow the lightweight device to access.

Optionally, the type of the terminal device executing the method provided by the embodiment of the present application includes at least one of the following: light-duty equipment and ordinary equipment.

Optionally, the network-side scheduling information may include information on whether to allow the lightweight device to access, and after receiving the information, the terminal device may determine whether it can access the current network.

Optionally, the MIB of the network side scheduling information may include information on whether to allow the lightweight device to access. Or may include information in any one or more SIBs whether to allow access by the light-capable device. For example, a resource may be selected therein to indicate whether a lightweight device is allowed access. For example, if the indication bit is 1, the representation allows the light capacity device to access, and/or if the indication bit is 0, the representation does not allow the light capacity device to access.

Optionally, the network device and the terminal device may pre-agree which resource in the network side scheduling information indicates whether the light capacity device is allowed to access, so that after receiving the network side scheduling information, the terminal device may obtain the indication information from the corresponding signaling to determine whether the network device allows the light capacity device to access.

Optionally, the terminal device may execute any one of the

steps

1102 and 1104 according to the specifically received network-side scheduling information and its type.

Step 1102, if the terminal device is a light capacity device and the network side scheduling information representation does not allow the light capacity device to access, the sending policy is uncertain or no random access preamble is generated.

Optionally, if the current terminal device is a light-weight device and the network side scheduling information represents that the light-weight device is not allowed to access, it may be considered that the network device does not allow the terminal device to access, and therefore, the terminal device may not perform a random access procedure, that is, it is not determined or a preamble is not generated.

Step 1103, if the terminal device is a light-weight device and the network side scheduling information represents that the light-weight device is allowed to access, sending a policy to determine or generate a random access preamble, and sending the random access preamble.

If the current terminal device is a light-weight device and the scheduling information representation of the network side allows the light-weight device to access, the network device can be considered to allow the terminal device to access, and therefore, the terminal device can determine or generate a preamble in the random access process.

And 1104, if the terminal device has the capabilities of the light-weight capability device and the common device, the terminal device accesses the network by the common device capability, and the network side scheduling information represents that the light-weight capability device is not allowed to access and the common device is allowed to access, sending a policy to determine or generate a random access preamble, and sending the random access preamble.

Optionally, the terminal device may confirm that it is a normal device based on the service requirement.

In this application scenario, for such a terminal device that has both the capabilities of the light-weight capability device and the capabilities of the common device, if the terminal device accesses the network with the common device capability, it is characterized that the terminal device can only access the network device with the identity of the common device, and therefore, if the scheduling information at the network side characterizes that the light-weight capability device is not allowed to access and the common device is allowed to access, the terminal device may determine or generate a preamble, and optionally, the device type identifier in the preamble determined or generated by the terminal device is an identifier corresponding to the common device.

Optionally, for a device with normal capability and light capability, if the device accesses a network with the normal device capability, if the scheduling information of the network side indicates that the light capability device is allowed to access but the normal device is not allowed to access, the device is not determined or does not generate a preamble during the random access process; and/or, for a device with ordinary capability and light capability, if the device accesses the network with ordinary device capability, if the network side scheduling information represents that the ordinary capability device is allowed to access but the light device is not allowed to access, the device may determine or generate a preamble during the random access; and/or for a device with normal capability and light capability, if the device accesses the network with the normal device capability, if the network side scheduling information represents that the device with normal capability is allowed to access the network and the device with light capability is allowed to access the network, the device serving as the normal capability device can determine or generate a preamble in the random access process.

Optionally, if the type of the terminal device is a common device, no matter whether the representation of the network side scheduling information allows the access of the light-duty device, as long as the representation of the network side scheduling information allows the access of the common device, the terminal device may perform a random access procedure, and may specifically determine or generate a preamble.

If the terminal device determines or generates the preamble, the preamble can be sent through the random access channel to report the device type identifier.

Optionally, the terminal device may send the preamble through a random access channel. For example, in the four-step random access procedure, the preamble may be transmitted through message1 (MSG 1). In two random accesses, the preamble may be sent via message a (msga).

Optionally, the preamble is determined or generated at random access. The random access process refers to a process from the time when the terminal device sends preamble and tries to access the network to the time when a basic signaling connection is established between the terminal device and the network. For example, when randomly accessing, the terminal device may determine a sending policy of the preamble according to the network side scheduling information and the type of the terminal device, and further determine or generate the preamble.

The device type identifier is located in a GP in the preamble.

Optionally, the preamble includes three parts of CP, SEQ and GP. The device type identification may be set in the GP therein.

Optionally, the determined or generated preamble may include both CP and SEQ portions. If the solution of the embodiment of the present application needs to add a device type identifier to a GP portion of a preamble, the solution of the embodiment of the present application is not applicable to the preamble that only includes the CP and the SEQ.

Optionally, a device type identifier may be set in any preamble.

Optionally, the device type identifier may be set in the first resource unit of the GP of the preamble.

Optionally, the device type identifier may be set in the last resource unit of the GP of the preamble.

Still alternatively, the device type identifier may be set in any resource unit between the preamble first resource unit and the last resource unit.

The number of preambles is 64.

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

In the 64 random access preamble codes, 0-3, 7-10, 14-17.. 49-52 preambles are used for random access based on competition, 4-6, 11-13, 53-55 preambles are used for random access based on non-competition, and 56-63 preambles are used for random access based on other purposes.

Optionally, each of the 64 preambles has a corresponding SSB. For example, the 0 th to 6 th preambles correspond to SSB #0, and the 7 th to 13 th preambles correspond to SSB #1, and the 49 th to 55 th preambles correspond to SSB #7, respectively, in ….

The random access preamble comprises at least one of:

a first portion of random access preamble codes;

a second portion of random access preamble;

a third portion of the random access preamble.

Optionally, the terminal device may generate at least one preamble, which is divided into three parts.

In CBRA, a terminal device randomly selects one preamble from a pool of preambles shared with other terminal devices. This means that the terminal device has the potential risk of selecting the same preamble as another terminal device and may then experience a conflict or dispute.

In CFRA, preambles are assigned by network devices, such preambles are referred to as dedicated random access preambles. The dedicated sequence is provided to the terminal device through Radio Resource Control (RRC) signaling (the allocation sequence may be specified in an RRC message) or through Physical Downlink Control (PDCCH) signaling, and thus, there is no preamble collision.

For another example, the terminal device may use the third preamble to perform random access based on other purposes.

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

The processing method provided by the embodiment of the application is applied to network equipment, the terminal equipment can be accessed to the network equipment, and the terminal equipment can be ordinary equipment or light-duty equipment.

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

step 1201, receiving a random access preamble sent by a terminal device; optionally, the random access preamble includes a device type identifier.

Optionally, the random access procedure refers to a procedure from when the terminal device sends a preamble to try to access the network to when a basic signaling connection is established with the network.

Optionally, at the time of random access, the terminal device may determine or generate a preamble, and the determined or generated preamble may include three parts, CP, SEQ, and GP.

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

Optionally, the terminal device may send a preamble including the device type identifier to the network device, so that the network device can receive the preamble.

Step 1202, obtaining a device type identifier in the random access preamble, and determining the type of the terminal device according to the device type identifier.

Optionally, after receiving the preamble sent by the terminal device, the network device may obtain the device type identifier therein, further determine the type of the terminal device, and may also send a message to the terminal device according to the type of the terminal device.

Optionally, the terminal device and the network device may agree in advance the location of the device type identifier in the preamble, so that after receiving the preamble, the network device may obtain the device type identifier from the corresponding location, and further determine the type of the terminal device.

For example, if the value of the device type identifier or the indication bit is 1, it is determined that the terminal device is a Redcap device; and/or if the value of the equipment type identifier or the indication bit is 0, determining that the terminal equipment is the common equipment.

The processing method provided by the embodiment of the application enables the network device to acquire the type of the terminal device by receiving the random access preamble code including the device type identifier, and the method does not need to reserve the random access preamble code and increase the system overhead, so that the purpose of distinguishing the type of the terminal device can be realized with lower communication cost.

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

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

step 1301, network side scheduling information is broadcasted, and the network side scheduling information includes information whether to allow the light capacity device to access, so that a terminal device receiving the network side scheduling information determines whether to determine or generate a random access preamble according to the network side scheduling information.

Alternatively, the network device may broadcast the network-side scheduling information, and the terminal device may receive the network-side scheduling information. Optionally, the DCI or RRC signaling of the MIB, or SIB1, or scheduling SIB1 includes information about whether to allow the lightweight device to access.

Optionally, the information on whether the lightweight capability device is allowed to access may be carried in other high-level signaling, and the terminal device may analyze the signaling to obtain the information on what capability device is allowed to access. For example, if the value indicating whether the lightweight device is allowed to access or the bit is indicated to be 1, then the lightweight device is characterized to be allowed to access, and/or if the value indicating whether the lightweight device is allowed to access or the bit is indicated to be 0, then the lightweight device is characterized to not be allowed to access.

Optionally, if the current terminal device is a light-weight device and the network side scheduling information representation does not allow the light-weight device to access, it may be considered that the network device does not allow the terminal device to access, and therefore, the terminal device does not need to perform a random access process, that is, it is not determined or a preamble is not generated.

Optionally, if the current terminal device is a light-weight device and the scheduling information representation of the network side allows the light-weight device to access, it may be considered that the network device allows the terminal device to access, and therefore, when the terminal device needs to perform random access, the preamble may be determined or generated.

Optionally, for a device with normal capability and light capability, if the device accesses the network with the normal device capability, and the network side scheduling information represents that the light capability device is not allowed to access and the normal device is allowed to access, the terminal device accesses the network device with the type of the normal device, so that the terminal device may determine or generate a preamble when performing a random access procedure.

In this application scenario, since the terminal device is accessed to the network device by using the type of the normal device, the device type identifier in the preamble determined or generated by the terminal device is the identifier corresponding to the normal device.

Optionally, for a device with ordinary capability and light capability, if the device accesses a network with ordinary device capability, if the network side scheduling information represents that the light capability device is allowed to access but the ordinary device is not allowed to access, the device is not determined or does not generate a preamble during a random access process; and/or, for a device with ordinary capability and light capability, if the device accesses the network with ordinary device capability and the network side scheduling information represents that the ordinary capability device is allowed to access but the light device is not allowed to access, the device may determine or generate a preamble during the random access process; and/or, for a device with ordinary capability and light capability, if the device accesses the network with ordinary device capability and the network side scheduling information representation allows the access of the ordinary capability device and the access of the light device, the device as an ordinary capability device may determine or generate a preamble during the random access process.

Optionally, for a device with normal capability and light capability, if the device accesses the network with the light device capability, if the scheduling information of the network side indicates that the light-capability device is allowed to access but the normal device is not allowed to access, the device determines or generates a preamble in a random access process; and/or if the device accesses the network by the capacity of the light device and the scheduling information representation of the network side allows the access of the common capacity device but not the access of the light device, the device is uncertain or does not generate a preamble in the random access process; and/or if the device accesses the network by the light device capacity, and the network side scheduling information representation allows the access of the common capacity device and the access of the light device, the device serving as the light capacity device can determine or generate a preamble in the random access process.

Alternatively, the terminal device may determine its device type based on traffic requirements.

Optionally, if the terminal device determines or generates the preamble, it may send the preamble to the network device, so that the network device can receive the corresponding preamble.

Step 1302, receiving a random access preamble sent by a terminal device through a random access channel; optionally, the random access preamble includes a device type identifier.

Optionally, the terminal device may send the preamble through a random access channel. For example, in a four-step random access, the preamble may be transmitted through the msg 1. When two steps of random access are performed, the preamble can be sent through the message msgA, so that the network device can receive the preamble sent by the terminal.

Step 1303, obtaining the device type identifier in the specified resource unit in the guard interval in the random access preamble, and determining the type of the terminal device according to the device type identifier.

Optionally, the device type identifier is located in a GP in the preamble, and in this embodiment, the network device may obtain the device type identifier from the GP in the preamble.

Alternatively, the device type identifier may be located in a designated resource unit of the GP. In this case, the network device may obtain the device type identifier from a specified resource unit in the GP of the preamble.

Optionally, the network device and the terminal device may subscribe a designated resource unit of the GP in advance, so that the terminal device may set the device type identifier in the designated resource unit of the GP, and the network device may obtain the device type identifier from the designated resource unit of the GP.

Optionally, the terminal device may set a device type identifier in the first resource unit of the GP of the preamble, and the network device may obtain the device type identifier from the first resource unit of the GP of the preamble.

Optionally, the terminal device may set a device type identifier in the last resource unit of the GP of the preamble, and the network device may obtain the device type identifier from the last resource unit of the guard interval of the preamble.

Optionally, the terminal device may set a device type identifier in any resource unit between the first resource unit of the preamble and the last resource unit, and the network device may obtain the device type identifier from any resource unit between the first resource unit of the preamble and the last resource unit.

a first portion of random access preamble codes;

a second portion of random access preamble;

a third portion of the random access preamble.

The network device may generate at least one preamble based on a protocol, for example, 64 preambles, and may further identify the received preamble in the generated preamble, specifically, identify the received preamble in the first part of the preambles, the second part of the preambles, or the third part of the preambles.

In such an embodiment, the network device may identify the received random access preamble in the contention-based first portion of the random access preamble.

In such an embodiment, the network device identifies the received random access preamble in the non-contention based second portion of random access preambles.

In this embodiment, the network device identifies the received random access preamble in a third part of random access preambles acquired based on the network side scheduling information.

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

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

After receiving the preamble, the network device performs preamble blind detection based on random access triggered by which event, thereby determining the type of the device accessing the network and which SSB the device uses to send the preamble.

Fig. 14 is a schematic structural diagram of a processing apparatus according to a first exemplary embodiment of the present application.

The processing device 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-duty equipment.

As shown in fig. 14, a processing apparatus 1400 provided in the embodiment of the present application includes:

a code determination unit 1410, configured to determine or generate a random access preamble at the time of random access; optionally, the random access preamble includes a device type identifier;

a sending unit 1420, configured to send the random access preamble to report the device type identifier.

The specific principle and implementation of the processing apparatus provided in this embodiment are similar to those of the embodiment shown in fig. 5, and are not described here again.

Fig. 15 is a schematic structural diagram of a processing apparatus according to a second exemplary embodiment of the present application.

As shown in fig. 15, based on the embodiment shown in fig. 14, in a processing apparatus 1500 provided in the embodiment of the present application, the device type identifier is located in a guard interval in the random access preamble.

Optionally, the device type identifier is located in a specified resource unit of the guard interval.

Optionally, the random access preamble comprises at least one of:

a first portion of random access preamble codes;

a second portion of random access preamble;

a third portion of the random access preamble.

Optionally, the sending unit 1420 includes:

a first access module 1421, configured to perform contention-based random access by using the first part of random access preamble;

a second access module 1422, configured to perform non-contention based random access by using the second part of random access preamble;

a third accessing module 1423, configured to utilize the third part of the random access preamble for random access based on other purposes.

Optionally, the number of the random access preamble codes is 64; and/or the presence of a gas in the gas,

the sending unit 1420 is specifically configured to: transmitting the random access preamble through a random access channel.

Optionally, the apparatus further includes a receiving unit 1430, configured to receive network-side scheduling information, where the network-side scheduling information includes information about whether to allow the lightweight capability device to access;

at the time of random access, the code determination unit 1410 determines whether to determine or generate the random access preamble according to the network-side scheduling information.

Optionally, the code determining unit 1410 is specifically configured to at least one of:

if the terminal equipment is light-weight capacity equipment and the network side scheduling information represents that the light-weight capacity equipment is not allowed to be accessed, the random access lead code is not determined or generated;

if the terminal equipment is light-weight capacity equipment and the network side scheduling information represents that the light-weight capacity equipment is allowed to be accessed, determining or generating the random access lead code;

and if the terminal equipment has the capacity of the light capacity equipment and the capacity of the common equipment, the equipment type identifier of the terminal equipment is an identifier corresponding to the common equipment, and the network side scheduling information represents that the light capacity equipment is not allowed to be accessed and the common equipment is allowed to be accessed, determining or generating the random access lead code.

The specific principle and implementation of the processing apparatus provided in this embodiment are similar to those of the embodiment shown in fig. 6, and are not described here again.

Fig. 16 is a schematic structural diagram of a processing apparatus according to a third exemplary embodiment of the present application.

The processing device provided by the embodiment of the application is applied to terminal equipment. As shown in fig. 16, a processing apparatus 1600 provided in the embodiment of the present application includes:

a policy determining unit 1610, configured to determine a sending policy of a random access preamble according to network-side scheduling information and the type of the terminal device;

a sending unit 1620, configured to send the random access preamble according to the sending policy, so as to report the device type identifier.

The specific principle and implementation of the processing apparatus provided in this embodiment are similar to those of the embodiment shown in fig. 10, and are not described here again.

Fig. 17 is a schematic structural diagram of a processing apparatus according to a fourth exemplary embodiment of the present application.

The processing device provided by the embodiment of the application is applied to terminal equipment. As shown in fig. 17, in the processing apparatus 1700 provided in the embodiment of the present application, on the basis of the foregoing embodiment, the type of the terminal device includes at least one of the following: light-duty equipment and ordinary equipment.

Optionally, the network-side scheduling information includes information on whether to allow the lightweight capability device to access.

Optionally, the device type identifier is located in a guard interval in the random access preamble.

Optionally, the random access preamble is determined or generated at random access.

Optionally, the number of the random access preambles is 64.

Optionally, the sending unit 1620 is specifically configured to send the random access preamble through a random access channel.

Optionally, the apparatus further comprises:

a receiving unit 1630, configured to receive network-side scheduling information, where the network-side scheduling information includes information about whether to allow access of a light-capability device.

Optionally, the policy determining unit 1610 includes:

a non-access module 1611, configured to, if the terminal device is a light-weight device and the network-side scheduling information indicates that the light-weight device is not allowed to be accessed, determine that the sending policy is uncertain or the random access preamble is not generated;

a first policy module 1612, configured to determine or generate the random access preamble and send the random access preamble if the terminal device is a light-weight device and the network-side scheduling information represents that the light-weight device is allowed to access;

a second policy module 1613, configured to determine or generate the random access preamble if the terminal device has the capabilities of a light-weight device and a normal device, the device type identifier of the terminal device is an identifier corresponding to a normal device, and the network-side scheduling information indicates that the light-weight device is not allowed to access and the normal device is allowed to access, and send the random access preamble.

Optionally, the random access preamble comprises at least one of:

a first portion of random access preamble codes;

a second portion of random access preamble;

a third portion of the random access preamble.

Optionally, at least one of the following is also included:

performing contention-based random access using the first portion of random access preamble codes;

performing non-contention based random access using the second portion of random access preamble;

and utilizing the third part of random access preamble codes to carry out random access based on other purposes.

The specific principle and implementation of the processing apparatus provided in this embodiment are similar to those of the embodiment shown in fig. 11, and are not described here again.

Fig. 18 is a schematic structural diagram of a processing apparatus according to a fifth exemplary embodiment of the present application.

The processing device provided by the embodiment of the application is applied to network equipment. As shown in fig. 18, a processing device 1800 according to an embodiment of the present application includes:

a receiving unit 1810, configured to receive a random access preamble sent by a terminal device; optionally, the random access preamble includes a device type identifier;

an obtaining unit 1820, configured to obtain a device type identifier in the random access preamble;

a type determining unit 1830, configured to determine the type of the terminal device according to the device type identifier.

The specific principle and implementation of the processing apparatus provided in this embodiment are similar to those of the embodiment shown in fig. 12, and are not described here again.

Fig. 19 is a schematic structural diagram of a processing apparatus according to a sixth exemplary embodiment of the present application.

The processing device provided by the embodiment of the application is applied to network equipment. Based on the embodiment shown in fig. 18, in the processing apparatus 1900 provided in this embodiment of the application, the device type identifier is located in a guard interval in the random access preamble.

Optionally, the obtaining unit 1820 is specifically configured to:

and acquiring the equipment type identification in the appointed resource unit in the guard interval in the random access lead code.

Optionally, the random access preamble comprises at least one of:

a first portion of random access preamble codes;

a second portion of random access preamble;

a third portion of the random access preamble.

Optionally, the apparatus further comprises a determining unit 1840 for at least one of:

if the terminal equipment carries out random access based on competition, identifying the received random access lead code in a first part of random access lead codes based on competition;

if the terminal equipment carries out random access based on non-competition, identifying the received random access lead code in a second part of random access lead codes based on non-competition;

and if the terminal equipment performs random access based on other purposes, identifying the received random access lead code in a third part of random access lead codes acquired based on the scheduling information of the network side.

the receiving unit 1810 is specifically configured to: and receiving the random access preamble sent by the terminal equipment through a random access channel.

Optionally, the apparatus further comprises a broadcasting unit 1850 for:

and broadcasting network side scheduling information, wherein the network side scheduling information comprises information about whether the light capacity equipment is allowed to access, so that the terminal equipment receiving the network side scheduling information determines whether to determine or generate the random access preamble according to the network side scheduling information.

The specific principle and implementation of the processing apparatus provided in this embodiment are similar to those of the embodiment shown in fig. 13, and are not described here again.

The embodiment of the application provides a processing method, which is applied to terminal equipment and comprises the following steps:

Optionally, the random access preamble comprises at least one of:

a first portion of random access preamble codes;

a second portion of random access preamble;

a third portion of the random access preamble.

Optionally, the method further comprises at least one of:

Optionally, the number of the random access preamble codes is 64; and/or the sending the random access preamble comprises: transmitting the random access preamble through a random access channel.

Optionally, the method further comprises:

receiving network side scheduling information, wherein the network side scheduling information comprises information whether to allow the light capacity equipment to access;

and when the random access is carried out, determining whether to determine or generate the random access preamble according to the network side scheduling information.

Optionally, the determining whether to determine or generate the random access preamble according to the network side scheduling information includes at least one of:

Optionally, the type of the terminal device includes at least one of: light-duty equipment and ordinary equipment.

Optionally, the number of the random access preambles is 64.

Optionally, the sending the random access preamble comprises: transmitting the random access preamble through a random access channel.

Optionally, the method further comprises: and receiving network side scheduling information, wherein the network side scheduling information comprises information whether the light capacity equipment is allowed to access.

Optionally, the determining a transmission policy of the random access preamble according to the network side scheduling information and the type of the terminal device includes at least one of:

if the terminal equipment is light-weight capacity equipment and the network side scheduling information represents that the light-weight capacity equipment is not allowed to be accessed, the sending strategy is uncertain or the random access lead code is not generated;

if the terminal device is a light capacity device and the network side scheduling information represents that the light capacity device is allowed to access, determining or generating the random access lead code and sending the random access lead code by the sending strategy;

if the terminal device has the capabilities of the light-weight capability device and the capabilities of the common device, the device type identifier of the terminal device is an identifier corresponding to the common device, and the network side scheduling information represents that the light-weight capability device is not allowed to access and the common device is allowed to access, the sending policy is to determine or generate the random access preamble and send the random access preamble.

Optionally, the random access preamble comprises at least one of:

a first portion of random access preamble codes;

a second portion of random access preamble;

a third portion of the random access preamble.

Optionally, the method further comprises at least one of:

and utilizing the third part of random access preamble codes to carry out random access for other purposes.

The embodiment of the application provides a processing method, which is applied to network equipment, and the method comprises the following steps:

Optionally, the obtaining the device type identifier in the random access preamble includes: and acquiring the equipment type identification in the appointed resource unit in the guard interval in the random access lead code.

Optionally, the random access preamble comprises at least one of:

a first portion of random access preamble codes;

a second portion of random access preamble;

a third portion of the random access preamble.

Optionally, the method further comprises at least one of:

and if the terminal equipment performs random access based on other purposes, identifying the received random access preamble in a third part of random access preambles accessed based on other purposes.

Optionally, the number of the random access preamble codes is 64; and/or, the receiving the random access preamble sent by the terminal device includes: and receiving the random access preamble sent by the terminal equipment through a random access channel.

Optionally, the method further comprises: and broadcasting network side scheduling information, wherein the network side scheduling information comprises information about whether the light capacity equipment is allowed to access, so that the terminal equipment receiving the network side scheduling information determines whether to determine or generate the random access preamble according to the network side scheduling information.

As shown in fig. 20, the communication apparatus provided in the present embodiment includes:

a memory 2001;

a processor 2002; and the number of the first and second groups,

a computer program.

Optionally, the computer program is stored in the memory 2001 and configured to be executed by the processor 2002 to implement the processing method shown in any one of the above-mentioned embodiments.

The present embodiments also provide a computer-readable storage medium, having stored thereon a computer program,

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

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

The embodiment of the present application further provides a communication device, where the communication device includes a memory and a processor, and the memory stores a processing program, and the processing program, when executed by the processor, implements the steps of the processing method in any of the above embodiments.

The embodiment of the present application further provides a computer-readable storage medium, where a processing program is stored on the computer-readable storage medium, and when the processing program is executed by a processor, the processing program implements the steps of the processing method in any of the above embodiments.

In the embodiments of the communication device and the computer-readable storage medium provided in the embodiments of the present application, all technical features of any one of the embodiments of the processing method may be included, and the expanding and explaining contents of the specification are basically the same as those of the embodiments of the method, and are not described herein again.

Embodiments of the present application also provide a computer program product, which includes computer program code, when the computer program code runs on a computer, the computer is caused to execute the method in the above various possible embodiments.

Embodiments of the present application further provide a chip, which includes a memory and a processor, where the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that a device in which the chip is installed executes the method in the above various possible embodiments.

It is to be understood that the foregoing scenarios are only examples, and do not constitute a limitation on application scenarios of the technical solutions provided in the embodiments of the present application, and the technical solutions of the present application may also be applied to other scenarios. For example, as can be known by those skilled in the art, with the evolution of system architecture and the emergence of new service scenarios, the technical solution provided in the embodiments of the present application is also applicable to similar technical problems.

The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits 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 in the embodiment of the application can be merged, divided and deleted according to actual needs.

In the present application, the same or similar term concepts, technical solutions and/or application scenario descriptions will be generally described only in detail at the first occurrence, and when the description is repeated later, the detailed description will not be repeated in general for brevity, and when understanding the technical solutions and the like of the present application, reference may be made to the related detailed description before the description for the same or similar term concepts, technical solutions and/or application scenario descriptions and the like which are not described in detail later.

In the present application, each embodiment is described with emphasis, and reference may be made to the description of other embodiments for parts that are not described or illustrated in any embodiment.

The technical features of the technical solution of the present application may be arbitrarily combined, and for brevity of description, all possible combinations of the technical features in the embodiments are not described, however, as long as there is no contradiction between the combinations of the technical features, the scope of the present application should be considered as being described in the present application.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, a controlled terminal, or a network device) to execute the method of each embodiment of the present application.

In the above embodiments, the implementation may be wholly or partially realized 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. The procedures or functions according to the embodiments of the present application are all or partially generated when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, 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 wire (e.g., coaxial cable, fiber optic, digital subscriber line) or wirelessly (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, memory Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

The above description is only a preferred embodiment of the present application, and not intended to limit the scope of the present application, and all modifications of equivalent structures and equivalent processes, which are made by the contents of the specification and the drawings of the present application, or which are directly or indirectly applied to other related technical fields, are included in the scope of the present application.

Claims

1. A processing method is applied to a terminal device, and comprises the following steps:

determining or generating a random access preamble when randomly accessing; wherein the random access preamble comprises a device type identifier;

2. The method of claim 1, wherein the device type identifier is located in a guard interval in the random access preamble.

3. The method of claim 2, wherein the device type identifier is located in a specified resource unit of the guard interval.

4. The method according to any of claims 1 to 3, wherein the random access preamble comprises at least one of:

a first portion of random access preamble codes;

a second portion of random access preamble;

a third portion of the random access preamble.

5. The method of claim 4, further comprising at least one of:

6. The method according to any of claims 1 to 3, wherein the number of random access preambles is 64; and/or the sending the random access preamble comprises: transmitting the random access preamble through a random access channel.

7. The method according to any one of claims 1 to 3, further comprising:

8. The method of claim 7, wherein the determining whether to determine or generate the random access preamble according to the network-side scheduling information comprises at least one of:

and if the terminal equipment has the capacity of the light capacity equipment and the capacity of the common equipment, the terminal equipment accesses the network by the capacity of the common equipment, and the network side scheduling information represents that the light capacity equipment is not allowed to access and the common equipment is allowed to access, determining or generating the random access lead code.

9. A processing method is applied to a terminal device, and comprises the following steps:

10. The method of claim 9, comprising at least one of:

the type of the terminal equipment comprises at least one of the following types: light-duty equipment, general equipment;

the network side scheduling information comprises information whether the light capacity equipment is allowed to access;

the device type identifier is located in a guard interval in the random access preamble;

the random access preamble is determined or generated at random access.

11. The method of claim 9, wherein the sending the random access preamble comprises:

transmitting the random access preamble through a random access channel.

12. The method according to any one of claims 9 to 11, further comprising:

and receiving network side scheduling information, wherein the network side scheduling information comprises information whether the light capacity equipment is allowed to access.

13. The method of claim 12, wherein the determining the transmission policy of the random access preamble according to the network-side scheduling information and the type of the terminal device comprises at least one of:

if the terminal device has the capabilities of the light-weight capability device and the capabilities of the common device, the terminal device accesses the network by the capabilities of the common device, and the network side scheduling information represents that the light-weight capability device is not allowed to access and the common device is allowed to access, the sending strategy is to determine or generate the random access preamble, and the random access preamble is sent.

14. The method according to any of claims 9 to 11, wherein the random access preamble comprises at least one of:

a first portion of random access preamble codes;

a second portion of random access preamble;

a third portion of the random access preamble.

15. The method of claim 14, further comprising at least one of:

16. A processing method applied to a network device, the method comprising:

receiving a random access lead code sent by terminal equipment; wherein the random access preamble comprises a device type identifier;

17. The method of claim 16, wherein the device type identifier is located in a guard interval in the random access preamble.

18. The method of claim 16, wherein the random access preamble comprises at least one of:

a first portion of random access preamble codes;

a second portion of random access preamble;

a third portion of the random access preamble.

19. The method of claim 18, further comprising at least one of:

20. The method according to any one of claims 16 to 19, further comprising: and broadcasting network side scheduling information, wherein the network side scheduling information comprises information about whether the light capacity equipment is allowed to access, so that the terminal equipment receiving the network side scheduling information determines whether to determine or generate the random access preamble according to the network side scheduling information.

21. 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.

22. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the method according to any one of claims 1 to 20.