Processing method, communication device, and storage medium

Abstract

Disclosed in the present application are a processing method, a communication device, and a storage medium. The processing method comprises: a terminal device executing first processing on the basis of a first configuration. By means of the technical solution of the present application, a terminal device executes first processing on the basis of a first configuration, thereby clearly determining a contention-based MSG3 transmission process, and thus supporting an increase in the uplink capacity.

Description

Processing method, communication device and storage medium Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a processing method, communication equipment and storage medium. Background Art

[0002] To improve the uplink capacity of the R19 IoT-NTN (Internet of Things-Non-terrestrial network), one approach is to support contention-based MSG3 (Message 3) transmission without MSG1 / RAR (Message 1 / Random Access Response).

[0003] During the process of conceiving and implementing this application, the inventors discovered at least the following problems:

[0004] The existing protocol has not yet clarified the contention-based MSG3 transmission process. Therefore, it is necessary to clarify the contention-based MSG3 transmission process.

[0005] The preceding description is intended to provide general background information and does not necessarily constitute prior art. Technical Solutions

[0006] The main purpose of this application is to provide a processing method, a communication device and a storage medium, which aim to clarify the contention-based MSG3 transmission process, thereby supporting the improvement of uplink capacity.

[0007] This application provides a processing method that can be applied to a terminal device (such as a mobile phone), comprising the following steps:

[0008] S2: Execute a first process based on the first configuration.

[0009] Optionally, the first configuration includes at least one of the following:

[0010] Shared pre-configured uplink resource timing configuration;

[0011] Shared pre-configured uplink resource timing group configuration;

[0012] Shared pre-configured uplink resource time-frequency domain resource configuration;

[0013] Repeat the sending times N;

[0014] Shared pre-configured uplink resource response window timer or contention resolution timer;

[0015] Maximum transport block size.

[0016] Optionally, the method further comprises at least one of the following:

[0017] The first configuration is for first message transmission without using MSG1 / RAR;

[0018] The shared pre-configured uplink resource timing configuration indicates the time domain position and / or period of the shared uplink resource;

[0019] The shared pre-configured uplink resource opportunity grouping configuration indicates grouping the shared pre-configured uplink resource opportunities;

[0020] The shared pre-configured uplink resource opportunity group configuration includes a group start position and / or a group length;

[0021] The number of repetitions N represents the number of times the first message is repetitively sent on a shared pre-configured uplink resource opportunity or within a group;

[0022] The shared pre-configured uplink resource response window timer or the contention resolution timer represents the window in which the terminal device monitors the network response after sending the first message.

[0023] Optionally, step S2 includes:

[0024] In response to a first condition being met, a first message is sent based on a first configuration.

[0025] Optionally, the first condition is satisfied, including at least one of the following:

[0026] The upper layer requests to establish or restore a radio resource control connection;

[0027] The terminal device is configured to use shared pre-configured uplink resources;

[0028] The terminal device has valid shared pre-configured uplink resources;

[0029] The terminal equipment has a valid timing advance;

[0030] The terminal device stores a next-hop link counter;

[0031] The uplink data does not exceed the transport block size.

[0032] Optionally, sending the first message based on the first configuration includes at least one of the following:

[0033] Selecting a timing to share pre-configured uplink resources or sending the first message in groups;

[0034] Selecting to send the first message at the next nearest shared pre-configured uplink resource opportunity or group;

[0035] Repeating N times the first message within a shared pre-configured uplink resource opportunity or group;

[0036] Selecting N shared pre-configured uplink resource opportunities within the shared pre-configured uplink resource opportunity or group based on a first rule to send a first message;

[0037] The first message carries the shared pre-configured uplink resource opportunity or the location information of the shared pre-configured uplink resource opportunity selected in the group.

[0038] Optionally, the method further comprises at least one of the following:

[0039] Start the shared pre-configured uplink resource response window timer or contention resolution timer;

[0040] After the shared pre-configured uplink resource opportunity grouping ends, starting the shared pre-configured uplink resource response window timer or the contention resolution timer;

[0041] If a response matching that of the terminal device is received before the shared pre-configured uplink resource response window timer or the contention resolution timer times out, the shared pre-configured uplink resource transmission is successful or the contention resolution is successful.

[0042] Optionally, the received response that matches the terminal device includes at least one of the following:

[0043] Successfully detecting a physical downlink control channel identified, scrambled, or addressed using the first RNTI;

[0044] The received downlink control information or media access control protocol data unit or second message includes identification information of the terminal device;

[0045] The received MAC protocol data unit or second message matches the first message;

[0046] detecting a physical downlink control channel identified, scrambled, or addressed using a second RNTI;

[0047] A layer 1 confirmation message is received.

[0048] Optionally, the method further comprises at least one of the following:

[0049] The first RNTI is predefined by the system;

[0050] The first RNTI is calculated by the terminal device according to the selected shared pre-configured uplink resource opportunity or the shared pre-configured uplink resource opportunity group;

[0051] The identification information is a second RNTI or a temporary mobile user identity code;

[0052] The identification information is sent to the terminal device via a radio resource control message;

[0053] The second RNTI is the C-RNTI.

[0054] The present application also provides a processing method, which can be applied to a network device (such as a base station), comprising the steps of:

[0055] S1: Send a first configuration to enable the terminal device to perform a first process based on the first configuration.

[0056] Optionally, the first configuration includes at least one of the following:

[0057] Shared pre-configured uplink resource timing configuration;

[0058] Shared pre-configured uplink resource timing group configuration;

[0059] Shared pre-configured uplink resource time-frequency domain resource configuration;

[0060] Repeat the sending times N;

[0061] Shared pre-configured uplink resource response window timer or contention resolution timer;

[0062] Maximum transport block size.

[0063] Optionally, the method further comprises at least one of the following:

[0064] The first configuration is for first message transmission without using MSG1 / RAR;

[0065] The shared pre-configured uplink resource timing configuration indicates the time domain position and / or period of the shared uplink resource;

[0066] The shared pre-configured uplink resource opportunity grouping configuration indicates grouping the shared pre-configured uplink resource opportunities;

[0067] The shared pre-configured uplink resource opportunity group configuration includes a group start position and / or a group length;

[0068] The number of repetitions N represents the number of times the first message is repetitively sent on a shared pre-configured uplink resource opportunity or within a group;

[0069] The shared pre-configured uplink resource response window timer or the contention resolution timer represents the window in which the terminal device monitors the network response after sending the first message.

[0070] Optionally, the terminal device performs a first process based on the first configuration, including:

[0071] In response to the first condition being met, the terminal device sends a first message based on the first configuration.

[0072] Optionally, the first condition is satisfied, including at least one of the following:

[0073] The upper layer requests to establish or restore a radio resource control connection;

[0074] The terminal device is configured to use shared pre-configured uplink resources;

[0075] The terminal device has valid shared pre-configured uplink resources;

[0076] The terminal equipment has a valid timing advance;

[0077] The terminal device stores a next-hop link counter;

[0078] The uplink data does not exceed the transport block size.

[0079] Optionally, the terminal device sends a first message based on the first configuration, including at least one of the following:

[0080] The terminal device selects a timing to share pre-configured uplink resources or sends the first message in groups;

[0081] The terminal device selects to send the first message at the next nearest shared pre-configured uplink resource opportunity or group;

[0082] The terminal device repeatedly sends the first message N times in a shared pre-configured uplink resource opportunity or group;

[0083] The terminal device selects N shared pre-configured uplink resource opportunities based on the first rule within the shared pre-configured uplink resource opportunity or group to send the first message;

[0084] The first message carries the shared pre-configured uplink resource opportunity or the location information of the shared pre-configured uplink resource opportunity selected in the group.

[0085] Optionally, the method further comprises at least one of the following:

[0086] Detecting the physical uplink shared channel at the corresponding shared pre-configured uplink resource opportunity, and sending a response message if uplink information of the terminal device is successfully detected;

[0087] The terminal device starts a shared pre-configured uplink resource response window timer or a contention resolution timer;

[0088] After the shared pre-configured uplink resource opportunity grouping ends, the terminal device starts the shared pre-configured uplink resource response window timer or the contention resolution timer;

[0089] If the terminal device receives a response that matches the terminal device before the shared pre-configured uplink resource response window timer or the contention resolution timer times out, the shared pre-configured uplink resource transmission is successful or the contention resolution is successful.

[0090] Optionally, the terminal device receives a response that matches the terminal device, including at least one of the following:

[0091] The terminal device successfully detects a physical downlink control channel identified, scrambled, or addressed using the first RNTI;

[0092] The downlink control information or media access control protocol data unit or second message received by the terminal device includes identification information of the terminal device;

[0093] The media access control protocol data unit or the second message received by the terminal device matches the first message;

[0094] The terminal device successfully detects a physical downlink control channel identified, scrambled, or addressed using the second RNTI;

[0095] The terminal device receives the layer 1 confirmation message.

[0096] Optionally, the method further comprises at least one of the following:

[0097] The response information includes identification information of at least one terminal device;

[0098] The response message includes scheduling information of the physical downlink shared channel;

[0099] The first RNTI is predefined by the system;

[0100] The first RNTI is calculated by the terminal device according to the selected shared pre-configured uplink resource opportunity or the shared pre-configured uplink resource opportunity group;

[0101] The identification information is a second RNTI or a temporary mobile user identity code;

[0102] The identification information is sent to the terminal device via a radio resource control message;

[0103] The second RNTI is the C-RNTI.

[0104] The present application also provides a processing device, comprising:

[0105] The processing module is configured to perform a first process based on the first configuration.

[0106] The present application also provides a processing device, comprising:

[0107] The sending module is used to send a first configuration so that the terminal device performs a first process based on the first configuration.

[0108] The present application also provides a communication device, comprising: a memory and a processor, wherein a processing program is stored in the memory, and the processing program is executed by the processor to implement the steps of any of the processing methods described above.

[0109] The communication device in this application can be a terminal device (such as a mobile phone) or a network device (such as a base station). The specific reference needs to be clarified in the context.

[0110] The present application also provides a computer-readable storage medium, on which a computer program is stored. The computer program is executed by a processor to implement the steps of any of the processing methods described above.

[0111] In the technical solution of the present application, the terminal device performs the first processing based on the first configuration, clarifies the contention-based MSG3 transmission process, and thus can support the improvement of uplink capacity. BRIEF DESCRIPTION OF THE DRAWINGS

[0112] The accompanying drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present application, and together with the specification, are used to explain the principles of the present application. In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for describing the embodiments. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without inventive work.

[0113] FIG1 is a schematic diagram of the hardware structure of a mobile terminal for implementing various embodiments of the present application;

[0114] FIG2 is a diagram of a communication network system architecture provided by an embodiment of the present application;

[0115] FIG3 is a schematic diagram of the hardware structure of a controller 140 provided in this application;

[0116] FIG4 is a schematic diagram of the hardware structure of a network node 150 provided in this application;

[0117] FIG5 is a schematic flow chart of a processing method according to the first embodiment of the present application;

[0118] FIG6 is a schematic diagram of a scenario of a processing method shown in the third embodiment of the present application;

[0119] FIG7 is a schematic diagram of a scenario of a processing method shown in the third embodiment of the present application;

[0120] FIG8 is a schematic diagram of a scenario of a processing method according to a fourth embodiment of the present application;

