CN116582231B

CN116582231B - Processing method, communication device and storage medium

Info

Publication number: CN116582231B
Application number: CN202310849147.7A
Authority: CN
Inventors: 王沙; 谢毅力; 黄伟
Original assignee: Shenzhen Transsion Holdings Co Ltd
Current assignee: Shenzhen Transsion Holdings Co Ltd
Priority date: 2023-07-12
Filing date: 2023-07-12
Publication date: 2023-12-22
Anticipated expiration: 2043-07-12
Also published as: CN116582231A

Abstract

The application discloses a processing method, communication equipment and storage medium, wherein the processing method comprises the following steps: and the terminal equipment determines the frequency domain resource occupied by the Msg3 PUSCH according to the preset field. According to the technical scheme, enough bits in the random access response uplink grant can be guaranteed to be used as the frequency domain resource allocation of the Msg3 PUSCH, and further the flexibility and/or the frequency hopping performance of the frequency domain resource allocation of the terminal equipment with the enhanced light capacity are guaranteed.

Description

Processing method, communication device and storage medium

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a processing method, a communications device, and a storage medium.

Background

According to the existing protocol, when the frequency-domain hopping of the PUSCH (Physical UplinkSharedCHannel ) of the Msg3 (message 3) is enabled, the 1-2 bits of the most significant bit of the PUSCH frequency resource allocation (frequency-domain resource allocation) field in the UL grant (RAR (Random AccessResponse, random access response) will be used as the hopping bits of the PUSCH of the Msg 3; i.e. only the remaining L bits (l=14-number of hopping bits) in the PUSCH frequency resource allocation field are used as PUSCH frequency domain resource allocation bits.

In the course of conception and implementation of the present application, the inventors found that: if the most significant 2 bits of the PUSCH frequency resource allocation field in the RAR UL grant are used as the hopping bits for the Msg3 PUSCH, only the remaining 14-2=12 bits in the PUSCH frequency resource allocation field are available for frequency domain resource allocation for R18 eRedcap UEs (R18 enhanced lightweight capability terminal devices). In other words, taking the example of a subcarrier spacing of 15KHz, about 20 RBs (Resource Block) out of 106 RBs corresponding to the 20MHz bandwidth portion cannot be used for PUSCH frequency domain Resource allocation of R18 eredcapuce. Therefore, the above-described manner of determining the frequency domain resource allocation bits may cause a problem that the available resources for Msg3 PUSCH frequency domain hopping of the R18 eRedcap UE are limited. Especially when the R18 eRedCap, rel-17 RedCap UE or the legacy UE coexist in the same cell, the problem of limited available resources for frequency hopping of the R18 eRedCap UE frequency domain is further aggravated.

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

Disclosure of Invention

The main objective of the present application is to provide a processing method, a communication device, and a storage medium, so as to solve the problem that when Msg3 PUSCH frequency hopping is enabled, available frequency domain resources of Msg3 PUSCH frequency hopping of R18 eRedcap UE are limited due to a smaller number of available bits of frequency domain resource allocation of Msg3 PUSCH.

The application provides a processing method, which can be applied to terminal equipment (such as a mobile phone), and comprises the following steps:

s2, determining the frequency domain resource occupied by the Msg3 PUSCH based on the preset field.

Optionally, the preset field includes at least one of:

a channel state information request field in a random access response uplink grant;

the random access response is an uplink grant in which the physical uplink shared channel frequency domain resource allocation field is used.

Optionally, the random access response is a random access response in Msg2 (message 2) in 4-step random access or a fallback random access response in MsgB (message B) in 2-step random access.

Optionally, the 4-step random access corresponds to Type-1 (Type 1) random access; the 2-step random access corresponds to Type-2 (Type 2) random access.

Optionally, the step S2 includes the steps of:

s20, determining a frequency hopping indication bit of the Msg3 PUSCH based on a preset field;

s21: and determining the frequency domain resource occupied by the Msg3 PUSCH based on the frequency hopping indication bit determination result.

Optionally, the step S20 includes at least one of the following:

when the bandwidth part size is smaller than 50 PRBs (Physical Resource Block ), using a channel state information request field in the random access response uplink grant as an Msg3 PUSCH frequency hopping indication bit;

When the bandwidth part size is smaller than 50 PRBs, using the most significant 1 bit in a physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant as an Msg3PUSCH frequency hopping indication bit;

when the bandwidth part size is smaller than 50 PRBs, using the lowest bit 1 bit in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant as an Msg3PUSCH frequency hopping indication bit;

when the bandwidth part size is greater than or equal to 50 PRB, the highest bit 1 bit in the channel state information request field in the random access response uplink grant and the physical uplink shared channel frequency domain resource allocation field jointly form 2 bits to be used as Msg3PUSCH frequency hopping indication bits;

when the bandwidth part size is greater than or equal to 50 PRB, the channel state information request field in the random access response uplink grant and the lowest bit 1 bit in the physical uplink shared channel frequency domain resource allocation field jointly form 2 bits to be used as Msg3PUSCH frequency hopping indication bits;

when the bandwidth part size is greater than or equal to 50 PRBs, the most significant 2 bits in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant are used as Msg3PUSCH frequency hopping indication bits.

Optionally, the step S21 includes at least one of the following:

when the lowest bit 1 bit fixed reservation in the physical uplink shared channel frequency domain resource allocation field is used as a frequency hopping indication bit, determining the frequency domain resource occupied by the Msg3 PUSCH based on the highest bit or the lowest bit X bit in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant;

when the most significant 1 bit fixed reservation in the physical uplink shared channel frequency domain resource allocation field is used as a frequency hopping indication bit, determining the frequency domain resource occupied by the Msg3 PUSCH based on the most significant or least significant X bits in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant;

when the highest 1 bit in the physical uplink shared channel frequency domain resource allocation field is used as a frequency hopping indication bit when the frequency domain frequency hopping identification is 1 and can also be used for determining the frequency domain resource occupied by the Msg3 PUSCH when the frequency domain frequency hopping identification is 0, determining the frequency domain resource occupied by the Msg3 PUSCH based on the highest or lowest X bit after the frequency hopping indication bit of the Msg3 PUSCH in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant;

When the lowest bit 1 bit in the physical uplink shared channel frequency domain resource allocation field is used as a frequency hopping indication bit when the frequency domain frequency hopping flag is 1 and can also be used for determining the frequency domain resource occupied by the Msg3 PUSCH when the frequency domain frequency hopping flag is 0, determining the frequency domain resource allocation of the Msg3 PUSCH based on the highest bit or the lowest bit X bit in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant.

Optionally, X is a natural number.

Optionally, the frequency hopping includes inter-slot frequency hopping or intra-slot frequency hopping.

The application also provides a processing method, which can be applied to network equipment (such as a base station), and comprises the following steps:

s1, sending a random access response so that the terminal equipment determines the frequency domain resource occupied by the Msg3 PUSCH according to the preset field in the random access response.

Optionally, the preset field includes at least one of:

Optionally, the random access response is a random access response in Msg2 in 4-step random access or a fallback random access response in MsgB in 2-step random access.

Optionally, the 4-step random access corresponds to Type-1 (Type 1) random access.

Alternatively, the 2-step random access corresponds to Type-2 (Type 2) random access.

Optionally, the determining, by the terminal device, the frequency domain resource occupied by the Msg3 PUSCH according to the preset field in the random access response includes:

the terminal equipment determines a frequency hopping indication bit of the Msg3 PUSCH based on a preset field in the random access response;

and the terminal equipment determines the frequency domain resource occupied by the Msg3 PUSCH based on the frequency hopping indication bit determination result.

Optionally, the terminal device determines the Msg3 PUSCH frequency hopping indication bit according to a preset field in the random access response, including at least one of the following:

when the bandwidth part size is smaller than 50 PRBs, using a channel state information request field in random access response uplink grant as an Msg3 PUSCH frequency hopping indication bit;

when the bandwidth part size is smaller than 50 PRBs, using the most significant 1 bit in a physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant as an Msg3 PUSCH frequency hopping indication bit;

when the bandwidth part size is smaller than 50 PRBs, using the lowest bit 1 bit in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant as an Msg3 PUSCH frequency hopping indication bit;

When the bandwidth part size is greater than or equal to 50 PRB, the highest bit 1 bit in the channel state information request field in the random access response uplink grant and the physical uplink shared channel frequency domain resource allocation field jointly form 2 bits to be used as Msg3 PUSCH frequency hopping indication bits;

when the bandwidth part size is greater than or equal to 50 PRB, the channel state information request field in the random access response uplink grant and the lowest bit 1 bit in the physical uplink shared channel frequency domain resource allocation field jointly form 2 bits to be used as Msg3 PUSCH frequency hopping indication bits;

when the bandwidth part size is greater than or equal to 50 PRBs, the most significant 2 bits in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant are used as Msg3 PUSCH frequency hopping indication bits.

Optionally, the determining, by the terminal device, the frequency domain resource occupied by the Msg3 PUSCH based on the result of determining the frequency hopping indication bit includes at least one of the following:

Optionally, X is a natural number.

The application also provides a processing device, comprising:

and the determining module is used for determining the frequency domain resource occupied by the Msg3 PUSCH based on the preset field.

The application also proposes a processing device comprising:

and the sending module is used for sending the random access response so that the terminal equipment determines the frequency domain resource occupied by the Msg3 PUSCH according to the preset field in the random access response.

The present application also provides a communication device comprising: the system comprises a memory, a processor and a processing program stored in the memory and capable of running on the processor, wherein the processing program realizes the processing method when being executed by the processor. The communication device mentioned in the present application may be a terminal device (such as an intelligent terminal, specifically, a mobile phone), or may be a network device (such as a base station), which specifically refers to a device that needs to be explicitly combined with the context.

The present application also provides a storage medium having stored thereon a computer program which, when executed by a processor, implements a processing method as described in any of the embodiments above.

According to the technical scheme, the terminal equipment determines the frequency domain resources occupied by the Msg3 PUSCH according to the preset field, so that enough bits in the random access response uplink grant can be ensured to be used as the frequency domain resource allocation of the Msg3 PUSCH, and further the flexibility and/or the frequency hopping performance of the frequency hopping domain resource allocation of the terminal equipment with the enhanced light capacity are ensured.

Drawings

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

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

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

fig. 3 is a schematic hardware structure of the controller 140 according to an embodiment of the processing method of the present application;

fig. 4 is a schematic hardware structure of a network node 150 according to an embodiment of the processing method of the present application;

Fig. 5 is a schematic diagram of an interaction flow between a terminal device and a network device according to a first embodiment of the processing method of the present application;

FIG. 6 is a schematic diagram of a 4-step random access procedure according to a third embodiment of the processing method of the present application;

fig. 7 to fig. 10 are explanatory diagrams of a physical uplink shared channel frequency domain resource allocation field in a random access response uplink grant in the first scenario in the third embodiment of the processing method of the present application;

fig. 11 to fig. 12 are explanatory views of a physical uplink shared channel frequency domain resource allocation field in a random access response uplink grant in a second scenario in a third embodiment of the processing method of the present application;

fig. 13 to fig. 14 are explanatory views of a physical uplink shared channel frequency domain resource allocation field in a random access response uplink grant in a second scenario in a third embodiment of the processing method of the present application;

fig. 15 to fig. 18 are explanatory diagrams of a physical uplink shared channel frequency domain resource allocation field in a random access response uplink grant in the first scenario in the fourth embodiment of the processing method of the present application;

fig. 19 to fig. 20 are explanatory diagrams of a physical uplink shared channel frequency domain resource allocation field in a random access response uplink grant in the second scenario in the fourth embodiment of the processing method of the present application;

Fig. 21 to fig. 22 are explanatory diagrams of a physical uplink shared channel frequency domain resource allocation field in a random access response uplink grant in a third scenario in a fourth embodiment of the processing method of the present application;

FIG. 23 is a schematic flow chart of a 2-step random access procedure in an embodiment of the processing method of the present application;

fig. 24-26 are explanatory diagrams of a physical uplink shared channel frequency domain resource allocation field in a random access response uplink grant in a seventh embodiment of the processing method of the present application.

The realization, functional characteristics and advantages of the present application will be further described with reference to the embodiments, referring to the attached drawings. Specific embodiments thereof have been shown by way of example in the drawings and will herein be described in more detail. These drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments.

Detailed Description

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

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

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

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

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

It should be noted that, in this document, step numbers such as S10 and S20 are adopted, and the purpose of the present invention is to more clearly and briefly describe the corresponding content, and not to constitute a substantial limitation on the sequence, and those skilled in the art may execute S20 first and then execute S10 when implementing the present invention, which is within the scope of protection of the present application.

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

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

The communication device mentioned in the present application may be a terminal device (such as a mobile terminal, specifically, a mobile phone), or may be a network device (such as a base station), and specifically, the reference needs to be explicitly combined with the context.

Alternatively, the terminal device may be implemented in various forms. For example, the terminal devices described in the present application may include smart terminals such as cell phones, tablet computers, notebook computers, palm computers, personal digital assistants (Personal Digital Assistant, PDA), portable media players (Portable Media Player, PMP), navigation devices, wearable devices, smart bracelets, pedometers, and stationary terminals such as digital TVs, desktop computers, and the like.

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

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

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

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

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

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

The a/V input unit 104 is used to receive an audio or video signal. The a/V input unit 104 may include a graphics processor (Graphics Processing Unit, GPU) 1041 and a microphone 1042, the graphics processor 1041 processing 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 graphics processor 1041 may be stored in the memory 109 (or other storage medium) or transmitted via the radio frequency unit 101 or the WiFi module 102. The microphone 1042 can receive sound (audio data) via the microphone 1042 in a phone call mode, a recording mode, a voice recognition mode, and the like, and can process such sound into audio data. The processed audio (voice) data may be converted into a format output that can be transmitted to the mobile communication base station via the radio frequency unit 101 in the case of a telephone call mode. The microphone 1042 may implement various types of noise cancellation (or suppression) algorithms to cancel (or suppress) noise or interference generated in the course of receiving and transmitting the audio signal.

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

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

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

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

The interface unit 108 serves as an interface through which at least one external device can be connected with the mobile terminal 100. For example, the external devices may include a wired or wireless headset port, an external power (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 an external device and transmit the received input to one or more elements within the mobile terminal 100 or may be used to transmit data between the mobile terminal 100 and an external device.

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

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

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

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

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

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

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

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

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

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

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

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

Fig. 3 is a schematic hardware structure of the controller 140 provided in the present application. The controller 140 includes: the memory 1401 and the processor 1402, the memory 1401 is configured to store program instructions, and the processor 1402 is configured to invoke the program instructions in the memory 1401 to execute the steps executed by the controller in the first embodiment of the method, so that the implementation principle and the beneficial effects are similar, and no further description is given here.

Optionally, the controller further comprises a communication interface 1403, which communication interface 1403 may be connected to the processor 1402 via a bus 1404. The processor 1402 may control the communication interface 1403 to implement the functions of receiving and transmitting of the controller 140.

Fig. 4 is a schematic hardware structure of a network node 150 provided in the present application. The network node 150 comprises: the memory 1501 and the processor 1502, the memory 1501 is configured to store program instructions, and the processor 1502 is configured to invoke the program instructions in the memory 1501 to execute the steps executed by the first node in the first embodiment of the method, so that the implementation principle and the beneficial effects are similar, and no further description is given here.

Optionally, the controller further includes a communication interface 1503, where the communication interface 1503 may be connected to the processor 1502 through a bus 1504. The processor 1502 may control the communication interface 1503 to implement the functionality of receiving and transmitting of the network node 150.

The integrated modules, which are implemented in the form of software functional modules, may be stored in a computer readable storage medium. The software functional module is stored in a storage medium, and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (english: processor) to perform some steps of the methods of the embodiments of the present application.

Technical terms related to this embodiment:

PUSCH, physical Uplink Shared CHannel, physical uplink shared channel;

RAR, random Access Response, random access response;

fallback RAR, fallback Random Access Response, fallback random access response;

UL grant, upLink grant;

PUSCH frequency resource allocation physical uplink shared channel frequency domain resource allocation;

r18 eRedCap UE, R18 enhanced lightweight capability terminal equipment.

First embodiment

Referring to fig. 5, a first embodiment of the present application proposes a processing method, including the steps of:

s1, the network equipment sends a random access response so that the terminal equipment determines the frequency domain resource occupied by the Msg3 PUSCH according to the preset field in the random access response.

S2, the terminal equipment determines the frequency domain resource occupied by the Msg3 PUSCH based on the preset field.

Optionally, the network device sends a random access response, and the terminal device determines the frequency domain resource occupied by the Msg3 PUSCH based on a preset field in the uplink grant of the random access response.

Optionally, the preset field includes at least one of:

Alternatively, the preset field in the random access response uplink grant may refer to the uplink grant definition in the random access response of table 1 below.

Table 1, random access response grant content domain size

Optionally, the random access response is a random access response in Msg2 in a 4-step random access.

Optionally, the random access response is a fallback random access response in MsgB in a 2-step random access.

Optionally, the step S2 includes the steps of:

s20, determining a frequency hopping indication bit of the Msg3PUSCH based on a preset field;

s21: and determining the frequency domain resource occupied by the Msg3PUSCH based on the frequency hopping indication bit determination result.

Alternatively, the relation of the hopping indication bits and the second hopping frequency domain resource of the Msg3PUSCH may be defined with reference to table 2.

TABLE 2 frequency domain offset of the second hop frequency for PUSCH Transmission by RAR UL grant or Msg3PUSCH retransmission scheduling hop frequency

Optionally, the step S20 includes at least one of the following:

when the bandwidth part size is smaller than 50 PRBs, using a channel state information request field in random access response uplink grant as an Msg3PUSCH frequency hopping indication bit;

Optionally, the terminal device determines the frequency domain resource occupied by the Msg3 PUSCH based on the above-mentioned frequency hopping indication bit determination result.

In the technical scheme of the embodiment, the terminal equipment determines the frequency domain resource occupied by the Msg3 PUSCH according to the preset field. The method can ensure that enough bits in the random access response uplink grant are used as the frequency domain resource allocation of the Msg3 PUSCH, thereby ensuring the flexibility and/or the frequency hopping performance of the frequency domain resource allocation of the terminal equipment with enhanced light capacity.

Second embodiment

Based on the above embodiments, a second embodiment of the present application proposes a processing method, where a network device sends a random access response, and a terminal device determines, according to a preset field in the random access response, a frequency domain resource occupied by an Msg3 PUSCH.

Optionally, the preset field includes at least one of:

Alternatively, the preset field in the random access response uplink grant may be as shown in table 1 above.

Optionally, the determining, by the terminal device, the frequency domain resource occupied by the Msg3 PUSCH based on the preset field includes the steps of:

Optionally, the step S20 includes at least one of the following:

Optionally, the terminal device determines the frequency domain resource occupied by the Msg3PUSCH based on the above-mentioned frequency hopping indication bit determination result.

Optionally, the step S21 includes at least one of the following:

Optionally, X is a natural number.

The frequency domain resource allocation in the two scenarios where the frequency domain hopping flag (Frequency hopping flag) is 0 and 1 is described in detail below in conjunction with tables 1 and 2.

Alternatively, when the frequency domain hopping flag is '1', there are several scenarios as follows:

first scenario:

alternatively, when the frequency hopping flag is '1' and the bandwidth part size is smaller than 50 PRBs, i.e.When, 1 bit of a channel state information request (CSI request) field in a random access response uplink grant (RAR ULgrant) is used as an Msg3 PUSCH frequency hopping indication bit.

Alternatively, when the frequency domain hopping flag is '1' and the bandwidth part size is greater than or equal to 50 PRBs, the channel state information request field in the random access response uplink grant and the lowest-order 1 bit in the physical uplink shared channel frequency domain resource allocation field together constitute 2 bits to be used as the Msg3 PUSCH hopping indication bit.

Alternatively, when the frequency domain hopping flag is '1', the frequency domain resource allocation of the Msg3 PUSCH may be determined by the most significant X bits in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant.

Optionally, one implementation is: when the bandwidth part size is smaller than 50 PRBs, all bits from the most significant bit in the frequency domain resource allocation field of the physical uplink shared channel in the random access response uplink grant can be used for determining the frequency domain resource allocation of the Msg3 PUSCH according to the bandwidth part size; when the bandwidth part size is greater than or equal to 50 PRBs, other bits except the last 1 bit from the most significant bit in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant can be used to determine the frequency domain resource allocation of the Msg3 PUSCH according to the bandwidth part size.

Alternatively, another implementation is: when the bandwidth part size is less than 50 PRBs or when the bandwidth part size is greater than or equal to 50 PRBs, determining the frequency domain resource allocation of the Msg3 PUSCH according to the bandwidth part size using other bits excluding the last 1 bit from the most significant bit in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant.

Alternatively, when the frequency domain hopping flag is '1' and the bandwidth part size is greater than or equal to 50 PRBs, the channel state information request field in the random access response uplink grant and the most significant 1 bit in the physical uplink shared channel frequency domain resource allocation field together constitute 2 bits to be used as the Msg3 PUSCH hopping indication bit.

Alternatively, when the frequency domain hopping flag is '1', the frequency domain resource allocation of the Msg3 PUSCH may be determined by the least significant X bits in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant.

Optionally, one implementation is: when the bandwidth part size is smaller than 50 PRBs, all bits from the lowest bit in the frequency domain resource allocation field of the physical uplink shared channel in the random access response uplink grant can be used for determining the frequency domain resource allocation of the Msg3 PUSCH according to the bandwidth part size; when the bandwidth part size is greater than or equal to 50 PRBs, other bits except the most significant 1 bit from the least significant 1 bit in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant can be used to determine the frequency domain resource allocation of the Msg3 PUSCH according to the bandwidth part size.

Alternatively, another implementation is: when the bandwidth part size is less than 50 PRBs or when the bandwidth part size is greater than or equal to 50 PRBs, determining the frequency domain resource allocation of the Msg3 PUSCH according to the bandwidth part size using other bits excluding the most significant 1 bit from the least significant bits in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant.

Optionally, one implementation is: when the bandwidth part size is smaller than 50 PRBs, all bits from the most significant bit in the frequency domain resource allocation field of the physical uplink shared channel in the random access response uplink grant can be used for determining the frequency domain resource allocation of the Msg3 PUSCH according to the bandwidth part size; when the bandwidth part size is greater than or equal to 50 PRBs, all bits from the second most significant bit in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant can be used to determine the frequency domain resource allocation of the Msg3 PUSCH according to the bandwidth part size.

Alternatively, another implementation is: when the bandwidth part size is less than 50 PRBs or when the bandwidth part size is greater than or equal to 50 PRBs, determining the frequency domain resource allocation of the Msg3 PUSCH according to the bandwidth part size using all bits from the second most significant bit in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant.

Alternatively, the frequency domain resource allocation of the Msg3 PUSCH may be determined by the least significant X bits in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant

Optionally, one implementation is: when the bandwidth part size is smaller than 50 PRBs, all bits from the lowest bit in the frequency domain resource allocation field of the physical uplink shared channel in the random access response uplink grant can be used for determining the frequency domain resource allocation of the Msg3 PUSCH according to the bandwidth part size; when the bandwidth part size is greater than or equal to 50 PRBs, other bits except the last 1 bit in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant can be used to determine the frequency domain resource allocation of the Msg3 PUSCH according to the bandwidth part size.

Alternatively, another implementation is: when the bandwidth part size is smaller than 50 PRBs or when the bandwidth part size is greater than or equal to 50 PRBs, determining the frequency domain resource allocation of the Msg3 PUSCH according to the bandwidth part size by using other bits except the last 1 bits from the lowest bits in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant.

The second scenario:

alternatively, when the frequency domain hopping flag is '1' and the bandwidth part size is less than 50 PRBs, the most significant 1 bit in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant is used as the Msg3 PUSCH hopping indication bit.

Alternatively, when the frequency domain hopping flag is '1', the frequency domain resource allocation of the Msg3 PUSCH may be determined by the most significant X bits after the Msg3 PUSCH hopping indication bit in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant.

Optionally, one implementation is: all bits from the second most significant bit in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant can be used to determine the frequency domain resource allocation of the Msg3PUSCH according to the bandwidth part size.

Alternatively, when the frequency domain hopping flag is '1' and the bandwidth part size is greater than or equal to 50 PRBs, the channel state information request field in the random access response uplink grant and the most significant 1 bit in the physical uplink shared channel frequency domain resource allocation field together constitute 2 bits to be used as the Msg3PUSCH hopping indication bit.

Alternatively, when the frequency domain hopping flag is '1', the frequency domain resource allocation of the Msg3PUSCH may be determined by the least significant X bits after the Msg3PUSCH hopping indication bit in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant.

Optionally, one implementation is: other bits of the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant, excluding the most significant 1 bit, can be used to determine the frequency domain resource allocation of the Msg3PUSCH according to the bandwidth part size.

Third scenario:

alternatively, when the frequency domain hopping flag is '1' and when the bandwidth part size is less than 50 PRBs, the lowest order 1 bit in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant is used as the Msg3 PUSCH hopping indication bit.

Optionally, one implementation is: other bits except the last 1 bit from the most significant bit in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant can be used to determine the frequency domain resource allocation of the Msg3 PUSCH according to the bandwidth part size.

Alternatively, the frequency domain resource allocation of the Msg3 PUSCH may be determined by the least significant X bits starting from the least significant bit in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant.

Alternatively, another implementation is: other bits except the last 1 bit in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant from the lowest bit can be used to determine the frequency domain resource allocation of the Msg3 PUSCH according to the bandwidth part size.

Optionally, when the frequency domain hopping flag is '0', according to the determining manner of the different hopping indication bits in the first to third scenarios when the frequency domain hopping flag is '1', 1 bit may be fixedly reserved in the physical uplink shared channel frequency domain resource allocation field to be used as the hopping indication bit, and all other remaining bits except the 1 bit in the physical uplink shared channel frequency domain resource allocation field to be used as the hopping indication bit are selected to be the highest-order or lowest-order X bits according to the bandwidth part size of the Msg3 PUSCH to be used for determining the frequency domain resource of the Msg3 PUSCH.

Alternatively, the fixedly reserved 1 bit may be located at the most significant 1 bit or the least significant 1 bit of the physical uplink shared channel frequency domain resource allocation field.

Optionally, according to the determination mode of different frequency hopping indication bits in the first to third scenarios when the frequency domain frequency hopping identifier is '1', 1 bit may be selected as needed in the frequency domain resource allocation field of the physical uplink shared channel to be used as the frequency hopping indication bit. When the frequency-domain hopping flag is '0', all bits in the physical uplink shared channel frequency-domain resource allocation field can be used to determine the frequency-domain resource of the Msg3 PUSCH.

Optionally, according to the bandwidth part size of the Msg3 PUSCH, the most significant or least significant X bits in the physical uplink shared channel frequency domain resource allocation field may be selected to determine the frequency domain resource of the Msg3 PUSCH.

Optionally, when the frequency domain hopping flag is '1' and the bandwidth part size is less than 50 PRBs, using the highest 1 bit in the physical uplink shared channel frequency domain resource allocation field as the Msg3 PUSCH hopping indication bit; the most significant X bits after using the frequency hopping indication bits in the physical uplink shared channel frequency domain resource allocation field are used as frequency domain resource allocation bits for the Msg3 PUSCH.

Alternatively, when the frequency domain hopping flag is '1' and the bandwidth part size is greater than or equal to 50 PRBs, the highest 2 bits in the physical uplink shared channel frequency domain resource allocation field are used as Msg3 PUSCH hopping indication bits, and the highest X bits after the hopping indication bits in the physical uplink shared channel frequency domain resource allocation field and the channel state information request bits are used together as frequency domain resource allocation bits of Msg3 PUSCH.

Alternatively, when the frequency domain hopping flag is '0', the most significant X bits in the physical uplink shared channel frequency domain resource allocation field are used as the frequency domain resource allocation bits of the Msg3 PUSCH.

Optionally, the X is equal toWherein->The uplink bandwidth part size of Msg3 PUSCH.

Third embodiment

Based on any one of the foregoing embodiments, a third embodiment of the present application proposes a processing method, where a network device sends a random access response, and a terminal device determines, according to a preset field in the random access response, a frequency domain resource occupied by an Msg3 PUSCH.

Optionally, the preset field includes at least one of:

Alternatively, the random access TYPE (ra_type) is set to 4-step random access, i.e., the random access procedure is a TYPE-1 (TYPE 1) random access procedure. Alternatively, a 4-step random access procedure may be shown with reference to fig. 6, the procedure comprising the steps of:

(1) msg1 (message 1): the terminal equipment sends a random access preamble to the network equipment;

(2) msg2 (message 2): the network device sends a random access response to the terminal device, where the RAR (random access response) includes: UL grant (uplink grant), RAPID (Random AccessPreambleIdentity, random access preamble identification), backoff indication (back-off indication), TA (Time advance), etc.;

(3) Msg3 (message 3): the terminal equipment sends a PUSCH to the base station according to the UL grant and TA in the Msg 2;

(4) msg4 (message 4): the network device transmits the contention resolution result to the terminal device.

Alternatively, the definition of uplink grant in random access response in Msg2 is shown in table 1 above.

first scenario:

alternatively, when the frequency hopping flag is '1' and the bandwidth part size is smaller than 50 PRBs, i.e.When 1 bit of the channel state information request field in the random access response uplink grant is used as the Msg3 PUSCH frequency hopping indication bit.

Alternatively, when the channel state information request field has a value of 1, it can be seen from table 2 that the second hopping frequency domain offset of the Msg3 PUSCH isWherein->Is the bandwidth portion size.

Optionally, in one implementation, if the channel state information request field is the most significant bit of the 2-bit frequency hopping bits, the least significant 1 bit in the physical uplink shared channel frequency domain resource allocation field is the least significant bit of the 2-bit frequency hopping bits, and the value of the channel state information request field is '0', and the least significant 1 bit in the physical uplink shared channel frequency domain resource allocation field is '1', then it is known from table 2 that the second frequency hopping domain offset of the Msg3 PUSCH is。

In another implementation, if the channel state information request field is the lowest bit of the 2-bit frequency hopping bits, the physical uplink shared channel frequency domain resource allocation fieldThe second hopping frequency domain offset of the Msg3 PUSCH is known according to table 2 if the lowest 1 bit is the highest bit of the 2-bit hopping frequency bits and the value of the channel state information request field is '0' and the lowest 1 bit in the physical uplink shared channel frequency domain resource allocation field is '1。

Alternatively, the frequency domain resource of the Msg3 PUSCH may be determined by the other most significant X bits excluding the last 1 bit in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant. Alternatively, the lowest 1 bit fixed reservation in the physical uplink shared channel frequency domain resource allocation field is used as the frequency hopping indication bit. Optionally, when the frequency hopping flag is 1 or 0, and/or when the bandwidth part size is greater than, equal to or less than 50 PRBs, only the most significant X bits of other bits except the least significant 1 bit in the physical uplink shared channel frequency domain resource allocation field are selected for determining the frequency domain resource of the Msg3 PUSCH.

Optionally, the PUSCH sub-carrier interval is 15KHz, and the bandwidth is 10MHz, namely=52RB，X==/>For example, =11 bits, the definition of the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant is shown in fig. 7.

Alternatively, the reserved bits in fig. 7 may also be used for physical uplink shared channel frequency domain resource allocation, except that since the existing bandwidth part size is 52RB, there are 2 bits reserved bits in fig. 7. Alternatively, if the bandwidth portion increases, the Msg3 PUSCH frequency domain resource allocation valid bit position in fig. 7 will contain a reserved bit position.

Optionally, in one implementation, if the channel state information request field is the most significant bit of the 2-bit frequency hopping bits, the most significant 1 bit in the physical uplink shared channel frequency domain resource allocation field is the least significant bit of the 2-bit frequency hopping bits, and the value of the channel state information request field is '0', and the most significant 1 bit in the physical uplink shared channel frequency domain resource allocation field is '1', it is known from table 2 that the second frequency hopping domain offset of the Msg3 PUSCH is 。

Alternatively, in another implementation, if the channel state information request field is the lowest bit of the 2-bit frequency hopping bits, the highest bit 1 in the physical uplink shared channel frequency domain resource allocation field is the highest bit of the 2-bit frequency hopping bits, and the value of the channel state information request field is '0', and the highest bit 1 in the physical uplink shared channel frequency domain resource allocation field is '1', then it is known from table 2 that the second frequency hopping domain offset of the Msg3 PUSCH is。

Alternatively, the frequency domain resource of the Msg3 PUSCH may be determined by the other least significant X bits excluding the most significant 1 bit in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant. Alternatively, the most significant 1 bit fixed reservation in the physical uplink shared channel frequency domain resource allocation field is used as the frequency hopping indication bit. Optionally, when the frequency hopping flag is 1 or 0, and/or when the bandwidth part size is greater than, equal to or less than 50 PRBs, only the least significant X bits of other bits except the most significant 1 bit in the physical uplink shared channel frequency domain resource allocation field are selected for determining the frequency domain resource of the Msg3 PUSCH.

Optionally, the PUSCH sub-carrier interval is 15KHz, and the bandwidth is 10MHz, namely=52RB，X==/>For example, =11 bits, the definition of the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant is shown in fig. 8. />

Alternatively, the reserved bits in fig. 8 may also be used for physical uplink shared channel frequency domain resource allocation, except that since the existing bandwidth part size is 52RB, there are 2 bits reserved bits in fig. 8. Alternatively, if the bandwidth portion increases, the Msg3 PUSCH frequency domain resource allocation valid bit position in fig. 8 will contain a reserved bit position.

Alternatively, in another implementation, if the channel state information request field is the least significant bit of the 2-bit frequency hopping bits, the physical methodThe highest 1 bit in the uplink shared channel frequency domain resource allocation field is the highest bit of the 2-bit hopping bit, and the value of the channel state information request field is '0', and the highest 1 bit in the physical uplink shared channel frequency domain resource allocation field is '1', then the second hopping frequency domain offset of the Msg3 PUSCH is known to be according to table 2。

Alternatively, the frequency domain resource of the Msg3 PUSCH may be determined by X bits from the second most significant bit excluding the most significant 1 bit in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant.

Alternatively, the most significant 1 bit fixed reservation in the physical uplink shared channel frequency domain resource allocation field is used as the frequency hopping indication bit. Optionally, when the frequency hopping flag is 1 or 0, and/or when the bandwidth part size is greater than, equal to or less than 50 PRBs, only the most significant X bits from the second most significant bit in the physical uplink shared channel frequency domain resource allocation field are selected for determining the frequency domain resource of the Msg3 PUSCH.

Optionally, the PUSCH sub-carrier interval is 15KHz, and the bandwidth is 10MHz, namely=52RB，X==/>For example, =11 bits, the definition of the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant is shown in fig. 9.

Alternatively, the reserved bits in fig. 9 may also be used for physical uplink shared channel frequency domain resource allocation, except that since the existing bandwidth part size is 52RB, there are 2 bits reserved bits in fig. 9. Alternatively, if the bandwidth portion increases, the Msg3 PUSCH frequency domain resource allocation valid bit position in fig. 9 will contain a reserved bit position.

Optionally, in one implementation, if the channel state information request field is the most significant bit of the 2-bit frequency hopping bits, the least significant 1 bit in the physical uplink shared channel frequency domain resource allocation field is the least significant bit of the 2-bit frequency hopping bits, and the value of the channel state information request field is '0', and the least significant 1 bit in the physical uplink shared channel frequency domain resource allocation field is '1', then it is known from table 2 that the second frequency hopping domain offset of the Msg3 PUSCH is 。

Alternatively, in another implementation manner, if the channel state information request field is the lowest bit of the 2-bit frequency hopping bits, the lowest bit 1 bit in the physical uplink shared channel frequency domain resource allocation field is the highest bit of the 2-bit frequency hopping bits, and the value of the channel state information request field is '0', and the lowest bit 1 bit in the physical uplink shared channel frequency domain resource allocation field is '1', then it is known from table 2 that the second frequency hopping domain offset of the Msg3 PUSCH is。/>

Alternatively, the frequency domain resource of the Msg3 PUSCH may be determined by X bits from the second lowest bit excluding the lowest 1 bit in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant. Alternatively, the lowest 1 bit fixed reservation in the physical uplink shared channel frequency domain resource allocation field is used as the frequency hopping indication bit.

Optionally, when the frequency hopping flag is 1 or 0, and/or when the bandwidth part size is greater than, equal to or less than 50 PRBs, only the least significant X bits from the second least significant bit in the physical uplink shared channel frequency domain resource allocation field are selected for determining the frequency domain resource of the Msg3 PUSCH.

With a PUSCH subcarrier spacing of 15KHz and a bandwidth of 10MHz, i.e=52RB，X==/>For example, =11 bits, the definition of the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant is shown in fig. 10.

Alternatively, the reserved bits in fig. 10 may also be used for physical uplink shared channel frequency domain resource allocation, except that since the existing bandwidth part size is 52RB, there are 2 bits reserved bits in fig. 10. Alternatively, if the bandwidth portion increases, the Msg3 PUSCH frequency domain resource allocation valid bit position in fig. 10 will contain a reserved bit position.

The second scenario:

alternatively, when the frequency domain hopping flag is '1' and the bandwidth part size is less than 50 PRBs, the highest 1 bit in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant is used as the Msg3 PUSCH hopping indication bit.

Alternatively, when the most significant 1 bit in the physical uplink shared channel frequency domain resource allocation field is 0, the second hopping frequency domain offset of the Msg3 PUSCH is as follows from table 2Wherein->Is the bandwidth portion size.

Optionally, in one implementation, if the channel state information request field is the most significant bit of the 2-bit frequency hopping bits, the most significant 1 bit in the physical uplink shared channel frequency domain resource allocation field is the least significant bit of the 2-bit frequency hopping bits, and the value of the channel state information request field is '0', and the most significant 1 bit in the physical uplink shared channel frequency domain resource allocation field is '1', it is known from table 2 that the second frequency hopping domain offset of the Msg3 PUSCH is。

Optionally, the PUSCH sub-carrier interval is 15KHz, and the bandwidth is 10MHz, namely=52RB，X==/>For example, =11 bits, the definition of the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant is shown in fig. 11.

Alternatively, the reserved bits in fig. 11 may also be used for physical uplink shared channel frequency domain resource allocation, except that since the existing bandwidth part size is 52RB, there are 2 bits reserved bits in fig. 11. Alternatively, if the bandwidth portion increases, the Msg3 PUSCH frequency domain resource allocation valid bit position in fig. 11 will contain a reserved bit position.

Alternatively, the frequency domain resource allocation of the Msg3 PUSCH may be determined by the least significant X bits after the Msg3 PUSCH frequency hopping indication bit in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant; alternatively, the most significant 1 bit fixed reservation in the physical uplink shared channel frequency domain resource allocation field is used as the frequency hopping indication bit. Optionally, when the frequency hopping flag is 1 or 0, and/or when the bandwidth part size is greater than, equal to or less than 50 PRBs, only the least significant X bits of other bits except the most significant 1 bit in the physical uplink shared channel frequency domain resource allocation field are selected for determining the frequency domain resource of the Msg3 PUSCH.

Optionally, the PUSCH sub-carrier interval is 15KHz, and the bandwidth is 10MHz, namely=52RB，X==/>For example, =11 bits, the definition of the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant is shown in fig. 12.

Alternatively, the reserved bits in fig. 12 may also be used for physical uplink shared channel frequency domain resource allocation, except that since the existing bandwidth part size is 52RB, there are 2 bits reserved bits in fig. 12. Alternatively, if the bandwidth portion increases, the Msg3 PUSCH frequency domain resource allocation valid bit position in fig. 12 will contain a reserved bit position.

Third scenario:

alternatively, when the frequency domain hopping flag is '1' and the bandwidth part size is less than 50 PRBs, the lowest order 1 bit in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant is used as the Msg3 PUSCH hopping indication bit.

Alternatively, when the lowest 1 bit in the physical uplink shared channel frequency domain resource allocation field has a value of 0, the second hopping frequency domain offset of the Msg3 PUSCH is as follows from table 2Wherein->Is the bandwidth portion size.

Optionally, when the frequency domain hopping flag is '1' and the bandwidth part size is greater than or equal to 50 PRBs, the channel state information request field in the random access response uplink grant and the lowest-order 1 bit in the physical uplink shared channel frequency domain resource allocation field together form 2 bits to be used as Msg3 PUSCH hopping indication bits;

Optionally, in one implementation, if the channel state information request field is the most significant bit of the 2-bit frequency hopping bits, the least significant 1 bit in the physical uplink shared channel frequency domain resource allocation field is the least significant bit of the 2-bit frequency hopping bits, and the value of the channel state information request field is '0', and the least significant 1 bit in the physical uplink shared channel frequency domain resource allocation field is '1'It can be seen from Table 2 that the second hopping frequency domain offset of the Msg3 PUSCH is。

Alternatively, in another implementation manner, if the channel state information request field is the lowest bit of the 2-bit frequency hopping bits, the lowest bit 1 bit in the physical uplink shared channel frequency domain resource allocation field is the highest bit of the 2-bit frequency hopping bits, and the value of the channel state information request field is '0', and the lowest bit 1 bit in the physical uplink shared channel frequency domain resource allocation field is '1', then it is known from table 2 that the second frequency hopping domain offset of the Msg3 PUSCH is。

Alternatively, the frequency domain resource allocation of the Msg3 PUSCH may be determined by the most significant X bits in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant.

Alternatively, the lowest 1 bit fixed reservation in the physical uplink shared channel frequency domain resource allocation field is used as the frequency hopping indication bit.

Optionally, no matter the frequency domain hopping flag is 1 or 0, and/or no matter the bandwidth part size, only the most significant X bits of other bits except the least significant 1 bit in the physical uplink shared channel frequency domain resource allocation field are selected for determining the frequency domain resource of the Msg3 PUSCH.

Optionally, the PUSCH sub-carrier interval is 15KHz, and the bandwidth is 10MHz, namely=52RB，X==/>For example, =11 bits, the definition of the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant is shown in fig. 13.

Alternatively, the reserved bits in fig. 13 may also be used for physical uplink shared channel frequency domain resource allocation, except that since the existing bandwidth part size is 52RB, there are 2 bits reserved bits in fig. 13. Alternatively, if the bandwidth portion increases, the Msg3 PUSCH frequency domain resource allocation valid bit position in fig. 13 will contain a reserved bit position.

Alternatively, the frequency domain resource allocation of the Msg3 PUSCH may be determined by the least significant X bits from the second least significant bit in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant.

Alternatively, the lowest 1 bit fixed reservation in the physical uplink shared channel frequency domain resource allocation field is used as the frequency hopping indication bit. Optionally, regardless of whether the frequency domain hopping identity is 1 or 0, and/or regardless of the bandwidth part size, only the least significant X bits from the second least significant bit in the physical uplink shared channel frequency domain resource allocation field are selected for determining the frequency domain resources of the Msg3 PUSCH.

Optionally, the PUSCH sub-carrier interval is 15KHz, and the bandwidth is 10MHz, namely=52RB，X==/>For example, =11 bits, the definition of the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant is shown in fig. 14.

Alternatively, the reserved bits in fig. 14 may also be used for physical uplink shared channel frequency domain resource allocation, except that there are 2 bits reserved bits in fig. 14 because the existing bandwidth part size is 52 RB. Alternatively, if the bandwidth portion increases, the Msg3 PUSCH frequency domain resource allocation valid bit position in fig. 14 will contain a reserved bit position.

Optionally, the position of the frequency hopping bit in the frequency domain resource allocation field of the physical uplink shared channel in this embodiment is reserved, and is irrelevant to the size of the bandwidth part and the value of the frequency domain frequency hopping identifier.

For example, in the first, second, and third scenarios described above, the hopping bit positions in the physical uplink shared channel frequency domain resource allocation field (i.e., the positions identified by the mark lines in fig. 7-14) are indicated by the hopping bits in the Msg3 PUSCH frequency domain reserved fixedly. Only the position excluding the Msg3 PUSCH frequency domain hopping bits in the physical uplink shared channel frequency domain resource allocation field can be used as the Msg3 PUSCH frequency domain resource allocation.

Fourth embodiment

Based on any one of the foregoing embodiments, a processing method is provided in a fourth embodiment of the present application, where a network device sends a random access response, and a terminal device determines, according to a preset field in the random access response, a frequency domain resource occupied by an Msg3 PUSCH.

Optionally, the preset field includes at least one of:

Optionally, the ra_type is set to 4-step random access, that is, the random access procedure is a TYPE-1 random access procedure. Alternatively, a 4-step random access procedure may be illustrated with reference to fig. 6, wherein the definition of uplink grant in the random access response in Msg2 (message 2) is as shown in table 1 above.

Alternatively, if the frequency domain hopping flag in the uplink grant in the random access response is 0, all bits in the frequency domain resource allocation field in the random access response uplink grant are available for use as Msg3 PUSCH frequency domain resource allocation.

First scenario:

alternatively, when the frequency domain hopping flag is '1' and the bandwidth part size is less than 50 PRBs, the channel state information request field in the random access response uplink grant is used as the Msg3 PUSCH hopping indication bit.

Alternatively, in another implementation manner, if the channel state information request field is the lowest bit of the 2-bit frequency hopping bits, the lowest bit 1 bit in the physical uplink shared channel frequency domain resource allocation field is the highest bit of the 2-bit frequency hopping bits, and the value of the channel state information request field is '0', and the lowest bit 1 bit in the physical uplink shared channel frequency domain resource allocation field is '1', then it is known from table 2 that the second frequency hopping domain offset of the Msg3 PUSCH is 。

Alternatively, when the frequency domain hopping flag is '0', the lowest 1 bit in the frequency domain resource allocation field in the random access response uplink grant is not used as the hopping indication bit, but is released to be used as the frequency domain resource allocation bit.

Alternatively, when the frequency domain hopping flag is '0', all bits in the frequency domain resource allocation field in the random access response uplink grant are available for use as Msg3 PUSCH frequency domain resource allocation.

Alternatively, when the frequency domain hopping flag is '0', the frequency domain resource allocation of the Msg3 PUSCH may be determined by the most significant X bits in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant.

Optionally, the PUSCH sub-carrier interval is 15KHz, and the bandwidth is 10MHz, namely=52RB，X==/>For example, =11 bits, the definition of the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant is shown in fig. 15.

Fig. 15 is a diagram showing a reserved bit position including "bits used as a hopping indication when a bandwidth part is greater than or equal to 50 PRBs" as compared with fig. 7; alternatively, the reserved bits in fig. 15 may also be used for physical uplink shared channel frequency domain resource allocation, except that since the existing bandwidth part size is 52RB, there are 3 bits reserved bits in fig. 15. Alternatively, if the bandwidth portion increases, the Msg3 PUSCH frequency domain resource allocation valid bit position in fig. 15 will contain a reserved bit position.

Alternatively, in another implementation, if the channel state information request field is the lowest bit of the 2-bit frequency hopping bits, the highest bit 1 in the physical uplink shared channel frequency domain resource allocation field is the highest bit of the 2-bit frequency hopping bits, and the value of the channel state information request field is '0', and the highest bit 1 in the physical uplink shared channel frequency domain resource allocation field is '1', then it is known from table 2 that the second frequency hopping domain offset of the Msg3 PUSCH is 。

Alternatively, when the frequency domain hopping flag is '0', the most significant 1 bit in the frequency domain resource allocation field in the random access response uplink grant is not used as the hopping indication bit, but is released to be used as the frequency domain resource allocation bit.

Alternatively, when the frequency domain hopping flag is '0', the frequency domain resource allocation of the Msg3 PUSCH may be determined by the least significant X bits in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant.

Optionally, the PUSCH sub-carrier interval is 15KHz, and the bandwidth is 10MHz, namely=52RB，X==/>For example, =11 bits, the definition of the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant is shown in fig. 16.

In fig. 16, compared with fig. 8, the reserved bit position contains "bits used as a hopping indication when the bandwidth part is greater than or equal to 50 PRBs".

Alternatively, the reserved bits in fig. 16 may also be used for physical uplink shared channel frequency domain resource allocation, except that since the existing bandwidth part size is 52RB, there are 3 bits reserved bits in fig. 16.

Alternatively, if the bandwidth portion increases, the Msg3 PUSCH frequency domain resource allocation valid bit position in fig. 16 will contain a reserved bit position.

Optionally, in another implementation, the channel state information request field is the lowest bit of the 2-bit frequency hopping bits, the highest bit 1 in the physical uplink shared channel frequency domain resource allocation field is the highest bit of the 2-bit frequency hopping bits, and the value of the channel state information request field is '0', and the highest bit 1 in the physical uplink shared channel frequency domain resource allocation field is '1', then it is known from table 2 that the second frequency hopping frequency domain offset of the Msg3 PUSCH is 。

Alternatively, when the frequency domain hopping flag is '0', the most significant 1 bit in the frequency domain resource allocation field in the random access response uplink grant is not used as the hopping indication bit, but is released to be used as the frequency domain resource allocation bit; alternatively, when the frequency domain hopping flag is '0', all bits in the frequency domain resource allocation field in the random access response uplink grant are available for use as Msg3 PUSCH frequency domain resource allocation. Alternatively, when the frequency domain hopping flag is '0', the frequency domain resource allocation of the Msg3 PUSCH may be determined by the most significant X bits in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant.

Optionally, the PUSCH sub-carrier interval is 15KHz, and the bandwidth is 10MHz, namely=52RB，X==/>For example, =11 bits, the definition of the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant is shown in fig. 17.

In fig. 17, compared with fig. 9, when the "bandwidth part is greater than or equal to 50 PRBs," bits used as a hopping indication "are released as valid bits for allocation of Msg3 PUSCH frequency domain resources when the frequency domain hopping flag is '0'. Alternatively, the reserved bits in fig. 17 may also be used for physical uplink shared channel frequency domain resource allocation, except that since the existing bandwidth part size is 52RB, there are 3 bits reserved bits in fig. 17. Alternatively, if the bandwidth portion increases, the Msg3 PUSCH frequency domain resource allocation valid bit position in fig. 17 will contain a reserved bit position.

In another implementation, if the channel state information request field is the lowest bit of the 2-bit frequency hopping bits, the lowest bit 1 bit in the physical uplink shared channel frequency domain resource allocation field is the highest bit of the 2-bit frequency hopping bits, and the value of the channel state information request field is '0', and the lowest bit 1 bit in the physical uplink shared channel frequency domain resource allocation field is '1', then it is known from table 2 that the second frequency hopping domain offset of the Msg3 PUSCH is 。

Alternatively, when the frequency domain hopping flag is '0', the lowest 1 bit in the frequency domain resource allocation field in the random access response uplink grant is not used as the hopping indication bit, but is released to be used as the frequency domain resource allocation bit. Alternatively, when the frequency domain hopping flag is '0', all bits in the frequency domain resource allocation field in the random access response uplink grant are available for use as Msg3 PUSCH frequency domain resource allocation. Alternatively, when the frequency domain hopping flag is '0', the frequency domain resource allocation of the Msg3 PUSCH may be determined by the least significant X bits in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant.

Optionally, the PUSCH sub-carrier interval is 15KHz, and the bandwidth is 10MHz, namely=52RB，X==/>For example, =11 bits, the definition of the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant is shown in fig. 18.

In fig. 18, compared with fig. 10, when the "bandwidth part is greater than or equal to 50 PRBs," bits used as a hopping indication "are released as valid bits for allocation of Msg3 PUSCH frequency domain resources when the frequency domain hopping flag is '0'. Alternatively, the reserved bits in fig. 18 may also be used for physical uplink shared channel frequency domain resource allocation, except that since the existing bandwidth part size is 52RB, there are 3 bits reserved bits in fig. 18. Alternatively, if the bandwidth portion increases, the Msg3 PUSCH frequency domain resource allocation valid bit position in fig. 18 will contain a reserved bit position.

Second scene of

Optionally, if the most significant 1 bit in the physical uplink shared channel frequency domain resource allocation field is 0, the second hopping frequency domain offset of the corresponding Msg3 PUSCH is。

Alternatively, when the frequency domain hopping flag is '0', the most significant 1 bit in the frequency domain resource allocation field in the random access response uplink grant is not used as the hopping indication bit any more, but is released to be used as the frequency domain resource allocation bit. Alternatively, when the frequency domain hopping flag is '0', all bits in the frequency domain resource allocation field in the random access response uplink grant are available for use as Msg3 PUSCH frequency domain resource allocation. Alternatively, when the frequency domain hopping flag is '0', the frequency domain resource allocation of the Msg3 PUSCH may be determined by the most significant X bits in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant.

Optionally, the PUSCH sub-carrier interval is 15KHz, and the bandwidth is 10MHz, namely=52RB，X==/>For example, =11 bits, the definition of the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant is shown in fig. 19.

In fig. 19, compared with fig. 11, the most significant bit fixedly used as the "hopping bit" can also be used as the Msg3 PUSCH frequency domain allocation valid bit. Alternatively, the reserved bits in fig. 19 may also be used for physical uplink shared channel frequency domain resource allocation, except that since the existing bandwidth part size is 52RB, there are 3 bits reserved bits in fig. 19. Alternatively, if the bandwidth portion increases, the Msg3 PUSCH frequency domain resource allocation valid bit position in fig. 19 will contain a reserved bit position.

Alternatively, when the frequency domain hopping flag is '0', the most significant 1 bit in the frequency domain resource allocation field in the random access response uplink grant is not used as the hopping indication bit, but is released to be used as the frequency domain resource allocation bit. Alternatively, when the frequency domain hopping flag is '0', all bits in the frequency domain resource allocation field in the random access response uplink grant are available for use as Msg3 PUSCH frequency domain resource allocation. Alternatively, when the frequency domain hopping flag is '0', the frequency domain resource allocation of the Msg3 PUSCH may be determined by the least significant X bits in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant.

Optionally, the PUSCH sub-carrier interval is 15KHz, and the bandwidth is 10MHz, namely=52RB，X=/>=/>For example, =11 bits, the definition of the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant is shown in fig. 20.

Fig. 20 compares to fig. 12, the reserved bit positions contain "hopping bits"; alternatively, the reserved bits in fig. 20 may also be used for physical uplink shared channel frequency domain resource allocation, except that since the existing bandwidth part size is 52RB, there are 3 bits reserved bits in fig. 20. Alternatively, if the bandwidth portion increases, the Msg3 PUSCH frequency domain resource allocation valid bit position in fig. 20 will contain a reserved bit position.

Third scenario

Alternatively, when the frequency domain hopping flag is '01' and the bandwidth part size is less than 50 PRBs, the lowest order 1 bit in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant is used as the Msg3 PUSCH hopping indication bit.

Optionally, if the lowest 1 bit in the physical uplink shared channel frequency domain resource allocation field has a value of 0, the second hopping frequency domain offset of the corresponding Msg3 PUSCH is。

Alternatively, when the frequency domain hopping flag is '01' and the bandwidth part size is greater than or equal to 50 PRBs, the channel state information request field in the random access response uplink grant and the lowest-order 1 bit in the physical uplink shared channel frequency domain resource allocation field together constitute 2 bits to be used as the Msg3 PUSCH hopping indication bit.

Optionally, in one implementation, the channel state information request field is the most significant bit of the 2-bit frequency hopping bits, the least significant 1 bit in the physical uplink shared channel frequency domain resource allocation field is the least significant bit of the 2-bit frequency hopping bits, and the value of the channel state information request field is '0', and the least significant 1 bit in the physical uplink shared channel frequency domain resource allocation field is '1', then it is known from table 2 that the second frequency hopping domain offset of the Msg3 PUSCH is。

Alternatively, when the frequency domain hopping flag is '0', the lowest 1 bit in the frequency domain resource allocation field in the random access response uplink grant is not used as the hopping indication bit, but is released to be used as the frequency domain resource allocation bit. Alternatively, when the frequency domain hopping flag is '0', all bits in the frequency domain resource allocation field in the random access response uplink grant are available for use as Msg3 PUSCH frequency domain resource allocation. Alternatively, when the frequency domain hopping flag is '0', the frequency domain resource allocation of the Msg3 PUSCH may be determined by the most significant X bits in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant.

Optionally, the PUSCH sub-carrier interval is 15KHz, bandwidth of 10MHz, i.e=52RB，X==/>For example, =11 bits, the definition of the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant is shown in fig. 21.

In fig. 21, compared with fig. 13, the reserved bit positions contain "hopping bits". Alternatively, the reserved bits in fig. 21 may also be used for physical uplink shared channel frequency domain resource allocation, except that since the existing bandwidth part size is 52RB, there are 3 bits reserved bits in fig. 21. Alternatively, if the bandwidth portion increases, the Msg3 PUSCH frequency domain resource allocation valid bit position in fig. 21 will contain a reserved bit position.

Optionally, the PUSCH sub-carrier interval is 15KHz, and the bandwidth is 10MHz, namely=52RB，X==/>For example, =11 bits, the definition of the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant is shown in fig. 22.

In fig. 22, compared with fig. 14, the most significant bit fixedly used as the "hopping bit" can also be used as the Msg3 PUSCH frequency domain allocation valid bit. Alternatively, the reserved bits in fig. 22 may be used as physical uplink shared channel frequency domain resource allocation, except that since the existing bandwidth part size is 52RB, there are 3 bits reserved bits in fig. 22. Alternatively, if the bandwidth portion increases, the Msg3 PUSCH frequency domain resource allocation valid bit position in fig. 22 will contain a reserved bit position.

Fifth embodiment

Based on any of the foregoing embodiments, a fifth embodiment of the present application provides a processing method, where a network device sends a random access response, and a terminal device determines a frequency domain resource occupied by an Msg3 PUSCH according to a preset field in the random access response.

Optionally, the preset field includes at least one of:

Optionally, the ra_type is set to 2-step random access, that is, the random access procedure is a TYPE-2 random access procedure.

Alternatively, a 2-step random access procedure may be shown with reference to fig. 21, the procedure comprising the steps of:

MsgA (message a): the terminal device sends MsgA to the network device, wherein the MsgA comprises a random access preamble and/or a PUSCH

MsgB (message B): and the network equipment sends the MsgB to the terminal equipment according to the analysis result of the received MsgA, wherein the MsgB can comprise a fallback RAR (fallback random access response) or a success RAR.

Optionally, if the MsgB includes the success RAR, the network device is represented to successfully receive the MsgA, and the terminal device sends HARQ-ACK feedback to the network device.

Alternatively, if the backspace random access response is included in the MsgB, it represents that the network device does not successfully decode the PUSCH part of the MsgA, but successfully decodes the preamble part of the MsgA, and thus, the subsequent terminal device sends the PUSCH part of Msg3 in a similar 4-step to the network device.

Optionally, the uplink grant definition in the fallback random access response in MsgB is also shown in table 1.

Optionally, if the frequency domain frequency hopping flag in the uplink grant in the fallback random access response is 1, the value of the Msg3 PUSCH frequency hopping indication bit may be determined according to the channel state information request field and/or the physical uplink shared channel frequency domain resource allocation field in the uplink grant in the fallback random access response.

first scene

Alternatively, when the domain hopping identity is '1' and the bandwidth part size is smaller than 50 PRBs, i.e.When 1 bit of the channel state information request field in the fallback random access response uplink grant is used as the Msg3 PUSCH frequency hopping indication bit.

Alternatively, when the channel state information request field has a value of 1, it can be seen from table 2 that the second hopping frequency domain offset of the Msg3 PUSCH is Wherein->Is the bandwidth portion size.

Optionally, when the frequency domain hopping flag is '1' and the bandwidth part size is greater than or equal to 50 PRBs, the channel state information request field in the back-off random access response uplink grant and the lowest-order 1 bit in the physical uplink shared channel frequency domain resource allocation field together form 2 bits to be used as the Msg3 PUSCH hopping indication bit.

Alternatively, the frequency domain resource of the Msg3 PUSCH may be determined by the other most significant X bits excluding the last 1 bit in the physical uplink shared channel frequency domain resource allocation field in the fallback random access response uplink grant. Alternatively, the lowest 1 bit fixed reservation in the physical uplink shared channel frequency domain resource allocation field is used as the frequency hopping indication bit. Optionally, no matter the frequency domain hopping flag is 1 or 0, and/or no matter the bandwidth part size, only the most significant X bits of other bits except the least significant 1 bit in the physical uplink shared channel frequency domain resource allocation field are selected for determining the frequency domain resource of the Msg3 PUSCH.

Optionally, the PUSCH sub-carrier interval is 15KHz, and the bandwidth is 10MHz, namely=52RB，X==/>For example, =11 bits, the definition of the physical uplink shared channel frequency domain resource allocation field in the fallback random access response uplink grant is shown in fig. 7.

Optionally, when the frequency domain hopping flag is '1' and the bandwidth part size is greater than or equal to 50 PRBs, the channel state information request field in the backoff random access response uplink grant and the most significant 1 bit in the physical uplink shared channel frequency domain resource allocation field together form 2 bits to be used as the Msg3 PUSCH hopping indication bit.

Optionally, in one implementation, if the channel stateThe information request field is the most significant bit of the 2-bit frequency hopping bits, the most significant bit 1 bit in the physical uplink shared channel frequency domain resource allocation field is the least significant bit of the 2-bit frequency hopping bits, and the channel state information request field is valued at '0', and the most significant bit 1 bit in the physical uplink shared channel frequency domain resource allocation field is valued at '1', then it can be known from table 2 that the second frequency hopping frequency domain offset of the Msg3 PUSCH is。

Alternatively, the frequency domain resource of the Msg3 PUSCH may be determined by the other least significant X bits excluding the most significant 1 bit in the physical uplink shared channel frequency domain resource allocation field in the fallback random access response uplink grant. Alternatively, the most significant 1 bit fixed reservation in the physical uplink shared channel frequency domain resource allocation field is used as the frequency hopping indication bit. Optionally, regardless of whether the frequency-domain hopping flag is 1 or 0, and/or regardless of the bandwidth part size, only the least significant X bits of the other bits except the most significant 1 bit in the physical uplink shared channel frequency-domain resource allocation field are selected for determining the frequency-domain resource of the Msg3 PUSCH.

Optionally, the PUSCH sub-carrier interval is 15KHz, and the bandwidth is 10MHz, namely=52RB，X==/>For example, =11 bits, the definition of the physical uplink shared channel frequency domain resource allocation field in the back-off random access response uplink grant is shown in fig. 8.

Alternatively, the frequency domain resource of the Msg3 PUSCH may be determined by X bits from the second most significant bit excluding the most significant 1 bit in the physical uplink shared channel frequency domain resource allocation field in the back-off random access response uplink grant. Alternatively, the most significant 1 bit fixed reservation in the physical uplink shared channel frequency domain resource allocation field is used as the frequency hopping indication bit. Optionally, regardless of whether the frequency domain hopping identity is 1 or 0, and/or regardless of the bandwidth part size, only the most significant X bits from the second most significant bit in the physical uplink shared channel frequency domain resource allocation field are selected for determining the frequency domain resources of the Msg3 PUSCH.

Optionally, the PUSCH sub-carrier interval is 15KHz, and the bandwidth is 10MHz, namely=52RB，X==/>For example, =11 bits, the definition of the physical uplink shared channel frequency domain resource allocation field in the back-off random access response uplink grant is shown in fig. 9.

Optionally, an implementationIn the above, if the channel state information request field is the most significant bit of the 2-bit hopping bits, the least significant 1 bit in the physical uplink shared channel frequency domain resource allocation field is the least significant bit of the 2-bit hopping bits, and the channel state information request field is valued as '0', and the least significant 1 bit in the physical uplink shared channel frequency domain resource allocation field is valued as '1', then it is known from table 2 that the second hopping frequency domain offset of the Msg3 PUSCH is。

Alternatively, the frequency domain resource of the Msg3 PUSCH may be determined by X bits from the second lowest bit excluding the lowest 1 bit in the physical uplink shared channel frequency domain resource allocation field in the back-off random access response uplink grant. Alternatively, the lowest 1 bit fixed reservation in the physical uplink shared channel frequency domain resource allocation field is used as the frequency hopping indication bit. Optionally, regardless of whether the frequency domain hopping identity is 1 or 0, and/or regardless of the bandwidth part size, only the least significant X bits from the second least significant bit in the physical uplink shared channel frequency domain resource allocation field are selected for determining the frequency domain resources of the Msg3 PUSCH.

With a PUSCH subcarrier spacing of 15KHz and a bandwidth of 10MHz, i.e=52RB，X==/>For example, =11 bits, the definition of the physical uplink shared channel frequency domain resource allocation field in the back-off random access response uplink grant is shown in fig. 10.

The second scenario:

alternatively, when the frequency domain hopping flag is '1' and the bandwidth part size is less than 50 PRBs, the most significant 1 bit in the physical uplink shared channel frequency domain resource allocation field in the fallback random access response uplink grant is used as the Msg3 PUSCH hopping indication bit.

Optionally, in one implementation, if the channel state information request field is the most significant bit of the 2-bit frequency hopping bits, the most significant bit 1 bit in the physical uplink shared channel frequency domain resource allocation field is the least significant bit of the 2-bit frequency hopping bits, and the channel state The information request field has a value of '0', and the most significant 1 bit in the physical uplink shared channel frequency domain resource allocation field has a value of '1', then the second hopping frequency domain offset of the Msg3 PUSCH is known to be according to table 2。

Optionally, the PUSCH sub-carrier interval is 15KHz, and the bandwidth is 10MHz, namely=52RB，X==/>For example, 11 bits, then in the fallback random access response uplink grantThe definition of the physical uplink shared channel frequency domain resource allocation field of (c) is shown in fig. 11.

Alternatively, the frequency domain resource allocation of the Msg3 PUSCH may be determined by the least significant X bits after the Msg3 PUSCH frequency hopping indication bit in the physical uplink shared channel frequency domain resource allocation field in the fallback random access response uplink grant; alternatively, the most significant 1 bit fixed reservation in the physical uplink shared channel frequency domain resource allocation field is used as the frequency hopping indication bit. Optionally, regardless of whether the frequency-domain hopping flag is 1 or 0, and/or regardless of the bandwidth part size, only the least significant X bits of the other bits except the most significant 1 bit in the physical uplink shared channel frequency-domain resource allocation field are selected for determining the frequency-domain resource of the Msg3 PUSCH.

Optionally, the PUSCH sub-carrier interval is 15KHz, and the bandwidth is 10MHz, namely=52RB，X==/>For example, =11 bits, the definition of the physical uplink shared channel frequency domain resource allocation field in the back-off random access response uplink grant is shown in fig. 12.

Third scenario:

optionally, when the frequency domain hopping flag is '1' and the bandwidth part size is less than 50 PRBs, the lowest order 1 bit in the physical uplink shared channel frequency domain resource allocation field in the fallback random access response uplink grant is used as the Msg3 PUSCH hopping indication bit.

Alternatively, in another implementation, if the channel state information request field is the lowest bit of the 2-bit frequency hopping bits, the lowest bit 1 in the physical uplink shared channel frequency domain resource allocation field is the highest bit of the 2-bit frequency hopping bits, and the value of the channel state information request field is '0', the physical uplink shared channelIf the lowest 1 bit in the frequency domain resource allocation field has a value of '1', the second hopping frequency domain offset of the Msg3 PUSCH is known to be according to table 2。

Alternatively, the frequency domain resource allocation of the Msg3 PUSCH may be determined by the most significant X bits in the physical uplink shared channel frequency domain resource allocation field in the fallback random access response uplink grant. Alternatively, the lowest 1 bit fixed reservation in the physical uplink shared channel frequency domain resource allocation field is used as the frequency hopping indication bit. Optionally, no matter the frequency domain hopping flag is 1 or 0, and/or no matter the bandwidth part size, only the most significant X bits of other bits except the least significant 1 bit in the physical uplink shared channel frequency domain resource allocation field are selected for determining the frequency domain resource of the Msg3 PUSCH.

Optionally, the PUSCH sub-carrier interval is 15KHz, and the bandwidth is 10MHz, namely=52RB，X==/>For example, =11 bits, the definition of the physical uplink shared channel frequency domain resource allocation field in the back-off random access response uplink grant is shown in fig. 13.

Alternatively, the frequency domain resource allocation of the Msg3 PUSCH may be determined by the least significant X bits from the second least significant bit in the physical uplink shared channel frequency domain resource allocation field in the fallback random access response uplink grant; alternatively, the lowest 1 bit fixed reservation in the physical uplink shared channel frequency domain resource allocation field is used as the frequency hopping indication bit. Optionally, regardless of whether the frequency domain hopping identity is 1 or 0, and/or regardless of the bandwidth part size, only the least significant X bits from the second least significant bit in the physical uplink shared channel frequency domain resource allocation field are selected for determining the frequency domain resources of the Msg3 PUSCH.

Optionally, the PUSCH sub-carrier interval is 15KHz, and the bandwidth is 10MHz, namely=52RB，X==/>For example, =11 bits, the definition of the physical uplink shared channel frequency domain resource allocation field in the back-off random access response uplink grant is shown in fig. 14.

In the technical scheme of the embodiment, the terminal equipment determines the frequency domain resource occupied by the Msg3PUSCH according to the preset field. The method can ensure that enough bits in the random access response uplink grant are used as the frequency domain resource allocation of the Msg3PUSCH, thereby ensuring the flexibility and/or the frequency hopping performance of the frequency domain resource allocation of the terminal equipment with enhanced light capacity.

Sixth embodiment

Based on any of the foregoing embodiments, a sixth embodiment of the present application provides a processing method, where a network device sends a random access response, and a terminal device determines, according to a preset field in the random access response, a frequency domain resource occupied by an Msg3 PUSCH.

Optionally, the network device sends a random access response, and the terminal device determines the frequency domain resource occupied by the Msg3PUSCH based on a preset field in the uplink grant of the random access response.

Optionally, the preset field includes at least one of:

Optionally, the ra_type is set to 2-step random access, that is, the random access procedure is a TYPE-2 random access procedure. Alternatively, the 2-step random access procedure may be as shown with reference to fig. 23, alternatively the definition of the uplink grant in the fallback random access response in MsgB (message 2) is as shown in table 1 above.

Alternatively, if the frequency domain frequency hopping flag in the uplink grant in the random access response is 0, all bits in the frequency domain resource allocation field in the random access response uplink grant are available for use as Msg3 PUSCH frequency domain resource allocation.

Note that the present embodiment differs from the fourth embodiment described above in that the present embodiment replaces the "random access response" described in the fourth embodiment with a "fallback random access response"; the RAR descriptions in all 4-step random accesses in the fourth embodiment are equally applicable to the fallback random access response in the 2-step random access in this embodiment, and are not described here again.

In the technical scheme of the embodiment, the terminal equipment determines the frequency domain resource occupied by the Msg3 PUSCH according to the preset field. Enough bits in the uplink grant of the rollback random access response can be ensured to be used as the frequency domain resource allocation of the Msg3 PUSCH, and the flexibility and/or the frequency hopping performance of the frequency domain resource allocation of the R18 enhanced light-weight terminal equipment are further ensured.

Seventh embodiment

Based on any one of the foregoing embodiments, a processing method is provided in a seventh embodiment of the present application, where a network device sends a random access response, and a terminal device determines, according to a preset field in the random access response, a frequency domain resource occupied by an Msg3 PUSCH.

Optionally, the preset field includes at least one of:

Alternatively, when the frequency domain hopping flag is '1', and the bandwidth part size is greater than or equal to 50 PRBs, the highest 2 bits in the physical uplink shared channel frequency domain resource allocation field are used as Msg3 PUSCH hopping indication bits, and the highest X bits after the hopping indication bits in the physical uplink shared channel frequency domain resource allocation field and the 1 bits in the channel state information request field are used together as frequency domain resource allocation bits of Msg3 PUSCH.

Optionally, the PUSCH sub-carrier interval is 15KHz, and the bandwidth is 20MHz, namely=106RB，X==/>For example, let frequency domain hopping flag be '1' =13 bits; the fallback random access response or the definition of the physical uplink shared channel frequency domain resource allocation field in the uplink grant in the random access response is as shown in fig. 24.

Optionally, the PUSCH sub-carrier interval is 15KHz, and the bandwidth is 5MHz, namely=25RB，X==/>For example, let the frequency domain hopping flag be '1' =9 bits; the backoff random access response or the definition of the physical uplink shared channel frequency domain resource allocation field in the uplink grant in the random access response is as shown in fig. 25 (at this time, 1 bit in the channel state information request field is still a reserved bit).

Alternatively, when the frequency-domain hopping flag is '0', the most significant X bits in the physical uplink shared channel frequency-domain resource allocation field are used as the frequency-domain resource allocation bits of the Msg3 PUSCH, regardless of whether the bandwidth part size is less than 50 PRBs or the bandwidth part size is greater than or equal to 50 PRBs.

Optionally, the PUSCH sub-carrier interval is 15KHz, and the bandwidth is 20MHz, namely=106RB，X==/>For example, 13 bits, the physical uplink shared channel frequency domain resource allocation field in the fallback random access response or uplink grant in the random access response is interpreted as shown in fig. 26.

The embodiment of the application also provides a processing device applied to or being a terminal device, the device comprising:

Optionally, the preset field includes at least one of:

Optionally, the determining module includes:

a first determining module, configured to determine a frequency hopping indication bit of the Msg3PUSCH based on a preset field;

and the second determining module is used for determining the frequency domain resource occupied by the Msg3PUSCH based on the frequency hopping indication bit determining result.

Optionally, the first determining module is further configured to at least one of:

Optionally, the second determining module is further configured to at least one of:

When the highest 1 bit in the physical uplink shared channel frequency domain resource allocation field is used as a frequency hopping indication bit when the frequency domain frequency hopping identifier is 1, and the highest 1 bit can still be used as a frequency domain resource occupied by the Msg3 PUSCH when the frequency domain frequency hopping identifier is 0, determining the frequency domain resource occupied by the Msg3 PUSCH based on the highest or lowest X bit after the frequency hopping indication bit of the Msg3 PUSCH in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant;

when the lowest bit 1 bit in the physical uplink shared channel frequency domain resource allocation field is used as the frequency hopping indication bit when the frequency domain frequency hopping identifier is 1, the lowest bit 1 bit can still be used as the frequency domain resource occupied by the Msg3 PUSCH when the frequency domain frequency hopping identifier is 0, and the frequency domain resource allocation of the Msg3 PUSCH is determined based on the highest bit or the lowest bit X bit in the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant.

Optionally, X is a natural number.

The embodiment of the application also provides a processing device applied to or being a network device, which comprises:

Optionally, the preset field includes at least one of:

Optionally, X is a natural number.

The embodiment of the application also provides a communication system, which comprises the terminal device described in any one of the embodiments and the network device described in any one of the embodiments.

The embodiment of the application also provides a communication device, which comprises: the system comprises a memory, a processor and a processing program stored in the memory and capable of running on the processor, wherein the processing program is executed by the processor to realize the processing method in any embodiment. The communication device mentioned in the present application may be a terminal device (such as an intelligent terminal, specifically, a mobile phone), or may be a network device (such as a base station), which specifically refers to a device that needs to be explicitly combined with the context.

The present application also provides a storage medium having stored thereon a computer program which, when executed by a processor, implements a processing method as described in any of the above embodiments.

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

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

The embodiments also provide a chip including a memory for storing a computer program and a processor for calling and running the computer program from the memory, so that a device on which the chip is mounted performs the method in the above possible embodiments.

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

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

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

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

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

In this application, the descriptions of the embodiments are focused on, and the details or descriptions of one embodiment may be found in the related descriptions of other embodiments.

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

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

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

The foregoing description is only of the preferred embodiments of the present application, and is not intended to limit the scope of the claims, and all equivalent structures or equivalent processes using the descriptions and drawings of the present application, or direct or indirect application in other related technical fields are included in the scope of the claims of the present application.

Claims

1. A method of processing, comprising the steps of:

s2, determining the frequency domain resources occupied by the Msg3 PUSCH based on the channel state information request field in the random access response uplink grant and the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant, wherein when determining the frequency domain resources occupied by the Msg3 PUSCH, determining the allocation mode of the Msg3 PUSCH frequency hopping indication bit according to the channel state information request field and/or the physical uplink shared channel frequency domain resource allocation field.

2. The method of claim 1, wherein the step S2 comprises at least one of:

3. The method of claim 2, wherein the step S2 further comprises at least one of:

4. The method of claim 2, wherein the frequency hopping comprises inter-slot frequency hopping or intra-slot frequency hopping.

5. A method of processing, comprising the steps of:

s1, sending a random access response so that the terminal equipment determines the frequency domain resources occupied by the Msg3 PUSCH according to the channel state information request field in the random access response uplink grant and the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant, wherein when determining the frequency domain resources occupied by the Msg3 PUSCH, the terminal equipment determines the allocation mode of the Msg3 PUSCH frequency hopping indication bits according to the channel state information request field and/or the physical uplink shared channel frequency domain resource allocation field.

6. The method of claim 5, wherein the determining, by the terminal device, the frequency domain resource occupied by the Msg3 PUSCH according to the channel state information request field in the random access response uplink grant in the random access response and the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant, comprises at least one of:

7. The method of claim 6, wherein the terminal device determines the frequency domain resources occupied by the Msg3 PUSCH according to the channel state information request field in the random access response uplink grant in the random access response and the physical uplink shared channel frequency domain resource allocation field in the random access response uplink grant, further comprising at least one of:

8. The method of claim 6, wherein the frequency hopping comprises inter-slot frequency hopping or intra-slot frequency hopping.

9. A communication device, comprising: a memory, a processor, and a processing program stored in the memory, wherein the processing program realizes the processing method according to claim 1 or 5 when executed by the processor.

10. A storage medium having stored thereon a computer program which, when executed by a processor, implements the processing method of claim 1 or 5.