[0121] FIG9 is a schematic flow chart of a processing method according to a fifth embodiment of the present application;

[0122] FIG10 is a schematic diagram of the interaction flow between a network device and a terminal device according to a processing method according to a sixth embodiment of the present application;

[0123] FIG11 is a first structural diagram of a processing device provided in an embodiment of the present application;

[0124] FIG12 is a second structural diagram of a processing device provided in an embodiment of the present application;

[0125] FIG13 is a schematic diagram of the structure of the communication device provided in an embodiment of the present application.

[0126] The purpose of this application, its features, and advantages will be further described in conjunction with the embodiments and with reference to the accompanying drawings. The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and the accompanying text are not intended to limit the scope of the present application in any way, but rather to illustrate the concepts of this application to those skilled in the art by reference to specific embodiments.

[0127] Implementation Methods of the Application

[0128] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0129] It should be noted that, in this document, the terms "comprises", "includes" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element, and / or, components, features, and elements with the same name in different embodiments of the present application may have the same meaning or different meanings, and their specific meanings need to be determined by their explanation in the specific embodiment or further combined with the context of the specific embodiment.

[0130] It should be understood that although the terms "first," "second," "third," etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are used solely to distinguish information of the same type from one another. For example, without departing from the scope of this disclosure, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the term "if," as used herein, may be interpreted as "upon," "when," or "in response to a determination." 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 should be further understood that the terms "comprising" and "including" indicate the presence of the recited features, steps, operations, elements, components, items, types, and / or groups, but do not preclude the presence, occurrence, or addition of one or more other features, steps, operations, elements, components, items, types, and / or groups. The terms "or," "and / or," "including at least one of the following," etc., as used herein, may be interpreted as inclusive, meaning any one or any combination. For example, “comprising at least one of the following: A, B, C” means “any of the following: A; B; C; A and B; A and C; B and C; A and B and C”; and for another example, “A, B or C” or “A, B and / or C” means “any of the following: A; B; C; A and B; A and C; B and C; A and B and C”. An exception to this definition will occur only when a combination of elements, functions, steps or operations are inherently mutually exclusive in some manner.

[0131] It should be understood that, although the various steps in the flowchart in the embodiment of the present application are shown in sequence according to the indication of the arrows, these steps are not necessarily performed in sequence in the order indicated by the arrows. Unless clearly stated herein, the execution of these steps is not strictly limited in order, and they can be performed in other orders. Moreover, at least a portion of the steps in the figure may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily performed at the same time, but can be performed at different times, and their execution order is not necessarily performed in sequence, but can be performed in turn or alternately with at least a portion of other steps or sub-steps or stages of other steps.

[0132] As used herein, the words "if" and "if" may be interpreted as "at the time of" or "when" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined" or "if (stated condition or event) is detected" may be interpreted as "when it is determined" or "in response to the determination" or "when detecting (stated condition or event)" or "in response to detecting (stated condition or event)," depending on the context.

[0133] It should be noted that in this article, step codes such as S1 and S2 are used for the purpose of expressing the corresponding content more clearly and concisely, and do not constitute a substantial restriction on the order. When implementing the step, those skilled in the art may execute S2 first and then S1, etc., but these should all be within the scope of protection of this application.

[0134] It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application.

[0135] In the subsequent description, the use of suffixes such as "module", "component" or "unit" to represent elements is only for the purpose of facilitating the description of the present application and has no specific meaning. Therefore, "module", "component" or "unit" can be used interchangeably.

[0136] The communication device in this application can be a terminal device (such as a mobile phone) or a network device (such as a base station). The specific reference needs to be clarified based on the context.

[0137] The terminal device may be implemented in various forms. For example, the terminal device described in this application may include intelligent terminal devices such as mobile phones, tablet computers, laptop computers, PDAs, portable media players (PMPs), navigation devices, wearable devices, smart bracelets, pedometers, and other fixed terminal devices such as digital TVs and desktop computers.

[0138] The subsequent description will be made using a mobile terminal as an example. Those skilled in the art will understand that, in addition to components specifically used for mobile purposes, the configuration according to the embodiments of the present application can also be applied to fixed-type terminal devices.

[0139] Please refer to Figure 1, which is a schematic diagram of the hardware structure of a mobile terminal for implementing various embodiments of the present application. The mobile terminal 100 may include components such as 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 understand that the mobile terminal structure shown in Figure 1 does not limit the mobile terminal. The mobile terminal may include more or fewer components than shown, or may combine certain components, or arrange the components differently.

[0140] The following is a detailed introduction to the various components of the mobile terminal in conjunction with Figure 1:

[0141] The RF unit 101 can be used to send and receive information or receive signals during calls. Specifically, it receives downlink information from the base station and transmits it to the processor 110 for processing. It also transmits uplink data to the base station. Typically, the RF 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 / or other components. Furthermore, the RF unit 101 can communicate with the network and other devices via wireless communication. The above-mentioned wireless communications can use any communication standard or protocol, including but not limited to GSM (Global System of Mobile communication), GPRS (General Packet Radio Service), CDMA2000 (Code Division Multiple Access 2000), WCDMA (Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division Duplexing-Long Term Evolution), TDD-LTE (Time Division Duplexing-Long Term Evolution), 5G and 6G, etc.

[0142] WiFi is a short-range wireless transmission technology. A mobile terminal, through WiFi module 102, enables users to send and receive emails, browse web pages, and access streaming media, providing wireless broadband Internet access. Although FIG1 illustrates WiFi module 102, it is understood that it is not a required component of the mobile terminal and can be omitted as needed without altering the essence of the invention.

[0143] The audio output unit 103 can convert audio data received by the RF unit 101 or the WiFi module 102 or stored in the memory 109 into an audio signal and output it 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. Furthermore, the audio output unit 103 can also provide audio output related to a specific function performed by the mobile terminal 100 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 103 may include a speaker, a buzzer, or the like.

[0144] The A / V input unit 104 is used to receive audio or video signals. The A / V input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042. The GPU 1041 processes image data of still images or videos captured by an image capture device (e.g., a camera) in video capture mode or image capture mode. The processed image frames may be displayed on the display unit 106. The image frames processed by the GPU 1041 may be stored in the memory 109 (or other storage medium) or transmitted via the RF unit 101 or the WiFi module 102. The microphone 1042 may receive sound (audio data) in operating modes such as a phone call mode, a recording mode, and a voice recognition mode, and may process such sound into audio data. In the phone call mode, the processed audio (voice) data may be converted into a format that can be transmitted to a mobile communication base station via the RF unit 101. The microphone 1042 may implement various types of noise cancellation (or suppression) algorithms to eliminate (or suppress) noise or interference generated during the reception and transmission of audio signals.

[0145] 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 can adjust the brightness of the display panel 1061 according to the brightness of the ambient light, and the proximity sensor can turn off the display panel 1061 and / or the backlight when the mobile terminal 100 is moved to the ear. As a type of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in all directions (generally three axes), and can detect the magnitude and direction of gravity when stationary. It can be used for applications that recognize the posture of the mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc.; as for other sensors that can be configured in the mobile phone, such as fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., they will not be described here.

[0146] The display unit 106 is used to display information input by the user or information provided to the user. The display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

[0147] The user input unit 107 can be used to receive input digital or character information and generate key signal input related to user settings and function control of the mobile terminal. Optionally, the user input unit 107 may include a touch panel 1071 and other input devices 1072. The touch panel 1071, also known as a touch screen, can collect user touch operations on or near it (such as operations performed by the user using a finger, stylus, or any other suitable object or accessory on or near the touch panel 1071) and drive corresponding connected devices according to a pre-set program. The touch panel 1071 may include two parts: a touch detection device and a touch controller. Optionally, the touch detection device detects the user's touch direction and detects the signal generated by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device and converts it into touch point coordinates, which are then sent to the processor 110. It can also receive and execute commands sent by the processor 110. And / or, the touch panel 1071 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may further include other input devices 1072. Optionally, the other input devices 1072 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, power keys, etc.), a trackball, a mouse, a joystick, etc., and the specifics are not limited here.

[0148] Optionally, the touch panel 1071 may overlay the display panel 1061. When the touch panel 1071 detects a touch operation on or near it, it transmits the information to the processor 110 to determine the type of touch event. The processor 110 then provides a corresponding visual output on the display panel 1061 based on the type of touch event. Although in FIG1 , the touch panel 1071 and the display panel 1061 are shown as two separate components to implement the input and output functions of the mobile terminal, in some embodiments, the touch panel 1071 and the display panel 1061 may be integrated to implement the input and output functions of the mobile terminal, which is not limited to this specific embodiment.

[0149] The interface unit 108 serves as an interface through which at least one external device can be connected to the mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, an audio input / output (I / O) port, a video I / O port, a headphone port, etc. 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.

[0150] Memory 109 can be used to store software programs and various data. Memory 109 may primarily include a program storage area and a data storage area. Optionally, the program storage area may store an operating system and at least one application required for a function (such as a sound playback function or an image playback function); the data storage area may store data generated based on the use of the mobile phone (such as audio data, a phone book, etc.). Furthermore, / or, memory 109 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0151] Processor 110 is the control center of the mobile terminal, connecting all components of the mobile terminal using various interfaces and circuits. By running or executing software programs and / or modules stored in memory 109 and accessing data stored in memory 109, it executes various functions of the mobile terminal and processes data, thereby providing overall monitoring of the mobile terminal. Processor 110 may include one or more processing units; preferably, processor 110 may integrate an application processor and a modem processor. Optionally, the application processor primarily handles the operating system, user interface, and application programs, while the modem processor primarily handles wireless communications. It is understood that the modem processor may not be integrated into processor 110.

[0152] The mobile terminal 100 may also include a power supply 111 (such as a battery) for supplying power to various components. Preferably, the power supply 111 may be logically connected to the processor 110 through a power management system, thereby managing functions such as charging, discharging, and power consumption through the power management system.

[0153] Although not shown in FIG. 1 , the mobile terminal 100 may further include a Bluetooth module, etc., which will not be described in detail here.

[0154] To facilitate understanding of the embodiments of the present application, the communication network system on which the mobile terminal of the present application is based is described below.

[0155] Please refer to Figure 2, which is a communication network system architecture diagram provided in an embodiment of the present application. The communication network system is an NR (New Radio) system of universal mobile communication technology. The NR system includes UE (User Equipment) 201, E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) 202, EPC (Evolved Packet Core) 203 and the operator's IP service 204, which are connected in sequence.

[0156] Optionally, UE201 may be the above-mentioned terminal device 100, which will not be described in detail here.

[0157] E-UTRAN 202 includes eNodeB 2021 and other eNodeBs 2022 . Optionally, eNodeB 2021 may be connected to other eNodeBs 2022 via a backhaul (eg, an X2 interface). eNodeB 2021 is connected to EPC 203 , and eNodeB 2021 may provide access from UE 201 to EPC 203 .

[0158] EPC 203 may include an MME (Mobility Management Entity) 2031, an HSS (Home Subscriber Server) 2032, other MMEs 2033, an SGW (Serving Gate Way) 2034, a PGW (PDN Gate Way) 2035, and a PCRF (Policy and Charging Rules Function) 2036. MME 2031 is optionally a control node that processes signaling between UE 201 and EPC 203, providing bearer and connection management. HSS 2032 provides registers for managing functions such as the Home Location Register (not shown) and stores user-specific information such as service features and data rates. All user data can be sent through SGW2034, PGW2035 can provide IP address allocation and other functions for UE 201, PCRF2036 is the policy and charging control policy decision point for service data flow and IP bearer resources, and it selects and provides available policy and charging control decisions for the policy and charging execution function unit (not shown in the figure).

[0159] The IP service 204 may include the Internet, an intranet, an IMS (IP Multimedia Subsystem), or other IP services.

[0160] Although the above introduction takes the LTE system as an example, those skilled in the art should know that this application is not only applicable to the LTE system, but can also be applied to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, 5G and future new network systems (such as 6G), etc., which are not limited here.

[0161] FIG3 is a schematic diagram of the hardware structure of a controller 140 provided in this application. The controller 140 includes a memory 1401 and a processor 1402. The memory 1401 is used to store program instructions, and the processor 1402 is used to call the program instructions in the memory 1401 to execute the steps performed by the controller in the first embodiment of the above method. The implementation principles and beneficial effects are similar and will not be repeated here.

[0162] Optionally, the controller further includes a communication interface 1403, which can be connected to the processor 1402 via a bus 1404. The processor 1402 can control the communication interface 1403 to implement the receiving and sending functions of the controller 140.

[0163] Figure 4 is a schematic diagram of the hardware structure of a network node 150 provided in this application. Network node 150 includes: a memory 1501 and a processor 1502. Memory 1501 is used to store program instructions, and processor 1502 is used to call the program instructions in memory 1501 to execute the steps performed by the first node in the first embodiment of the above method. The implementation principles and beneficial effects are similar and will not be repeated here.

[0164] Optionally, the controller further includes a communication interface 1503, which can be connected to the processor 1502 via a bus 1504. The processor 1502 can control the communication interface 1503 to implement the receiving and sending functions of the network node 150.

[0165] The integrated modules implemented in the form of software function modules can be stored in a computer-readable storage medium. The software function modules stored in a storage medium include a number of instructions for causing a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute some of the steps of the methods of various embodiments of the present application.

[0166] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can 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 process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a storage medium or transmitted from one storage medium to another storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state drive solid state disk, SSD), etc.

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

[0168] Technical terms involved in this embodiment:

[0169] PDSCH: Physical Downlink Shared Channel, physical downlink shared channel;

[0170] PUSCH: Physical Uplink Shared Channel, physical uplink shared channel;

[0171] PDCCH: Physical Downlink Control Channel, physical downlink control channel;

[0172] IoT-NTN: Internet of Things-Non-Terrestrial Network;

[0173] RRC: Radio Resource Control;

[0174] TA: Timing Advance, timing advance;

[0175] DCI: Downlink Control Information, downlink control information;

[0176] SPUR: Shared Pre-configured Uplink Resource, shared pre-configured uplink resources;

[0177] SPUR occasion: Shared Preconfigured Uplink Resource occasion, shared preconfigured uplink resource occasion;

[0178] TBS: Transport Block Size, transport block size;

[0179] nextHopChainingCount: next Hop Chaining Counter, next hop link counter;

[0180] L1 ACK: Layer 1 Acknowledgement;

[0181] RNTI: Radio-Network Temporary Identifier, wireless network temporary identifier;

[0182] MAC PDU: Medium Access Control Protocol Data Unit, media access control protocol data unit;

[0183] TMSI: Temporary Mobile Subscriber Identity, temporary mobile user identification code;

[0184] MSG1 / RAR: Message 1 / Random Access Response;

[0185] MSG3: message 3;

[0186] MSG4: message 4;

[0187] RTT: Round-Trip Time, round-trip delay.

[0188] First embodiment

[0189] 5 , which is a flow chart of a processing method according to a first embodiment of the present application, the processing method according to the embodiment of the present application can be applied to a terminal device (such as a mobile phone), and includes the following steps:

[0190] S2: The terminal device performs a first process based on the first configuration.

[0191] The embodiment of the present application is mainly applied to the R19 IoT-NTN (Internet of Things - Non-Terrestrial Network) scenario, and aims to clarify the contention-based MSG3 transmission process, thereby supporting contention-based MSG3 (Message 3) transmission without MSG1 / RAR (Message 1 / Random Access Response), thereby improving uplink capacity, and / or supporting repeated transmission and contention resolution to improve contention-based MSG3 transmission performance.

[0192] Optionally, in order to clarify the contention-based MSG3 transmission process, in this embodiment, the terminal device performs the first processing based on the first configuration.

[0193] Optionally, the first configuration is provided by a network device.

[0194] Optionally, the first configuration is a shared pre-configured uplink resource (SPUR) configuration.

[0195] Optionally, the network device sends a first configuration, the terminal device receives the first configuration, and performs a first process based on the first configuration.

[0196] Optionally, the terminal device performs a first process, including: the terminal device sends a first message.

[0197] Optionally, the first configuration is used for first message transmission without using MSG1 / RAR.

[0198] Optionally, the first message is MSG3.

[0199] Optionally, the first message may specifically be an RRC EarlyData Request or an RRC Connection Resume Request message.

[0200] Optionally, the first configuration includes: shared pre-configured uplink resource timing configuration, shared pre-configured uplink resource timing grouping configuration, shared pre-configured uplink resource time-frequency domain resource configuration, number of repeated transmissions N, shared pre-configured uplink resource response window timer or contention resolution timer, and at least one of the maximum transmission block size.

[0201] Optionally, the first configuration also includes time information when the terminal device can use the shared pre-configured uplink resources.

[0202] Optionally, the first configuration also includes parameter information required for the terminal device to select a first rule for sharing a pre-configured uplink resource timing or grouping.

[0203] Optionally, the parameter information required by the first rule may be, for example, parameter information for specifying the terminal device to select a specific SPUR or group.

[0204] Optionally, the shared pre-configured uplink resource opportunity configuration represents a time domain position and / or period of the shared uplink resource.

[0205] Optionally, the grouping configuration of the shared pre-configured uplink resource opportunities indicates grouping the shared pre-configured uplink resource opportunities.

[0206] Optionally, the shared pre-configured uplink resource opportunity group configuration includes a group start position and / or a group length.

[0207] Optionally, the time-frequency domain resource configuration of the shared pre-configured uplink resource includes PUSCH configuration, such as uplink grant information.

[0208] Optionally, the time-frequency domain resource configuration of the shared pre-configured uplink resource further includes at least one of PDCCH, PDSCH, and PUCCH configuration.

[0209] Optionally, the number of repeated transmissions N represents the number of times the first message is repeatedly transmitted at a shared pre-configured uplink resource opportunity or within a group.

[0210] Optionally, the shared pre-configured uplink resource response window timer or the contention resolution timer represents a window in which the terminal device monitors the network response after sending the first message.

[0211] Optionally, the terminal device performs a first process based on the first configuration, including:

[0212] In response to a first condition being met, a first message is sent based on a first configuration.

[0213] Optionally, the first condition is satisfied, including at least one of the following:

[0214] The upper layer requests to establish or restore a radio resource control connection;

[0215] The terminal device is configured to use shared pre-configured uplink resources;

[0216] The terminal device has valid shared pre-configured uplink resources;

[0217] The terminal equipment has a valid timing advance;

[0218] The terminal device stores a next-hop link counter;

[0219] The uplink data does not exceed the transport block size.

[0220] Optionally, multiple terminal devices share pre-configured uplink resources.

[0221] Optionally, the shared pre-configured uplink resources are sent via a system message.

[0222] Optionally, the shared pre-configured uplink resources are sent via radio resource control signaling.

[0223] Optionally, sending the first message based on the first configuration includes at least one of the following:

[0224] Selecting a timing to share pre-configured uplink resources or sending the first message in groups;

[0225] Selecting to send the first message at the next nearest shared pre-configured uplink resource opportunity or group;

[0226] Repeating N times the first message within a shared pre-configured uplink resource opportunity or group;

[0227] Selecting N shared pre-configured uplink resource opportunities within the shared pre-configured uplink resource opportunity or group based on a first rule to send a first message;

[0228] The first message carries the shared pre-configured uplink resource opportunity or the location information of the shared pre-configured uplink resource opportunity selected in the group.

[0229] Optionally, the first rule may be, for example, random selection or selection based on terminal device identification and / or shared preconfigured uplink resources (SPUR) packet length, and / or selection of the shared preconfigured uplink resource timing based on auxiliary parameters provided by the network device.

[0230] Through the technical solution of this embodiment, the terminal device performs the first processing based on the first configuration, clarifies the contention-based MSG3 transmission process, and can support the improvement of uplink capacity.

[0231] Second embodiment

[0232] Based on the first embodiment of the present application, a second embodiment of the present application is proposed. This embodiment mainly explains the processing method after the terminal device sends the first message.

[0233] In this embodiment, the terminal device performs the first process based on the first configuration.

[0234] Optionally, the first configuration is provided by a network device.

[0235] Optionally, the first configuration is a shared pre-configured uplink resource (SPUR) configuration.

[0236] Optionally, the network device sends a first configuration, the terminal device receives the first configuration, and performs a first process based on the first configuration.

[0237] Optionally, the terminal device performs a first process, including: the terminal device sends a first message.

[0238] Optionally, the first configuration is used for first message transmission without using MSG1 / RAR.

[0239] Optionally, the first message is MSG3.

[0240] Optionally, the first message may specifically be an RRC EarlyData Request or an RRC Connection Resume Request message.

[0241] Optionally, the first configuration includes: shared pre-configured uplink resource timing configuration, shared pre-configured uplink resource timing grouping configuration, shared pre-configured uplink resource time-frequency domain resource configuration, number of repeated transmissions N, shared pre-configured uplink resource response window timer or contention resolution timer, and at least one of the maximum transmission block size.

[0242] Optionally, the first configuration carries time information when the terminal device can use the shared pre-configured uplink resources.

[0243] Optionally, the first configuration carries parameter information required for the terminal device to select a first rule for sharing a pre-configured uplink resource timing or grouping.

[0244] Optionally, the parameter information required by the first rule may be, for example, parameter information for specifying the terminal device to select a specific SPUR or group.

[0245] Optionally, the shared pre-configured uplink resource opportunity configuration represents a time domain position and / or period of the shared uplink resource.

[0246] Optionally, the grouping configuration of the shared pre-configured uplink resource opportunities indicates grouping the shared pre-configured uplink resource opportunities.

[0247] Optionally, the shared pre-configured uplink resource opportunity group configuration includes a group start position and / or a group length.

[0248] Optionally, the time-frequency domain resource configuration of the shared pre-configured uplink resource includes PUSCH configuration, such as uplink grant information.

[0249] Optionally, the time-frequency domain resource configuration of the shared pre-configured uplink resource further includes at least one of PDCCH, PDSCH, and PUCCH configuration.

[0250] Optionally, the number of repeated transmissions N represents the number of times the first message is repeatedly transmitted at a shared pre-configured uplink resource opportunity or within a group.

[0251] Optionally, the shared pre-configured uplink resource response window timer or the contention resolution timer represents a window in which the terminal device monitors the network response after sending the first message.

[0252] Optionally, after sending the first message, the terminal device starts a shared pre-configured uplink resource response window timer or a contention resolution timer.

[0253] Optionally, the terminal device starts a shared pre-configured uplink resource response window timer or a contention resolution timer after repeatedly sending the first message for the last time.

[0254] Optionally, after the shared pre-configured uplink resource opportunity group ends, the terminal device starts the shared pre-configured uplink resource response window timer or the contention resolution timer. This is because, when a conflict occurs, the network device may rely on the demodulation result of the first message sent by other terminal devices in the group to demodulate the data of the current terminal device (interference cancellation), so it is necessary to delay the start of the timer.

[0255] Optionally, the terminal device also needs to delay a fixed time and / or the RTT (round trip time) between the terminal device and the network device when starting the shared pre-configured uplink resource response window timer or the contention resolution timer.

[0256] Optionally, if the terminal device receives a response that matches the terminal device before the shared pre-configured uplink resource response window timer or the contention resolution timer times out, it indicates that the shared pre-configured uplink resource transmission is successful or the contention resolution is successful.

[0257] Optionally, the terminal device receives a response that matches the terminal device, including at least one of the following:

[0258] The terminal device successfully detects a physical downlink control channel identified, scrambled, or addressed using the first RNTI;

[0259] The downlink control information (DCI) or media access control protocol data unit (MAC PDU) or second message received by the terminal device includes identification information of the terminal device;

[0260] The media access control protocol data unit or the second message received by the terminal device matches the first message;

[0261] The terminal device detects a physical downlink control channel identified or scrambled using the second RNTI;

[0262] The terminal device receives a layer 1 acknowledgement message (L1 ACK).

[0263] Optionally, the second message is MSG4.

[0264] Optionally, the second message may specifically be an RRC EarlyDataComplete or RRCConnectionRelease message.

[0265] Optionally, the first RNTI is predefined by the system, or the first RNTI is calculated by the terminal device according to a selected shared pre-configured uplink resource opportunity or a shared pre-configured uplink resource opportunity group.

[0266] Optionally, the identification information is a second RNTI or a temporary mobile user identity code.

[0267] Optionally, the identification information is sent to the terminal device via a radio resource control message.

[0268] Optionally, the second RNTI is a C-RNTI.

[0269] Through the technical solution of this embodiment, the terminal device executes the first processing based on the first configuration. The terminal device executes the first processing including sending the first message. After sending the first message, the shared pre-configured uplink resource response window timer or the contention resolution timer is started to monitor the PDCCH, which clarifies the contention-based MSG3 transmission process, thereby supporting the improvement of uplink capacity.

[0270] Third embodiment

[0271] Based on any of the above embodiments of the present application, a third embodiment of the present application is proposed. This embodiment mainly explains the processing method of the present application in combination with specific scenarios.

[0272] In this embodiment, the terminal device performs the first process based on the first configuration.

[0273] Optionally, the first configuration is provided by a network device.

[0274] Optionally, the first configuration is a SPUR (Shared Preconfigured Uplink Resources) configuration.

[0275] Optionally, the network device sends a SPUR configuration, where the SPUR configuration is used for the first message transmission without using MSG1 / RAR.

[0276] Optionally, the first message is MSG3.

[0277] Optionally, MSG3 may specifically be an RRC EarlyData Request or RRC Connection Resume Request message.

[0278] Optionally, the terminal device receives the SPUR configuration and performs the first processing based on the SPUR configuration.

[0279] Optionally, the terminal device performs a first process, including: the terminal device sends a first message.

[0280] Optionally, the SPUR configuration includes: SPUR occasion (shared pre-configured uplink resource occasion) configuration, SPUR occasion grouping configuration, SPUR time-frequency domain resource configuration, number of repeated transmissions N, SPUR response window timer or contention resolution timer, maximum TBS (maximum transport block size), and at least one of the first RNTI, as shown in Figure 6.

[0281] Optionally, the SPUR configuration further includes time information during which the terminal device can use the SPUR.

[0282] Optionally, the SPUR configuration carries parameter information required by the terminal device to select the first rule of the SPUR occasion or grouping.

[0283] Optionally, the parameter information required by the first rule may be, for example, parameter information for specifying the terminal device to select a specific SPUR or group.

[0284] Optionally, the SPUR occasion configuration represents a time domain position and / or period of the SPUR occasion.

[0285] Optionally, the SPUR occasion grouping configuration indicates grouping the SPUR occasions.

[0286] Optionally, the SPUR occasion packet configuration includes a packet start position and / or a packet length L.

[0287] Optionally, the packet start position may be a specific superframe and / or system frame number. Optionally, the packet length L is in units of SPUR occasion, indicating that L consecutive SPUR occasions constitute a group.

[0288] Optionally, the SPUR time-frequency domain resource configuration includes PUSCH configuration, such as uplink grant information (UL grant).

[0289] Optionally, the SPUR time-frequency domain resource configuration further includes at least one of PDCCH, PDSCH, and PUCCH configurations.

[0290] Optionally, the number of repetitions N represents the number of times MSG3 (in the SPUR or the SPUR packet) is repetitively transmitted.

[0291] Optionally, the SPUR response window timer or contention resolution timer indicates a window in which the terminal device listens for a network response after sending MSG3.

[0292] Optionally, the maximum TBS indicates the maximum TBS that can be sent through the SPUR.

[0293] Optionally, the first RNTI is used to scramble MSG3.

[0294] Optionally, the SPUR is sent via a system message.

[0295] Optionally, the SPUR is sent through RRC signaling (such as an RRC release message), that is, the SPUR resources are configured through RRC signaling.

[0296] Optionally, the terminal device requests the network device to configure that the terminal device can use the SPUR and / or sends time information when the SPUR can or needs to be used to the network device.

[0297] Optionally, the terminal device obtains time information that can or needs to use the SPUR through terminal device location information and / or terminal device service information and / or NTN (Non-Terrestrial Network) payload assistance message.

[0298] Optionally, the NTN payload assistance information includes at least one of satellite ephemeris information, a start time of an upcoming satellite providing service, and a time when a current satellite or cell stops providing service.

[0299] Optionally, the network device configures the terminal device through RRC signaling (such as RRCrelease message) to use SPUR resources and / or time information and / or a second RNTI of the SPUR resources.

[0300] Optionally, when the terminal device reselects a cell, the SPUR configuration becomes invalid.

[0301] Optionally, when the time during which the SPUR resources can be used is exceeded, the SPUR configuration becomes invalid.

[0302] Optionally, multiple terminal devices share SPUR resources.

[0303] Optionally, the terminal device performs a first process based on the first configuration, including:

[0304] In response to the first condition being met, the terminal device sends a first message based on the first configuration.

[0305] Optionally, the terminal device receives SPUR configuration and may use SPUR to send MSG3 when the first condition is met.

[0306] Optionally, MSG3 may specifically be an RRC EarlyData Request or RRC Connection Resume Request message.

[0307] Optionally, satisfying the first condition includes at least one of the following:

[0308] The upper layer requests to establish or restore an RRC connection;

[0309] The terminal device is configured to use the SPUR resource. Optionally, the network device is configured so that the terminal device can use the SPUR.

[0310] The terminal device has a valid SPUR;

[0311] The terminal device has a valid TA;

[0312] The terminal device stores nextHopChainingCount;

[0313] The uplink data does not exceed TBS, for example, the transmitted MAC PDU does not exceed TBS.

[0314] Optionally, as shown in FIG7 , the terminal device uses SPUR to send MSG3, and at least one of the following solutions may be adopted:

[0315] The terminal device sends MSG3 in the SPUR occasion;

[0316] The terminal device repeatedly sends MSG3 on N SPUR occasions;

[0317] The terminal device sends MSG3 in the SPUR occasion within the SPUR group;

[0318] The terminal device sends MSG3 in the next most recent SPUR packet;

[0319] The terminal device repeatedly sends MSG3 N times in the SPUR packet;

[0320] The terminal device randomly selects N SPUR occasions in the SPUR group and repeatedly sends MSG3;

[0321] The terminal device selects a SPUR group and / or SPUR occasion according to the first rule to send or repeatedly send MSG3;

[0322] The terminal device carries (eg, in a SPUR packet) the repeatedly transmitted SPUR occasion location information in MSG3 or the corresponding PUSCH uplink transmission or in a MAC PDU (eg, via a MAC CE).

[0323] For example, assuming that a SPUR group contains 6 SPUR occasions, and the terminal device sends MSG3 / EDT at the 0th and 3rd SPUR occasions in the group, the indicated SPUR occasion positions are 0 and 3 respectively.

[0324] Optionally, the location of repeated transmission is indicated for network interference cancellation.

[0325] Optionally, the terminal device may select different SPUR resources according to the first rule, and try to distribute the terminal device to different SPUR occasions or groups. For example, if RRC configures shared PUR resources, the terminal device may be distributed to each occasion or group.

[0326] Optionally, the first rule may be, for example, random selection or selection based on terminal device identification and / or shared preconfigured uplink resources (SPUR) packet length, and / or, selection of SPURoccasion or packet based on auxiliary parameters provided by the network device.

[0327] Through the technical solution of this embodiment, the terminal device performs the first processing based on the first configuration, clarifies the contention-based MSG3 transmission process, and can support the improvement of uplink capacity.

[0328] Fourth embodiment

[0329] Based on any of the above embodiments of the present application, a fourth embodiment of the present application is proposed. This embodiment mainly explains the processing method of the present application in combination with specific scenarios.

[0330] In this embodiment, the terminal device performs the first process based on the first configuration.

[0331] Optionally, the first configuration is provided by a network device.

[0332] Optionally, the first configuration is a SPUR (Shared Preconfigured Uplink Resources) configuration.

[0333] Optionally, the network device sends a SPUR configuration, where the SPUR configuration is used for the first message transmission without using MSG1 / RAR.

[0334] Optionally, the first message is MSG3.

[0335] Optionally, MSG3 may specifically be an RRC EarlyData Request or RRC Connection Resume Request message.

[0336] Optionally, the terminal device receives the SPUR configuration and performs the first processing based on the SPUR configuration.

[0337] Optionally, the terminal device performs a first process, including: the terminal device sends a first message.

[0338] Optionally, the SPUR configuration includes: SPUR occasion (shared pre-configured uplink resource occasion) configuration, SPUR occasion grouping configuration, SPUR time-frequency domain resource configuration, number of repeated transmissions N, SPUR response window timer or contention resolution timer, maximum TBS (maximum transport block size), and at least one of the first RNTI.

[0339] Optionally, the SPUR configuration further includes time information during which the terminal device can use the SPUR.

[0340] Optionally, the SPUR configuration carries parameter information required by the terminal device to select the first rule of the SPUR occasion or grouping.

[0341] Optionally, the parameter information required by the first rule may be, for example, parameter information for specifying the terminal device to select a specific SPUR or group.

[0342] Optionally, the SPUR occasion configuration represents a time domain position and / or period of the SPUR occasion.

[0343] Optionally, the SPUR occasion grouping configuration indicates grouping the SPUR occasions.

[0344] Optionally, the SPUR occasion packet configuration includes a packet start position and / or a packet length L.

[0345] Optionally, the packet start position may be a specific superframe and / or system frame number. Optionally, the packet length L is in units of SPUR occasion, indicating that L consecutive SPUR occasions constitute a group.

[0346] Optionally, the SPUR time-frequency domain resource configuration includes PUSCH configuration, such as uplink authorization information.

[0347] Optionally, the SPUR time-frequency domain resource configuration further includes at least one of PDCCH, PDSCH, and PUCCH configurations.

[0348] Optionally, the number of repetitions N represents the number of times MSG3 (in the SPUR or the SPUR packet) is repetitively transmitted.

[0349] Optionally, the SPUR response window timer or contention resolution timer indicates a window in which the terminal device listens for a network response after sending MSG3.

[0350] Optionally, the maximum TBS indicates the maximum TBS that can be sent through the SPUR.

[0351] Optionally, the first RNTI is used to scramble MSG3 / EDT.

[0352] Optionally, the SPUR is sent via a system message.

[0353] Optionally, the SPUR is sent through RRC signaling (such as an RRC release message), that is, the SPUR resources are configured through RRC signaling.

[0354] Optionally, the terminal device requests the network device to configure that the terminal device can use the SPUR and / or sends time information when the SPUR can or needs to be used to the network device.

[0355] Optionally, the terminal device obtains time information at which the SPUR can or needs to be used through the terminal device location information and / or the terminal device service information and / or the NTN payload auxiliary message.

[0356] Optionally, the NTN payload assistance information includes at least one of satellite ephemeris information, a start time of an upcoming satellite providing service, and a time when a current satellite or cell stops providing service.

[0357] Optionally, the network device configures the terminal device to use SPUR resources and / or time information and / or a second RNTI of the SPUR resources through RRC signaling (such as an RRC release message).

[0358] Optionally, when the terminal device reselects a cell, the SPUR configuration becomes invalid.

[0359] Optionally, when the time during which the SPUR resources can be used is exceeded, the SPUR configuration becomes invalid.

[0360] Optionally, multiple terminal devices share SPUR resources.

[0361] Optionally, the terminal device performs a first process based on the first configuration, including:

[0362] In response to the first condition being met, the terminal device sends a first message based on the first configuration.

[0363] Optionally, the terminal device receives SPUR configuration and may use SPUR to send MSG3 when the first condition is met.

[0364] Optionally, MSG3 may specifically be an RRC EarlyData Request or RRC Connection Resume Request message.

[0365] Optionally, after sending MSG3, the terminal device starts the SPUR response window timer or the contention resolution timer and monitors the PDCCH, as shown in FIG8 .

[0366] Optionally, the terminal device starts a SPUR response window timer or a contention resolution timer after repeatedly sending MSG3 for the last time.

[0367] Optionally, the terminal device starts the SPUR response window timer or contention resolution timer after the corresponding SPUR packet ends. This is because, in the case of repeated transmission, when a conflict occurs, the network device may rely on the demodulation results of other terminal devices in the packet to demodulate the data of the current terminal device (interference cancellation), so it is necessary to delay the start of the timer.

[0368] Optionally, the terminal device also needs to consider the RTT (round trip time) and / or fixed time between the terminal device and the network device (such as eNB) when starting the SPUR response window timer or the contention resolution timer.

[0369] Optionally, when the terminal device receives a response that matches the terminal device before the SPUR response window timer or the contention resolution timer times out, it is considered that the SPUR transmission is successful or the contention resolution is successful.

[0370] Optionally, when the SPUR response window timer or the contention resolution timer times out and the terminal device does not receive a response that matches the terminal device, it is considered that the SPUR transmission has failed or the contention resolution has failed.

[0371] Optionally, the matching response received by the terminal device includes at least one of the following:

[0372] The terminal device successfully detects a PDCCH identified, scrambled, or addressed using the first RNTI;

[0373] The downlink control information (DCI) or media access control protocol data unit (MAC PDU) or second message received by the terminal device includes identification information of the terminal device;

[0374] The media access control protocol data unit or the second message received by the terminal device matches the first message;

[0375] The terminal device detects a physical downlink control channel identified or scrambled using the second RNTI;

[0376] The terminal device receives a layer 1 acknowledgement message (L1 ACK).

[0377] Optionally, the second message is MSG4.

[0378] Optionally, MSG4 may specifically be an RRC EarlyDataComplete or RRCConnectionRelease message.

[0379] Optionally, the first RNTI is predefined by the system or delivered by a system message;

[0380] Optionally, the first RNTI is calculated by the terminal device according to a SPUR occasion or SPUR group selected by the terminal device;

[0381] Optionally, the identification information may be a second RNTI or a TMSI (Temporary Mobile Subscriber Identity) or other identification information.

[0382] Optionally, the second RNTI or other identification information is sent to the terminal device via an RRC message (such as RRC release).

[0383] Optionally, the second RNTI may be a C-RNTI.

[0384] Optionally, the network device detects the PUSCH in the corresponding SPUR occasion and sends a response message if uplink information of the terminal device is successfully detected.

[0385] Optionally, the response information may include identification information of at least one terminal device.

[0386] Optionally, the response information may include PDSCH scheduling information.

[0387] Optionally, the network device configures whether the terminal device can use SPUR through an RRC message (such as an RRC release message).

[0388] Optionally, the network device may control the number of terminal devices that can use SPUR, thereby reducing contention.

[0389] Through the technical solution of this embodiment, the terminal device performs the first processing based on the first configuration, clarifies the contention-based MSG3 transmission process, and can support the improvement of uplink capacity.

[0390] Fifth embodiment

[0391] 9 is a flowchart of a processing method according to a fifth embodiment of the present application. The processing method according to the embodiment of the present application can be applied to a network device (such as a base station), and includes the following steps:

[0392] S1: Send a first configuration to enable the terminal device to perform a first process based on the first configuration.

[0393] The embodiment of the present application is mainly applied to the R19 IoT-NTN (Internet of Things - Non-Terrestrial Network) scenario, and aims to clarify the contention-based MSG3 transmission process, thereby supporting contention-based MSG3 (Message 3) transmission without MSG1 / RAR (Message 1 / Random Access Response), thereby improving uplink capacity, and / or supporting repeated transmission and contention resolution to improve contention-based MSG3 transmission performance.

[0394] Optionally, in order to clarify the contention-based MSG3 transmission process, support contention-based MSG3 transmission without MSG1 / RAR, or support MSG3 transmission with repeated transmission and contention resolution, in this embodiment, the terminal device performs the first processing based on the first configuration.

[0395] Optionally, the first configuration is provided by a network device.

[0396] Optionally, the first configuration is a shared pre-configured uplink resource (SPUR) configuration.

[0397] Optionally, the network device sends a first configuration, the terminal device receives the first configuration, and performs a first process based on the first configuration.

[0398] Optionally, the network device receives a request from the terminal device to use or configure the SPUR and / or time information when the SPUR needs to be used.

[0399] Optionally, the time information using the SPUR is obtained by the terminal device through the terminal device location information and / or the terminal device service information and / or the NTN payload auxiliary message.

[0400] Optionally, the NTN payload assistance information includes at least one of satellite ephemeris information, a start time of an upcoming satellite providing service, and a time when a current satellite or cell stops providing service.

[0401] Optionally, the network device configures whether the terminal device can use the SPUR resources and / or the time information and / or the second RNTI of the SPUR resources through RRC signaling (such as an RRC release message).

[0402] Optionally, the terminal device performs a first process, including: the terminal device sends a first message.

[0403] Optionally, the first configuration is used for first message transmission without using MSG1 / RAR.

[0404] Optionally, the first message is MSG3.

[0405] Optionally, MSG3 may specifically be an RRC EarlyData Request or RRC Connection Resume Request message.

[0406] Optionally, the first configuration includes: shared pre-configured uplink resource timing configuration, shared pre-configured uplink resource timing grouping configuration, shared pre-configured uplink resource time-frequency domain resource configuration, number of repeated transmissions N, shared pre-configured uplink resource response window timer or contention resolution timer, and at least one of the maximum transmission block size.

[0407] Optionally, the first configuration also includes time information when the terminal device can use the shared pre-configured uplink resources.

[0408] Optionally, the first configuration also includes parameter information required for the terminal device to select a first rule for sharing a pre-configured uplink resource timing or grouping.

[0409] Optionally, the parameter information required by the first rule may be, for example, parameter information for specifying the terminal device to select a specific SPUR or group.

[0410] Optionally, the shared pre-configured uplink resource opportunity configuration represents a time domain position and / or period of the shared uplink resource.

[0411] Optionally, the grouping configuration of the shared pre-configured uplink resource opportunities indicates grouping the shared pre-configured uplink resource opportunities.

[0412] Optionally, the shared pre-configured uplink resource opportunity group configuration includes a group start position and / or a group length.

[0413] Optionally, the time-frequency domain resource configuration of the shared pre-configured uplink resource includes PUSCH configuration, such as uplink grant information.

[0414] Optionally, the time-frequency domain resource configuration of the shared pre-configured uplink resource further includes at least one of PDCCH, PDSCH, and PUCCH configuration.

[0415] Optionally, the number of repeated transmissions N represents the number of times the first message is repeatedly transmitted at a shared pre-configured uplink resource opportunity or within a group.

[0416] Optionally, the shared pre-configured uplink resource response window timer or the contention resolution timer represents a window in which the terminal device monitors the network response after sending the first message.

[0417] Optionally, the terminal device performs a first process based on the first configuration, including:

[0418] In response to a first condition being met, a first message is sent based on a first configuration.

[0419] Optionally, the first condition is satisfied, including at least one of the following:

[0420] The upper layer requests to establish or restore a radio resource control connection;

[0421] The terminal device is configured to use shared pre-configured uplink resources;

[0422] The terminal device has valid shared pre-configured uplink resources;

[0423] The terminal equipment has a valid timing advance;

[0424] The terminal device stores a next-hop link counter;

[0425] The uplink data does not exceed the transport block size.

[0426] Optionally, multiple terminal devices share pre-configured uplink resources.

[0427] Optionally, the shared pre-configured uplink resources are sent via a system message.

[0428] Optionally, the shared pre-configured uplink resources are sent via radio resource control signaling.

[0429] Optionally, sending the first message based on the first configuration includes at least one of the following:

[0430] Selecting a timing to share pre-configured uplink resources or sending the first message in groups;

[0431] Selecting to send the first message at the next nearest shared pre-configured uplink resource opportunity or group;

[0432] Repeating N times the first message within a shared pre-configured uplink resource opportunity or group;

[0433] Selecting N shared pre-configured uplink resource opportunities within the shared pre-configured uplink resource opportunity or group based on a first rule to send a first message;

[0434] The first message carries the shared pre-configured uplink resource opportunity or the location information of the shared pre-configured uplink resource opportunity selected in the group.

[0435] Optionally, the first rule may be, for example, random selection or selection based on terminal device identification and / or shared preconfigured uplink resources (SPUR) packet length, and / or selection of the shared preconfigured uplink resource timing based on auxiliary parameters provided by the network device.

[0436] Optionally, after sending the first message, the terminal device starts a shared pre-configured uplink resource response window timer or a contention resolution timer and monitors the physical uplink shared channel (PDCCH).

[0437] Optionally, the terminal device starts a shared pre-configured uplink resource response window timer or a contention resolution timer after repeatedly sending the first message for the last time.

[0438] Optionally, after the shared pre-configured uplink resource opportunity group ends, the terminal device starts the shared pre-configured uplink resource response window timer or the contention resolution timer. This is because, in the case of repeated transmission, when a conflict occurs, the network device may rely on the demodulation results of other terminal devices in the group to demodulate the current terminal device's data (interference cancellation), so it is necessary to delay the start of the timer.

[0439] Optionally, the terminal device may also need to delay a fixed time and / or the RTT between the terminal device and the network device when starting the shared pre-configured uplink resource response window timer or the contention resolution timer.

[0440] Optionally, the network device detects the physical uplink shared channel at the corresponding shared pre-configured uplink resource opportunity, and sends response information if the uplink information of the terminal device is successfully detected.

[0441] Optionally, before the shared pre-configured uplink resource response window timer or the contention resolution timer times out, if the terminal device receives a response that matches the terminal device, it indicates that the shared pre-configured uplink resource transmission is successful or the contention resolution is successful.

[0442] Optionally, the terminal device receives a response that matches the terminal device, including at least one of the following:

[0443] The terminal device successfully detects a physical downlink control channel identified, scrambled, or addressed using the first RNTI;

[0444] The downlink control information or media access control protocol data unit or second message received by the terminal device includes identification information of the terminal device;

[0445] The media access control protocol data unit or the second message received by the terminal device matches the first message;

[0446] The terminal device successfully detects a physical downlink control channel identified or scrambled using the second RNTI;

[0447] The terminal device receives the layer 1 confirmation message.

[0448] Optionally, the second message is MSG4.

[0449] Optionally, the second message may specifically be an RRC EarlyDataComplete or RRCConnectionRelease message.

[0450] Optionally, the first RNTI is predefined by the system, or the first RNTI is calculated by the terminal device according to a selected shared pre-configured uplink resource opportunity or a shared pre-configured uplink resource opportunity group.

[0451] Optionally, the identification information is a second RNTI or a temporary mobile user identity code.

[0452] Optionally, the identification information is sent to the terminal device via a radio resource control message.

[0453] Optionally, the second RNTI may be a C-RNTI.

[0454] Optionally, the response information may include identification information of at least one terminal device.

[0455] Optionally, the response information may include scheduling information of the physical downlink shared channel.

[0456] Optionally, the network device configures whether the terminal device can use SPUR through an RRC message (such as an RRC release message). Optionally, the network device can control the number of terminal devices that can use SPUR, thereby reducing contention.

[0457] Through the technical solution of this embodiment, the network device sends the first configuration so that the terminal device performs the first processing based on the first configuration, clarifies the contention-based MSG3 transmission process, and can support the improvement of uplink capacity.

[0458] Sixth embodiment

[0459] 10 , which is a schematic diagram of an interaction flow between a network device and a terminal device according to a processing method according to a sixth embodiment, the sixth embodiment of the present application proposes a processing method, comprising the steps of:

[0460] S1: The network device sends a first configuration, so that the terminal device performs a first process based on the first configuration;

[0461] S2: The terminal device performs a first process based on the first configuration.

[0462] The embodiment of the present application is mainly applied to the R19 IoT-NTN (Internet of Things - Non-Terrestrial Network) scenario, and aims to clarify the contention-based MSG3 transmission process, thereby supporting contention-based MSG3 (Message 3) transmission without MSG1 / RAR (Message 1 / Random Access Response), thereby improving uplink capacity, and / or supporting repeated transmission and contention resolution to improve contention-based MSG3 transmission performance.

[0463] Optionally, the first configuration is provided by a network device.

[0464] Optionally, the first configuration is a shared pre-configured uplink resource (SPUR) configuration.

[0465] Optionally, the network device sends a first configuration, the terminal device receives the first configuration, and performs a first process based on the first configuration.

[0466] Optionally, the terminal device requests the network device to configure that the terminal device can use the SPUR and / or sends time information when the SPUR can or needs to be used to the network device.

[0467] Optionally, the terminal device obtains time information at which the SPUR can or needs to be used through the terminal device location information and / or the terminal device service information and / or the NTN payload auxiliary message.

[0468] Optionally, the NTN payload assistance information includes at least one of satellite ephemeris information, a start time of an upcoming satellite providing service, and a time when a current satellite or cell stops providing service.

[0469] Optionally, the network device configures the terminal device to use SPUR resources and / or time information and / or a second RNTI of the SPUR resources through RRC signaling (such as an RRC release message).

[0470] Optionally, when the terminal device reselects a cell, the SPUR configuration becomes invalid.

[0471] Optionally, when the time during which the SPUR resources can be used is exceeded, the SPUR configuration becomes invalid.

[0472] Optionally, the terminal device performs a first process, including: the terminal device sends a first message.

[0473] Optionally, the first configuration is used for first message transmission without using MSG1 / RAR.

[0474] Optionally, the first message is MSG3.

[0475] Optionally, the first message may specifically be an RRC EarlyData Request or an RRC Connection Resume Request message.

[0476] Optionally, the first configuration includes: shared pre-configured uplink resource timing configuration, shared pre-configured uplink resource timing grouping configuration, shared pre-configured uplink resource time-frequency domain resource configuration, number of repeated transmissions N, shared pre-configured uplink resource response window timer or contention resolution timer, and at least one of the maximum transmission block size.

[0477] Optionally, the first configuration also includes time information when the terminal device can use the shared pre-configured uplink resources.

[0478] Optionally, the first configuration also includes parameter information required for the terminal device to select the first rule for sharing the pre-configured uplink resource timing or grouping.

[0479] Optionally, the parameter information required by the first rule may be, for example, parameter information for specifying the terminal device to select a specific SPUR or group.

[0480] Optionally, the shared pre-configured uplink resource opportunity configuration represents a time domain position and / or period of the shared uplink resource.

[0481] Optionally, the grouping configuration of the shared pre-configured uplink resource opportunities indicates grouping the shared pre-configured uplink resource opportunities.

[0482] Optionally, the shared pre-configured uplink resource opportunity group configuration includes a group start position and / or a group length.

[0483] Optionally, the time-frequency domain resource configuration of the shared pre-configured uplink resource includes PUSCH configuration, such as uplink grant information.

[0484] Optionally, the time-frequency domain resource configuration of the shared pre-configured uplink resource further includes at least one of PDCCH, PDSCH, and PUCCH configuration.

[0485] Optionally, the number of repeated transmissions N represents the number of times the first message is repeatedly transmitted at a shared pre-configured uplink resource opportunity or within a group.

[0486] Optionally, the shared pre-configured uplink resource response window timer or the contention resolution timer represents a window in which the terminal device monitors the network response after sending the first message.

[0487] Optionally, the terminal device performs a first process based on the first configuration, including:

[0488] In response to a first condition being met, a first message is sent based on a first configuration.

[0489] Optionally, the first condition is satisfied, including at least one of the following:

[0490] The upper layer requests to establish or restore a radio resource control connection;

[0491] The terminal device is configured to use shared pre-configured uplink resources;

[0492] The terminal device has valid shared pre-configured uplink resources;

[0493] The terminal equipment has a valid timing advance;

[0494] The terminal device stores a next-hop link counter;

[0495] The uplink data does not exceed the transport block size.

[0496] Optionally, multiple terminal devices share pre-configured uplink resources.

[0497] Optionally, the shared pre-configured uplink resources are sent via a system message.

[0498] Optionally, the shared pre-configured uplink resources are sent via radio resource control signaling.

[0499] Optionally, sending the first message based on the first configuration includes at least one of the following:

[0500] Selecting a timing to share pre-configured uplink resources or sending the first message in groups;

[0501] Selecting to send the first message at the next nearest shared pre-configured uplink resource opportunity or group;

[0502] Repeating N times the first message within a shared pre-configured uplink resource opportunity or group;

[0503] Selecting N shared pre-configured uplink resource opportunities within the shared pre-configured uplink resource opportunity or group based on a first rule to send a first message;

[0504] The first message carries the shared pre-configured uplink resource opportunity or the location information of the shared pre-configured uplink resource opportunity selected in the group.

[0505] Optionally, the first rule may be, for example, random selection or selection based on terminal device identification and / or shared preconfigured uplink resource (SPUR) packet length, and / or selection of shared preconfigured uplink resource timing based on auxiliary parameters provided by the network device.

[0506] Optionally, after sending the first message, the terminal device starts a shared pre-configured uplink resource response window timer or a contention resolution timer and monitors the physical uplink shared channel (PDCCH).

[0507] Optionally, the terminal device starts a shared pre-configured uplink resource response window timer or a contention resolution timer after repeatedly sending the first message for the last time.

[0508] Optionally, after the shared pre-configured uplink resource opportunity group ends, the terminal device starts the shared pre-configured uplink resource response window timer or the contention resolution timer. This is because, in the case of repeated transmission, when a conflict occurs, the network device may rely on the demodulation results of other terminal devices in the group to demodulate the current terminal device's data (interference cancellation), so it is necessary to delay the start of the timer.

[0509] Optionally, the terminal device may also need to delay a fixed time and / or the RTT between the terminal device and the network device when starting the shared pre-configured uplink resource response window timer or the contention resolution timer.

[0510] Optionally, the network device detects the physical uplink shared channel at the corresponding shared pre-configured uplink resource opportunity, and sends response information if the uplink information of the terminal device is successfully detected.

[0511] Optionally, before the shared pre-configured uplink resource response window timer or the contention resolution timer times out, if the terminal device receives a response that matches the terminal device, it indicates that the shared pre-configured uplink resource transmission is successful or the contention resolution is successful.

[0512] Optionally, the terminal device receives a response that matches the terminal device, including at least one of the following:

[0513] The terminal device successfully detects a physical downlink control channel identified, scrambled, or addressed using the first RNTI;

[0514] The downlink control information or media access control protocol data unit or second message received by the terminal device includes identification information of the terminal device;

[0515] The media access control protocol data unit or the second message received by the terminal device matches the first message;

[0516] The terminal device successfully detects a physical downlink control channel identified or scrambled using the second RNTI;

[0517] The terminal device receives the layer 1 confirmation message.

[0518] Optionally, the second message is MSG4.

[0519] Optionally, the second message may specifically be an RRC EarlyDataComplete or RRCConnectionRelease message.

[0520] Optionally, the first RNTI is predefined by the system, or the first RNTI is calculated by the terminal device according to a selected shared pre-configured uplink resource opportunity or a shared pre-configured uplink resource opportunity group.

[0521] Optionally, the identification information is a second RNTI or a temporary mobile user identity code.

[0522] Optionally, the identification information is sent to the terminal device via a radio resource control message.

[0523] Optionally, the second RNTI may be a C-RNTI.

[0524] Optionally, the response information may include identification information of at least one terminal device.

[0525] Optionally, the response information may include scheduling information of the physical downlink shared channel.

[0526] Optionally, the network device configures whether the terminal device can use SPUR through an RRC message (such as an RRC release message). Optionally, the network device can control the number of terminal devices that can use SPUR, thereby reducing contention.

[0527] Through the technical solution of this embodiment, the network device sends the first configuration, and the terminal device performs the first processing based on the first configuration, which clarifies the contention-based MSG3 transmission process and can support the improvement of uplink capacity.

[0528] Seventh embodiment

[0529] Please refer to Figure 11, which is a schematic diagram of the structure of the processing device provided in the embodiment of the present application. The device can be installed in or is the terminal device in the above method embodiment. As shown in Figure 11, the processing device 160 includes:

[0530] The processing module 1601 is configured to perform a first process based on a first configuration.

[0531] Optionally, the first configuration includes at least one of the following:

[0532] Shared pre-configured uplink resource timing configuration;

[0533] Shared pre-configured uplink resource timing group configuration;

[0534] Shared pre-configured uplink resource time-frequency domain resource configuration;

[0535] Repeat the sending times N;

[0536] Shared pre-configured uplink resource response window timer or contention resolution timer;

[0537] Maximum transport block size.

[0538] Optionally, the device further comprises at least one of the following:

[0539] The first configuration is for first message transmission without using MSG1 / RAR;

[0540] The shared pre-configured uplink resource timing configuration indicates the time domain position and / or period of the shared uplink resource;

[0541] The shared pre-configured uplink resource opportunity grouping configuration indicates grouping the shared pre-configured uplink resource opportunities;

[0542] The shared pre-configured uplink resource opportunity group configuration includes a group start position and / or a group length;

[0543] The number of repetitions N represents the number of times the first message is repetitively sent on a shared pre-configured uplink resource opportunity or within a group;

[0544] The shared pre-configured uplink resource response window timer or the contention resolution timer represents the window in which the terminal device monitors the network response after sending the first message.

[0545] Optionally, performing a first process based on the first configuration includes:

[0546] In response to a first condition being met, a first message is sent based on a first configuration.

[0547] Optionally, the first condition is satisfied, including at least one of the following:

[0548] The upper layer requests to establish or restore a radio resource control connection;

[0549] The terminal device is configured to use shared pre-configured uplink resources;

[0550] The terminal device has valid shared pre-configured uplink resources;

[0551] The terminal equipment has a valid timing advance;

[0552] The terminal device stores a next-hop link counter;

[0553] The uplink data does not exceed the transport block size.

[0554] Optionally, sending the first message based on the first configuration includes at least one of the following:

[0555] Selecting a timing to share pre-configured uplink resources or sending the first message in groups;

[0556] Selecting to send the first message at the next nearest shared pre-configured uplink resource opportunity or group;

[0557] Repeating N times the first message within a shared pre-configured uplink resource opportunity or group;

[0558] Selecting N shared pre-configured uplink resource opportunities within the shared pre-configured uplink resource opportunity or group based on a first rule to send a first message;

[0559] The first message carries the shared pre-configured uplink resource opportunity or the location information of the shared pre-configured uplink resource opportunity selected in the group.

[0560] Optionally, the device further comprises at least one of the following:

[0561] Start the shared pre-configured uplink resource response window timer or contention resolution timer;

[0562] After the shared pre-configured uplink resource opportunity grouping ends, starting the shared pre-configured uplink resource response window timer or the contention resolution timer;

[0563] If a response matching that of the terminal device is received before the shared pre-configured uplink resource response window timer or the contention resolution timer times out, the shared pre-configured uplink resource transmission is successful or the contention resolution is successful.

[0564] Optionally, the received response that matches the terminal device includes at least one of the following:

[0565] Successfully detecting a physical downlink control channel identified, scrambled, or addressed using the first RNTI;

[0566] The received downlink control information or media access control protocol data unit or second message includes identification information of the terminal device;

[0567] The received MAC protocol data unit or second message matches the first message;

[0568] detecting a physical downlink control channel identified or scrambled using a second RNTI;

[0569] A layer 1 confirmation message is received.

[0570] Optionally, the device further comprises at least one of the following:

[0571] The first RNTI is predefined by the system;

[0572] The first RNTI is calculated by the terminal device according to the selected shared pre-configured uplink resource opportunity or the shared pre-configured uplink resource opportunity group;

[0573] The identification information is a second RNTI or a temporary mobile user identity code;

[0574] The identification information is sent to the terminal device via a radio resource control message;

[0575] The second RNTI is the C-RNTI.

[0576] The processing device provided in the embodiment of the present application has similar implementation principles and beneficial effects to the technical solutions shown in the above-mentioned corresponding method embodiments, and will not be described in detail here.

[0577] Please refer to Figure 12, which is a second structural diagram of a processing device provided in an embodiment of the present application. The device can be installed in or be the network device in the above method embodiment. As shown in Figure 12, the device 170 includes:

[0578] The sending module 1701 is configured to send a first configuration so that the terminal device performs a first process based on the first configuration.

[0579] Optionally, the first configuration includes at least one of the following:

[0580] Shared pre-configured uplink resource timing configuration;

[0581] Shared pre-configured uplink resource timing group configuration;

[0582] Shared pre-configured uplink resource time-frequency domain resource configuration;

[0583] Repeat the sending times N;

[0584] Shared pre-configured uplink resource response window timer or contention resolution timer;

[0585] Maximum transport block size.

[0586] Optionally, the device further comprises at least one of the following:

[0587] The first configuration is for first message transmission without using MSG1 / RAR;

[0588] The shared pre-configured uplink resource timing configuration indicates the time domain position and / or period of the shared uplink resource;

[0589] The shared pre-configured uplink resource opportunity grouping configuration indicates grouping the shared pre-configured uplink resource opportunities;

[0590] The shared pre-configured uplink resource opportunity group configuration includes a group start position and / or a group length;

[0591] The number of repetitions N represents the number of times the first message is repetitively sent on a shared pre-configured uplink resource opportunity or within a group;

[0592] The shared pre-configured uplink resource response window timer or the contention resolution timer represents the window in which the terminal device monitors the network response after sending the first message.

[0593] Optionally, the terminal device performs a first process based on the first configuration, including:

[0594] In response to the first condition being met, the terminal device sends a first message based on the first configuration.

[0595] Optionally, the first condition is satisfied, including at least one of the following:

[0596] The upper layer requests to establish or restore a radio resource control connection;

[0597] The terminal device is configured to use shared pre-configured uplink resources;

[0598] The terminal device has valid shared pre-configured uplink resources;

[0599] The terminal equipment has a valid timing advance;

[0600] The terminal device stores a next-hop link counter;

[0601] The uplink data does not exceed the transport block size.

[0602] Optionally, the terminal device sends a first message based on the first configuration, including at least one of the following:

[0603] The terminal device selects a timing to share pre-configured uplink resources or sends the first message in groups;

[0604] The terminal device selects to send the first message at the next nearest shared pre-configured uplink resource opportunity or group;

[0605] The terminal device repeatedly sends the first message N times in a shared pre-configured uplink resource opportunity or group;

[0606] The terminal device selects N shared pre-configured uplink resource opportunities based on the first rule within the shared pre-configured uplink resource opportunity or group to send the first message;

[0607] The first message carries the shared pre-configured uplink resource opportunity or the location information of the shared pre-configured uplink resource opportunity selected in the group.

[0608] Optionally, the device further comprises at least one of the following:

[0609] Detecting the physical uplink shared channel at the corresponding shared pre-configured uplink resource opportunity, and sending a response message if uplink information of the terminal device is successfully detected;

[0610] The terminal device starts a shared pre-configured uplink resource response window timer or a contention resolution timer;

[0611] After the shared pre-configured uplink resource opportunity grouping ends, the terminal device starts the shared pre-configured uplink resource response window timer or the contention resolution timer;

[0612] If the terminal device receives a response that matches the terminal device before the shared pre-configured uplink resource response window timer or the contention resolution timer times out, the shared pre-configured uplink resource transmission is successful or the contention resolution is successful.

[0613] Optionally, the terminal device receives a response that matches the terminal device, including at least one of the following:

[0614] The terminal device successfully detects a physical downlink control channel identified, scrambled, or addressed using the first RNTI;

[0615] The downlink control information or media access control protocol data unit or second message received by the terminal device includes identification information of the terminal device;

[0616] The media access control protocol data unit or the second message received by the terminal device matches the first message;

[0617] The terminal device successfully detects a physical downlink control channel identified or scrambled using the second RNTI;

[0618] The terminal device receives the layer 1 confirmation message.

[0619] Optionally, the device further comprises at least one of the following:

[0620] The response information includes identification information of at least one terminal device;

[0621] The response message includes scheduling information of the physical downlink shared channel;

[0622] The first RNTI is predefined by the system;

[0623] The first RNTI is calculated by the terminal device according to the selected shared pre-configured uplink resource opportunity or the shared pre-configured uplink resource opportunity group;

[0624] The identification information is a second RNTI or a temporary mobile user identity code;

[0625] The identification information is sent to the terminal device via a radio resource control message;

[0626] The second RNTI is the C-RNTI.

[0627] The processing device provided in the embodiment of the present application has similar implementation principles and beneficial effects to the technical solutions shown in the above-mentioned corresponding method embodiments, and will not be described in detail here.

[0628] Refer to Figure 13, which is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. As shown in Figure 13, the communication device 180 described in this embodiment can be the terminal device (or component that can be used for a terminal device) or network device (or component that can be used for a network device) mentioned in the aforementioned method embodiment. Communication device 180 can be used to implement the methods corresponding to the terminal device or network device described in the aforementioned method embodiment. For details, please refer to the description of the aforementioned method embodiment.

[0629] The communication device 180 may include one or more processors 1801, also referred to as processing units, which may implement certain control or processing functions. Processor 1801 may be a general-purpose processor or a dedicated processor. For example, it may be a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, while the central processing unit may be used to control the communication device, execute software programs, and process software program data.

[0630] Optionally, the processor 1801 may also store instructions 1803 or data (eg, intermediate data). Optionally, the instructions 1803 may be executed by the processor 1801, so that the communication device 180 executes the method corresponding to the terminal device or network device described in the above method embodiment.

[0631] Optionally, the communication device 180 may include a circuit that can implement the functions of sending, receiving, or communicating in the aforementioned method embodiments.

[0632] Optionally, the communication device 180 may include one or more memories 1802 , on which instructions 1804 may be stored. The instructions may be executed on the processor 1801 , so that the communication device 180 performs the method described in the above method embodiment.

[0633] Optionally, data may also be stored in the memory 1802. The processor 1801 and the memory 1802 may be provided separately or integrated together.

[0634] Optionally, the communication device 180 may further include a transceiver 1805 and / or an antenna 1806. The processor 1801 may be referred to as a processing unit, and controls the communication device 180 (terminal device, core network device, or wireless access network device). The transceiver 1805 may be referred to as a transceiver unit, transceiver, transceiver circuit, or transceiver, and is used to implement the transceiver functions of the communication device 180.

[0635] Optionally, if the communication device 180 is used to implement operations corresponding to the terminal device in the above embodiments, for example, the transceiver 1805 can receive the first configuration; and the processor 1801 can perform the first processing based on the first configuration.

[0636] Optionally, the specific implementation process of the processor 1801 and the transceiver 1805 can be found in the relevant descriptions of the above embodiments, and will not be repeated here.

[0637] Optionally, if the communication device 180 is used to implement operations corresponding to the network devices in the above embodiments, for example, the first configuration may be sent by the transceiver 1805 .

[0638] Optionally, the specific implementation process of the processor 1801 and the transceiver 1805 can be found in the relevant descriptions of the above embodiments, and will not be repeated here.

[0639] The processor 1801 and transceiver 1805 described in this application can be implemented on an IC (Integrated Circuit), an analog integrated circuit, an RFIC (Radio Frequency Integrated Circuit), a mixed-signal integrated circuit, an ASIC (Application Specific Integrated Circuit), a PCB (Printed Circuit Board), an electronic device, etc. The processor 1801 and transceiver 1805 can also be manufactured using various integrated circuit process technologies, such as CMOS (Complementary Metal Oxide Semiconductor), NMOS (N Metal-Oxide-Semiconductor), PMOS (Positive Channel Metal Oxide Semiconductor), BJT (Bipolar Junction Transistor), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0640] In this application, a communication device may be a terminal device (such as a mobile phone) or a network device (such as a base station), and the specific definition needs to be determined based on the context. In addition, the terminal device can be implemented in various forms. For example, the terminal devices described in this application may include mobile terminals such as mobile phones, tablet computers, laptop computers, PDAs, portable media players (PMPs), navigation devices, wearable devices, smart bracelets, pedometers, etc., as well as fixed terminal devices such as digital TVs and desktop computers.

[0641] Although the communication device is described above by taking a terminal device or a network device as an example, the scope of the communication device described in this application is not limited to the above-mentioned terminal device or network device, and the structure of the communication device may not be limited to Figure 13. The communication device may be an independent device or may be part of a larger device.

[0642] An embodiment of the present application further provides a communication system, including: a terminal device as in any of the above embodiments; and a network device as in any of the above embodiments.

[0643] An embodiment of the present application also provides a communication device, including a memory and a processor, wherein a processing program is stored in the memory, and when the processing program is executed by the processor, the steps of the processing method in any of the above embodiments are implemented.

[0644] The communication device in this application can be a terminal device (such as a mobile phone) or a network device (such as a base station). The specific reference needs to be clarified based on the context.

[0645] An embodiment of the present application further provides a computer-readable storage medium, on which a processing program is stored. When the processing program is executed by a processor, the steps of the processing method in any of the above embodiments are implemented.

[0646] In the embodiments of the communication device and storage medium provided in the embodiments of the present application, all technical features of any of the above-mentioned processing method embodiments may be included. The expansion and explanation content of the specification are basically the same as those of the embodiments of the above-mentioned methods, and will not be repeated here.

[0647] An embodiment of the present application further provides a computer program product, which includes computer program code. When the computer program code runs on a computer, the computer executes the methods in the various possible implementation modes described above.

[0648] An embodiment of the present application also provides a chip, including a memory and a processor, wherein the memory is used to store computer programs, and the processor is used to call and run the computer programs from the memory, so that a device equipped with the chip executes the methods in the various possible implementation modes as described above.

[0649] It is understood that the above scenarios are merely examples and do not limit the application scenarios of the technical solutions provided in the embodiments of this application. The technical solutions of this application can also be applied to other scenarios. For example, those skilled in the art will appreciate that with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application will also be applicable to similar technical problems.

[0650] The serial numbers of the above embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0651] The steps in the method of the embodiment of the present application can be adjusted in order, combined and deleted according to actual needs.

[0652] The units in the device of the embodiment of the present application can be merged, divided and deleted according to actual needs.

[0653] In this application, the same or similar terminology, technical solutions and / or application scenario descriptions are generally only described in detail the first time they appear. When they appear again later, they are generally not repeated for the sake of brevity. When understanding the technical solutions and other contents of this application, for the same or similar terminology, technical solutions and / or application scenario descriptions that are not described in detail later, you can refer to the previous relevant detailed descriptions.

[0654] In this application, the description of each embodiment has its own focus. For parts that are not described or recorded in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0655] The various technical features of the technical solution of this application can be combined arbitrarily. In order to make the description concise, not all possible combinations of the various technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0656] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as above, and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, controlled terminal device, or network device, etc.) to execute the method of each embodiment of the present application.

[0657] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can 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 process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a storage medium or transmitted from one storage medium to another storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium can be a magnetic medium (e.g., a floppy disk, a storage disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state storage disk Solid State Disk (SSD)).

[0658] The above are only preferred embodiments of the present application and do not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A processing method, wherein: Applied to terminal equipment, including the steps of: S2: Execute a first process based on the first configuration.

2. The method according to claim 1, wherein: The first configuration includes at least one of the following: Shared pre-configured uplink resource timing configuration; Shared pre-configured uplink resource timing group configuration; Shared pre-configured uplink resource time-frequency domain resource configuration; Repeat the sending times N; Shared pre-configured uplink resource response window timer or contention resolution timer; Maximum transport block size.

3. The method according to claim 2, wherein: Also includes at least one of the following: The first configuration is for the first message transmission without using MSG1 / RAR; The shared pre-configured uplink resource opportunity configuration indicates the time domain position and / or period of the shared uplink resource; The shared pre-configured uplink resource opportunity grouping configuration means grouping the shared pre-configured uplink resource opportunities; The shared pre-configured uplink resource opportunity group configuration includes a group start position and / or a group length; The number of repeated transmissions N represents the number of times the first message is repeatedly transmitted at the shared pre-configured uplink resource opportunity or within a group; The shared pre-configured uplink resource response window timer or the contention resolution timer indicates a window in which the terminal device monitors a network response after sending a first message.

4. The method according to claim 1, wherein: Step S2 comprises: In response to a first condition being met, a first message is sent based on a first configuration.

5. The method according to claim 4, wherein: The first condition is met, including at least one of the following: The upper layer requests to establish or restore a radio resource control connection; The terminal device is configured to use the shared pre-configured uplink resources; The terminal device has valid shared pre-configured uplink resources; The terminal equipment has a valid timing advance; The terminal device stores a next-hop link counter; The uplink data does not exceed the transport block size.

6. The method according to claim 4, wherein: Sending a first message based on the first configuration includes at least one of the following: Selecting a timing to share pre-configured uplink resources or sending the first message in groups; Selecting to send the first message at the next nearest shared pre-configured uplink resource opportunity or group; Repeating sending the first message N times within a shared pre-configured uplink resource opportunity or group; Selecting N shared pre-configured uplink resource opportunities within a shared pre-configured uplink resource opportunity or group based on a first rule to send a first message; The first message carries the location information of the shared pre-configured uplink resource opportunity selected in the shared pre-configured uplink resource opportunity or the group.

7. The method according to claim 4, wherein: The method further comprises at least one of the following: Starting a shared pre-configured uplink resource response window timer or a contention resolution timer; After the shared pre-configured uplink resource opportunity grouping ends, starting the shared pre-configured uplink resource response window timer or the contention resolution timer; If a response matching that of the terminal device is received before the shared pre-configured uplink resource response window timer or the contention resolution timer times out, the shared pre-configured uplink resource transmission is successful or the contention resolution is successful.

8. The method according to claim 7, wherein: A response matching that of the terminal device is received, including at least one of the following: Successfully detecting a physical downlink control channel identified or scrambled using the first RNTI; The received downlink control information or media access control protocol data unit or second message includes identification information of the terminal device; The received media access control protocol data unit or second message matches the first message; detecting a physical downlink control channel identified or scrambled using a second RNTI; A layer 1 confirmation message is received.

9. The method according to claim 8, wherein: Also includes at least one of the following: The first RNTI is predefined by the system; The first RNTI is calculated by the terminal device according to the selected shared pre-configured uplink resource opportunity or shared pre-configured uplink resource opportunity group; The identification information is a second RNTI or a temporary mobile user identification code; The identification information is sent to the terminal device via a radio resource control message; The second RNTI is the C-RNTI.

10. A processing method, wherein: Applied to network equipment, including the steps of: S1: Send a first configuration so that the terminal device performs a first process based on the first configuration.

11. The method according to claim 10, wherein: The first configuration includes at least one of the following: Shared pre-configured uplink resource timing configuration; Shared pre-configured uplink resource timing group configuration; Shared pre-configured uplink resource time-frequency domain resource configuration; Repeat the sending times N; Shared pre-configured uplink resource response window timer or contention resolution timer; Maximum transport block size.

12. The method according to claim 11, wherein: Also includes at least one of the following: The first configuration is for the first message transmission without using MSG1 / RAR; The shared pre-configured uplink resource opportunity configuration indicates the time domain position and / or period of the shared uplink resource; The shared pre-configured uplink resource opportunity grouping configuration means grouping the shared pre-configured uplink resource opportunities; The shared pre-configured uplink resource opportunity group configuration includes a group start position and / or a group length; The number of repeated transmissions N represents the number of times the first message is repeatedly transmitted at the shared pre-configured uplink resource opportunity or within a group; The shared pre-configured uplink resource response window timer or the contention resolution timer indicates a window in which the terminal device monitors a network response after sending a first message.

13. The method according to claim 10, wherein: The terminal device performs a first process based on the first configuration, including: In response to satisfying the first condition, the terminal device sends a first message based on the first configuration.

14. The method according to claim 13, wherein: The first condition is met, including at least one of the following: The upper layer requests to establish or restore a radio resource control connection; The terminal device is configured to use the shared pre-configured uplink resources; The terminal device has valid shared pre-configured uplink resources; The terminal equipment has a valid timing advance; The terminal device stores a next-hop link counter; The uplink data does not exceed the transport block size.

15. The method according to claim 13, wherein: The terminal device sends a first message based on the first configuration, including at least one of the following: The terminal device selects a timing to share the pre-configured uplink resources or sends the first message in groups; The terminal device selects to send the first message at the next nearest shared pre-configured uplink resource opportunity or group; The terminal device repeatedly sends the first message N times in a shared pre-configured uplink resource opportunity or group; The terminal device selects N shared pre-configured uplink resource opportunities based on the first rule within the shared pre-configured uplink resource opportunity or group to send the first message; The first message carries the location information of the shared pre-configured uplink resource opportunity selected in the shared pre-configured uplink resource opportunity or the group.

16. The method according to claim 13, wherein: Also includes at least one of the following: Detecting the physical uplink shared channel at the corresponding shared pre-configured uplink resource opportunity, and sending a response message if uplink information of the terminal device is successfully detected; The terminal device starts a shared pre-configured uplink resource response window timer or a contention resolution timer; After the shared pre-configured uplink resource opportunity grouping ends, the terminal device starts the shared pre-configured uplink resource response window timer or the contention resolution timer; If the terminal device receives a response that matches the terminal device before the shared pre-configured uplink resource response window timer or the contention resolution timer times out, the shared pre-configured uplink resource transmission is successful or the contention resolution is successful.

17. The method according to claim 16, wherein: The terminal device receives a response that matches the terminal device, including at least one of the following: The terminal device successfully detects a physical downlink control channel identified or scrambled using the first RNTI; The downlink control information or the media access control protocol data unit or the second message received by the terminal device includes identification information of the terminal device; The media access control protocol data unit or the second message received by the terminal device matches the first message; The terminal device successfully detects a physical downlink control channel identified or scrambled using the second RNTI; The terminal device receives a layer 1 confirmation message.

18. The method according to claim 17, wherein: Also includes at least one of the following: The response information includes identification information of at least one terminal device; The response message includes scheduling information of the physical downlink shared channel; The first RNTI is predefined by the system; The first RNTI is calculated by the terminal device according to the selected shared pre-configured uplink resource opportunity or shared pre-configured uplink resource opportunity group; The identification information is a second RNTI or a temporary mobile user identification code; The identification information is sent to the terminal device via a radio resource control message; The second RNTI is the C-RNTI.

19. A communication device, wherein: include: A memory and a processor, wherein a processing program is stored in the memory, and the processing program is executed by the processor to implement the processing method according to claim 1 or 10.

20. A computer-readable storage medium, wherein: The computer-readable storage medium stores a processing program, and the processing program is executed by a processor to implement the processing method according to claim 1 or 10.

Images