CN116419146A

CN116419146A - Communication method and device

Info

Publication number: CN116419146A
Application number: CN202111645990.0A
Authority: CN
Inventors: 雷珍珠; 周化雨; 徐志昆
Original assignee: Spreadtrum Semiconductor Nanjing Co Ltd
Current assignee: Spreadtrum Semiconductor Nanjing Co Ltd
Priority date: 2021-12-30
Filing date: 2021-12-30
Publication date: 2023-07-11
Also published as: WO2023125381A1

Abstract

The embodiment of the application provides a communication method and a device, and relates to the technical field of communication, wherein the method comprises the following steps: the terminal equipment determines first information according to ephemeris information and/or GNSS positioning information, wherein the first information is used for indicating the length or the wave beam of an uplink channel transmission section, and the length or the wave beam of the uplink channel transmission section is associated with resources for random access; the terminal device transmits a random access request message based on the resource. The method provided by the embodiment of the invention can maintain uplink synchronization under the scene of quicker TA change, and is beneficial to improving the uplink communication performance.

Description

Communication method and device

Technical Field

The embodiment of the application relates to the technical field of communication, in particular to a communication method and device.

Background

In a non-terrestrial network (Non Terrestrial Networks, NTN), the rate of change of the upstream Timing Advance (TA) and the magnitude of the doppler rate of change are related to the position between the terminal device and the satellite. The faster moving speed of the satellite causes faster propagation delay between the terminal device and the satellite, thereby causing uplink out-of-step. In order to reduce the risk of uplink out-of-step, the terminal device needs to perform TA adjustment frequently.

However, in NTN, one transmission of uplink data needs to last for a long time. Therefore, research on how to maintain uplink synchronization during uplink data transmission has important practical value for improving satellite communication performance.

Disclosure of Invention

The embodiment of the application provides a communication method and a communication device, which can realize the rapid uplink synchronization of terminal equipment under the scene of rapid TA change and are beneficial to improving the uplink communication performance.

In a first aspect, an embodiment of the present application provides a communication method, including:

the terminal equipment determines first information according to ephemeris information and/or GNSS positioning information, wherein the first information is used for indicating the length or the wave beam of an uplink channel transmission section, and the length or the wave beam of the uplink channel transmission section is associated with resources for random access;

the terminal device transmits a random access request message based on the resource.

In the embodiment of the present invention, since the association relationship exists between the resource and the transmission segment length or the beam, the terminal device can determine the resource for sending the random access request message according to the ephemeris information and/or the GNSS positioning information, so that the uplink synchronization can be maintained in the scene of faster TA change, and the uplink communication performance can be improved.

In one possible implementation manner, the resource is a carrier, and the uplink channel transmission segment length is associated with the resource, including:

the uplink channel transmission segment length is associated with a carrier or the uplink channel transmission segment length is associated with a carrier group comprising carriers.

In one possible implementation manner, the first information is used to indicate a length of an uplink channel transmission segment, and includes:

the first information is used for indicating the physical random access channel PRACH transmission segment length and the physical uplink shared channel PUSCH transmission segment length.

In one possible implementation manner, the method further includes:

and the terminal equipment sends uplink data according to the length of the PUSCH transmission section.

the first information is used to indicate a PRACH transmission segment length, wherein the PRACH transmission segment length is associated with a PUSCH transmission segment length.

In one possible implementation manner, the method further includes:

and the terminal equipment sends uplink data according to the PUSCH transmission section length associated with the PRACH transmission section length.

In one possible implementation manner, the resource is a random access opportunity RO and/or a preamble, and the uplink channel transmission segment length is associated with the resource, including:

The uplink channel transport segment length is associated with RO and/or the preamble.

the first information is used to indicate a PUSCH transmission segment length.

In one possible implementation manner, the first information is used to indicate a beam, where the beam is associated with a resource, and includes:

the beam is associated with a carrier.

In one possible implementation manner, the method further includes:

the terminal equipment receives a random access response message, wherein the random access response message is used for indicating the length of the PUSCH transmission section.

In one possible implementation manner, the method further includes:

the terminal device receives indication information, where the indication information is used to indicate an uplink channel transmission segment length or a beam associated with a resource for random access.

In a second aspect, an embodiment of the present application further provides a communication method, including:

the network equipment receives a random access request message based on a resource for random access, wherein the resource is associated with the length or the wave beam of an uplink channel transmission segment;

the network device sends a random access response message to the terminal device.

In one possible implementation manner, the resource is a carrier, and the resource is associated with the uplink channel transmission segment length, including:

The carrier is associated with an uplink channel transmission segment length, or a carrier group is associated with an uplink channel transmission segment length, the carrier group comprising carriers.

In one possible implementation manner, the uplink channel transmission segment length includes a physical random access channel PRACH transmission segment length and a physical uplink shared channel PUSCH transmission segment length; or,

the length of the uplink channel transmission segment is the length of the PRACH transmission segment, and the length of the PRACH transmission segment is related to the length of the PUSCH transmission segment.

In one possible implementation manner, the network device receives a random access request message based on a resource for random access, including:

the network device receives a random access request message on the resource according to the PRACH transmission segment length associated with the resource.

In one possible implementation, the resource is a random access opportunity RO and/or a preamble, and the resource is associated with the uplink channel transmission segment length.

the network device receives the random access request message according to the RO and/or the preamble associated with the uplink channel transmission segment length.

In one possible implementation, the uplink channel transmission segment length is a PUSCH transmission segment length.

In one possible implementation manner, the resource is a carrier, the resource is associated with a beam, the network device receives a random access request message based on the resource for random access, and the method includes:

the network device receives a random access request message based on the beam associated with the resource.

In one possible implementation, a random access response message is used to indicate the PUSCH transmission segment length.

In one possible implementation manner, the method further includes:

and the network equipment receives the uplink data according to the length of the PUSCH transmission section.

In one possible implementation manner, the method further includes:

the network device transmits indication information for indicating an uplink channel transmission segment length or beam associated with the resource for random access.

In a third aspect, an embodiment of the present application provides a communication apparatus, including: a processor and a memory for storing a computer program; the processor is configured to execute a computer program for performing the communication method as described in the first aspect.

In a fourth aspect, embodiments of the present application further provide a communication apparatus, including: a processor and a memory for storing a computer program; the processor is configured to execute a computer program for performing the communication method as described in the second aspect.

In a fifth aspect, embodiments of the present application provide a computer-readable storage medium having a computer program stored therein, which when run on a computer, causes the computer to implement the communication method as described in the first to second aspects.

In a sixth aspect, embodiments of the present application provide a computer program product comprising a computer program which, when executed by a computer, causes the computer to implement a communication method as described in the first or second aspect.

In a possible implementation manner, the program in the sixth aspect may be stored in whole or in part on a storage medium packaged together with the processor, or may be stored in part or in whole on a memory not packaged together with the processor.

In a seventh aspect, embodiments of the present application provide a communication apparatus, including: one or more functional modules for performing any of the communication methods provided in the first aspect.

In an eighth aspect, embodiments of the present application provide a communication apparatus, including: one or more functional modules for performing any of the communication methods provided in the second aspect.

In a ninth aspect, there is provided a communication system comprising: a communication device for performing any one of the methods provided in the first aspect and a communication device for performing any one of the methods provided in the second aspect.

Wherein the communication apparatus in the third aspect and the seventh aspect may be a chip or a terminal device, and the communication apparatus in the fourth aspect and the eighth aspect may be a chip or a network device.

Drawings

Fig. 1 is a schematic diagram of uplink data segment transmission provided in an embodiment of the present application;

fig. 2 is a schematic architecture diagram of a non-terrestrial network scenario provided in the present application;

FIG. 3 is a flow chart of one embodiment of a communication method provided herein;

FIG. 4 is a flow chart of another embodiment of a communication method provided herein;

FIG. 5 is a flow chart of a further embodiment of a communication method provided herein;

FIG. 6 is a flow chart of yet another embodiment of a communication method provided herein;

FIG. 7 is a flow chart of yet another embodiment of a communication method provided herein;

FIG. 8 is a flow chart of yet another embodiment of a communication method provided herein;

FIG. 9 is a flow chart of yet another embodiment of a communication method provided herein;

Fig. 10 is a schematic structural diagram of an embodiment of a communication device provided in the present application;

fig. 11 is a schematic structural diagram of another embodiment of a communication device provided in the present application;

fig. 12 is a schematic structural diagram of a further embodiment of a communication device provided in the present application.

Detailed Description

In the embodiment of the present application, unless otherwise specified, the character "/" indicates that the front-rear association object is one or a relationship. For example, A/B may represent A or B. "and/or" describes an association relationship of an association object, meaning that three relationships may exist. For example, a and/or B may represent: a exists alone, A and B exist together, and B exists alone.

It should be noted that the terms "first," "second," and the like in the embodiments of the present application are used for distinguishing between description and not necessarily for indicating or implying a relative importance or number of features or characteristics that are indicated, nor does it imply a sequential order.

In the embodiments of the present application, "at least one" means one or more, and "a plurality" means two or more. Furthermore, "at least one item(s)" below, or the like, refers to any combination of these items, and may include any combination of single item(s) or plural items(s). For example, at least one (one) of A, B or C may represent: a, B, C, a and B, a and C, B and C, or A, B and C. Wherein each of A, B, C may itself be an element or a collection comprising one or more elements.

In this application embodiments, "exemplary," "in some embodiments," "in another embodiment," etc. are used to indicate an example, instance, or illustration. Any embodiment or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, the term use of an example is intended to present concepts in a concrete fashion.

"of", "corresponding" and "corresponding" in the embodiments of the present application may be sometimes used in combination, and it should be noted that the meaning to be expressed is consistent when the distinction is not emphasized. In the embodiments of the present application, communications and transmissions may sometimes be mixed, and it should be noted that, when the distinction is not emphasized, the meaning expressed is consistent. For example, a transmission may include sending and/or receiving, either nouns or verbs.

The equal to that relates to in this application embodiment can be with being greater than even using, is applicable to the technical scheme that adopts when being greater than, also can be with being less than even using, is applicable to the technical scheme that adopts when being less than. It should be noted that when the number is equal to or greater than the sum, the number cannot be smaller than the sum; when the value is equal to or smaller than that used together, the value is not larger than that used together.

Some terms related to the embodiments of the present application are explained below to facilitate understanding by those skilled in the art.

1. And a terminal device. In this embodiment of the present application, the terminal device is a device with a wireless transceiver function, and may be referred to as a terminal, a User Equipment (UE), a Mobile Station (MS), a Mobile Terminal (MT), an access terminal device, a vehicle-mounted terminal device, an industrial control terminal device, a UE unit, a UE station, a mobile station, a remote terminal device, a mobile device, a UE terminal device, a wireless communication device, a UE agent, or a UE apparatus. The terminal device may be fixed or mobile. It should be noted that the terminal device may support at least one wireless communication technology, such as long term evolution (long term evolution, LTE), new radio, NR, etc. For example, the terminal device may be a mobile phone, a tablet, a desktop, a notebook, a kiosk, a car-mounted terminal, a Virtual Reality (VR) terminal device, an augmented reality (augmented reality, AR) terminal device, a wireless terminal in an industrial control (industrial control), a wireless terminal in a self-driving (self-driving), a wireless terminal in a teleoperation (remote medical surgery), a wireless terminal in a smart grid, a wireless terminal in a transportation security (transportation safety), a wireless terminal in a smart city, a wireless terminal in a smart home (smart home), a cellular phone, a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (wireless local loop, WLL) station, a personal digital assistant (personal digital assistant, PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a wearable device, a terminal in a future mobile communication network, or a public land mobile network (public land mobile network) in a future mobile communication network, etc. In some embodiments of the present application, the terminal device may also be a device with a transceiver function, such as a chip system. The chip system may include a chip and may also include other discrete devices.

2. A network device. The network device in the embodiment of the present application is a device that provides a wireless communication function for a terminal device, and may also be referred to as an access network device, a radio access network (radio access network, RAN) device, or the like. Wherein the network device may support at least one wireless communication technology, e.g., LTE, NR, etc. By way of example, network devices include, but are not limited to: next generation base stations (gnbs), evolved node bs (enbs), radio network controllers (radio network controller, RNCs), node bs (node bs, NB), base station controllers (base station controller, BSC), base transceiver stations (base transceiver station, BTS), home base stations (e.g., home evolved node B, or home node B, HNB), baseband units (BBUs), transceiving points (transmitting and receiving point, TRPs), transmitting points (transmitting point, TP), mobile switching centers, and the like in a fifth generation mobile communication system (5 th-generation, 5G). The network device may also be a wireless controller, a Centralized Unit (CU), and/or a Distributed Unit (DU) in the cloud wireless access network (cloud radio access network, CRAN) scenario, or the network device may be a relay station, an access point, an in-vehicle device, a terminal device, a wearable device, and a network device in future mobile communication or a network device in a future evolved PLMN, etc. In some embodiments, the network device may also be an apparatus, such as a system-on-a-chip, having functionality for providing wireless communication for the terminal device. By way of example, the chip system may include a chip, and may also include other discrete devices.

3. And transmitting the segment of the uplink channel. The uplink channel transmission segment in the embodiment of the present application refers to a plurality of uplink data repeated transmission units. Specifically, taking NTN as an example, in order to ensure reliability of uplink data transmission, the terminal device needs to use a retransmission mechanism to transmit uplink data, i.e. one transmission block (Transmission Block, TB) or random preamble needs to be repeatedly sent multiple times, which results in that one uplink data transmission lasts for a long time. Considering the rapid time delay change of NTN, the uplink data transmission can be segmented, namely N uplink data repeated transmission units are one transmission segment, N values are configured by a network, and N is the length of the uplink channel transmission segment. That is, the length of the uplink channel transmission segment can be understood as the number of uplink data retransmission units per segment after the uplink data transmission segment. Alternatively, in the embodiment of the present application, the length of the uplink channel transmission segment may represent the number of uplink data repeated transmission units in each segment after uplink data transmission segmentation in milliseconds, which is not limited.

For example, in embodiments of the present application, the uplink channel transmission segment may include a physical random access channel (Physical Random Access Channel, PRACH) transmission segment and/or a physical downlink shared channel (physical downlink shared channel, PDSCH) transmission segment.

4. Resources for random access. The resources used for random access in the embodiments of the present application refer to resources used by a terminal device to initiate random access, and may include time domain resources, frequency domain resources, and/or code domain resources. The resources may include, for example, a carrier, a random access occasion (RO), and a Preamble (Preamble).

In NTN, due to the rapid movement of the satellite relative to the terminal device, the propagation delay between the terminal device and the satellite may change rapidly over time, which may cause uplink out-of-step. Therefore, the terminal device needs to perform TA and frequency offset adjustment frequently, so as to achieve synchronization with the satellite.

In the random access procedure, in order to ensure the reliability of the transmission, the uplink data is usually required to be repeatedly sent, so for one uplink transmission (including the transmission of the random access preamble and the uplink data), for example, the transmission of one TB usually needs to last for a long period of time to complete the transmission. Considering the rapid time delay change of the NTN, the primary uplink transmission can be segmented, namely, the primary uplink transmission is divided into a plurality of uplink transmission segments (or uplink channel transmission segments), and the terminal equipment performs time-frequency adjustment again after finishing the transmission of the primary uplink transmission segments so as to adapt to the rapid time delay change. Fig. 1 schematically illustrates a PUSCH transmission segment transmission mode.

In addition, in NTN, the rate of change of the uplink TA and the magnitude of the doppler rate of change are related to the positions of the terminal device and the satellite. If the terminal equipment is located right below the satellite, the change rate of TA and the Doppler change rate are very small; if the terminal device is at the edge of the satellite coverage area (i.e., the terminal device has a large elevation angle relative to the satellite), the rate of change of TA and the rate of change of doppler will be very large. It can be understood that the larger the variation rate of TA and the doppler variation rate, the smaller the transmission segment length of the uplink data; the smaller the rate of change of TA and Doppler, the longer the transmission segment length of the uplink data. Wherein the transmission segment length is the length of a segment of upstream data.

As can be seen, if the transmission segment length of the uplink data is too small, the number of segments of one uplink data transmission is large, which increases the power consumption and complexity of the terminal device for transmitting the uplink data. If the transmission segment length of the uplink data is too long, the time-frequency synchronization accuracy of the uplink data transmission is affected. Considering the rapid air interface transmission delay variation in the NTN scene, how to determine a suitable transmission segment length value of uplink data by the terminal so as to ensure that uplink synchronization is maintained in the uplink data transmission process, and improving the uplink communication performance is a problem to be solved.

Based on the above problems, the embodiment of the application provides a communication method.

The communication method provided in the embodiment of the present application will now be described with reference to fig. 2 and 3.

The communication method provided in the embodiment of the present application may be applied to NTN, referring to fig. 2, fig. 2 is a schematic diagram of an NTN architecture provided in the embodiment of the present application.

As shown in fig. 2, the NTN includes a satellite, a terminal device, and a gateway (also referred to as a ground station). The wireless link between the satellite and the terminal device may be referred to as a service link, the wireless link between the satellite and the gateway may be referred to as a feedback link, and an inter-satellite link for providing a data backhaul may exist between the satellite and the satellite.

Typically, one or several gateways of the NTN need to be connected to a public data network (Public Data Network, PDN), such as the network in fig. 2.

In some embodiments, the network devices in the NTN may be located on land, e.g., the gateway in fig. 2 may be network device-enabled. At this time, the satellite will act as a relay between the terminal device and the gateway, receive the data sent by the terminal device through the service link, and forward the data to the gateway on the ground.

In other embodiments, the network devices in the NTN may also be located on a satellite, e.g., the satellite in fig. 2 may be provided with the functions of the network devices.

In this embodiment of the present application, the terminal device may communicate with the network device, and for convenience of description, the method related to the present application is hereinafter exemplified by taking the network device as a satellite with a base station function.

As shown in fig. 3, a flow chart of a communication method provided in an embodiment of the present application specifically includes the following steps:

in step 301, the terminal device determines first information according to ephemeris information and/or global navigation satellite system (Global Navigation Satellite System, GNSS) positioning information, where the first information is used to indicate an uplink channel transmission segment length or beam, and the uplink channel transmission segment length or beam is associated with a resource for random access.

The ephemeris information is used to indicate satellite orbit information, position information of a satellite, or operation speed information of the satellite, for example. For example, the terminal device may obtain ephemeris information by:

the terminal device may obtain ephemeris information through the system information.

For example, the GNSS positioning information is used to indicate current location information of the terminal device. For example, the terminal device may obtain GNSS positioning information by:

the terminal device may obtain GNSS positioning information via a global positioning system (Global Positioning System, GPS).

In some embodiments, the terminal device may determine the first information by initiating random access, triggering according to ephemeris information and/or GNSS positioning information.

For example, taking the first information for indicating the length of the uplink channel transmission segment as an example, the first information may be the number of uplink data retransmission units. Specifically, the determining, by the terminal device, the first information according to the ephemeris information and/or the GNSS information may be understood as: and the terminal equipment determines the length of the uplink channel transmission segment according to the ephemeris information and/or the GNSS information. For example, the terminal device determines the change rate and the Doppler change rate of the current TA according to ephemeris information and GNSS information; and then determining a proper uplink channel transmission segment length according to the change rate of the current TA and the Doppler change rate.

For example, taking the first information as an example for indicating a beam, the first information may be a beam index or a beam identification, etc. Specifically, the determining, by the terminal device, the first information according to the ephemeris information and/or the GNSS information may be understood as: and the terminal equipment determines the current position information according to the ephemeris information and/or the GNSS information, and determines the beam corresponding to the coverage area according to the position information.

In a specific implementation, the association relationship between the uplink channel transmission segment length or the beam and the resource for random access may be predefined by a protocol, and may be preset in the terminal device and the network device, or may be indicated to the terminal device by the network device through indication information, where the indication information is used to indicate the uplink channel transmission segment length or the beam associated with the resource for random access, or the indication information is used to indicate the association relationship between the uplink channel transmission segment length or the beam and the resource for random access. The embodiment of the present application is not particularly limited thereto.

For example, in the case that the association relationship between the uplink channel transmission segment length or the beam and the resource for random access is indicated to the terminal device by the network device through the indication message, the network device may send the indication message to the terminal device through a broadcast or unicast mode, which is not limited in particular in the embodiment of the present application. In some embodiments, the network device may send the indication information to the terminal device in higher layer signaling (e.g., system information, radio resource control (radio resource control, RRC) signaling) or downlink control messages (downlink control information, DCI). The embodiment of the present application is not particularly limited thereto. Correspondingly, the terminal equipment receives the indication information sent by the network equipment, so as to obtain the association relation between the uplink channel transmission segment length and the resource for random access.

In step 302, the terminal device transmits a random access request message based on the resource for random access. Correspondingly, the network device receives a random access request message based on the resources for random access.

Specifically, the terminal device may send a random access request message to the network device based on resources associated with the uplink channel transmission segment length or beam.

In this embodiment, for 4-step random access, the random access request message may be referred to as Msg1.

Step 303, the network device receives the random access request message and sends a random access response message to the terminal device. For 4-step random access, the random access response message may be referred to as Msg2.

In specific implementation, the terminal device may segment the random access request message according to the uplink channel transmission segment length, and may use the resource associated with the uplink channel transmission segment length to send the segments of the multiple random access request messages obtained after the segmentation to the network device. The terminal device may also perform uplink time-frequency synchronization adjustment, that is, TA adjustment, with the network device during the period when the terminal device sends the random access request message to the network device. For example, after the terminal device sends out a segment of a random access request message, uplink time-frequency synchronization adjustment can be performed with the network device, so that the terminal device can maintain uplink synchronization in a scene of rapid TA change, which is beneficial to improving uplink communication performance. Correspondingly, the network device may receive the random access request message sent by the terminal device on the resource, and may determine the uplink channel transmission segment length associated with the resource according to the resource, so that the network device may receive the random access request message sent by the terminal device according to the uplink channel transmission segment length.

In the embodiment of the present invention, since there is an association relationship between the resources and the uplink channel transmission segment or the beam, the terminal device can determine the resources for sending the random access request message according to the ephemeris information and/or the GNSS positioning information, so that the uplink synchronization can be maintained in a scene where the TA changes faster, and the uplink communication performance can be improved.

The following describes the communication method according to the embodiment of the present application in detail in connection with different situations where the uplink channel transmission segment length or beam is associated with the resource used for random access.

Embodiment one: the PRACH transmission segment length and PUSCH transmission segment length are associated with a carrier.

Fig. 4 is a schematic flow chart of a communication method according to an embodiment of the present application, which specifically includes the following steps:

401. the terminal equipment determines a proper uplink channel transmission section length (comprising PRACH transmission section length and PUSCH transmission section length) according to the ephemeris information and/or the GNSS positioning information.

For example, the terminal device determines the rate of change and the rate of doppler change of the current TA according to ephemeris information and/or GNSS positioning information. Then, the terminal equipment determines a proper uplink channel transmission segment length according to the change rate of the current TA and the Doppler change rate.

402. The terminal device selects a carrier associated with the uplink channel transmission segment length determined in step 401 above, and initiates random access to the network device. That is, the terminal device transmits a random access request message to the network device on a carrier associated with the uplink channel transmission segment length determined in step 401 described above. Correspondingly, the network device receives the random access request message based on the carrier associated with the uplink channel transmission segment length. For example, the network device receives the random access request message on a carrier associated with the uplink channel transmission segment length according to the PRACH transmission segment length.

Specifically, the terminal device sends a random access request message to the network device according to the PRACH transmission segment length determined in step 401 on the carrier associated with the uplink channel transmission segment length determined in step 401.

Further, in some embodiments, the terminal device may send uplink data to the network device based on the PUSCH transmission segment length determined in step 401. For example, the uplink data may be a radio resource control connection request message (i.e. Msg 3) or uplink data (e.g. Msg 5) sent after the terminal device completes the random access procedure (i.e. enters a connected state). Correspondingly, the network equipment receives uplink data from the terminal equipment according to the length of the PUSCH transmission section.

In other embodiments of the present application, the network device sends indication information to the terminal device, where the indication information is used to indicate the PRACH transmission segment length and the association relationship between the PUSCH transmission segment length and the carrier. Or, the indication information is used to indicate PRACH transmission segment length and PUSCH transmission segment length associated with the carrier. Correspondingly, the terminal equipment receives the indication information sent by the network equipment, so as to obtain the association relationship between the length of the uplink channel transmission segment and the carrier.

It should be noted that the indication information may be used to indicate one or more groups of PRACH transmission segment lengths and an association relationship between PUSCH transmission segment lengths and carriers. Or, the indication information is used to indicate a PRACH transmission segment length and a PUSCH transmission segment length associated with at least one carrier. It should be further noted that different uplink channel transmission segment lengths may be associated with the same carrier, that is, one carrier may be associated with multiple uplink channel transmission segment lengths. However, in the embodiment of the present application, one carrier is associated with one PRACH transmission segment length and one PUSCH transmission segment length.

For example, in the embodiment of the present application, the association relationship between the PRACH transmission segment length and the PUSCH transmission segment length and the carrier may be implemented through an association relationship table. For example, table of association between PRACH transmission segment length and PUSCH transmission segment length and carrier is shown in table 1.

TABLE 1

Carrier wave	PRACH transmission segment length	PUSCH transmission segment Length
			Carrier 1	N1	M1
Carrier 2	N2	M2
			Carrier 3	N3	M3
…	…	…

For example, as shown in table 1, carrier 1 is associated with N1 and M1, where N1 is the PRACH transmission segment length and M1 is the PUSCH transmission segment length. In some embodiments, in a specific implementation, the carrier 1 may be associated with N1 and M1 by establishing a mapping relationship or association relationship between the index or identifier of the carrier 1 and N1 and M1. It should be understood that the foregoing description is merely an introduction of a specific implementation manner of the association between a carrier and the length of the uplink channel transmission segment, and of course, in the embodiment of the present application, the association relationship between the carrier and the length of the uplink channel transmission segment may be established in other manners, which is not limited thereto. For example, the carrier is associated with a PRACH transmission segment length and a PUSCH transmission segment length, respectively. Taking the example of carrier 1 being associated with N1 and M1 in table 1, carrier 1 is associated with N1, and carrier 1 is associated with M1.

Embodiment two: the PRACH transmission segment length and PUSCH transmission segment length are associated with a carrier group. Wherein a carrier group may comprise one or more carriers. The number of carriers included in different carrier groups may be the same or different, and is not limited thereto.

Fig. 5 is a schematic flow chart of a communication method according to another embodiment of the present application, which specifically includes the following steps:

501. the terminal equipment determines a proper uplink channel transmission section length (comprising PRACH transmission section length and PUSCH transmission section length) according to the ephemeris information and/or the GNSS positioning information.

The specific implementation of step 501 may be referred to the related description in step 401, which is not described herein.

502. The terminal device selects one carrier from the carrier group associated with the uplink channel transmission segment length determined in the above step 501, and initiates random access to the network device. That is, the terminal device transmits a random access request message to the network device on the carrier selected in step 502 described above.

Correspondingly, the network device receives the random access request message based on the carrier group associated with the uplink channel transmission segment length. For example, the network device receives the random access request message on a carrier associated with the uplink channel transmission segment length according to the PRACH transmission segment length.

For example, the terminal device may randomly select one carrier from the carrier group associated with the uplink channel transmission segment length determined in step 501. Alternatively, the terminal device may select one carrier from the carrier group associated with the uplink channel transmission segment length determined in step 501, based on a certain carrier selection policy, where the carrier selection policy may be indicated to the terminal device by the network device, may be predefined by a protocol, or may be determined by the terminal device in combination with its own requirement, which is not limited.

Specifically, the terminal device may send a random access request message to the network device on the carrier selected in step 502 according to the PRACH transmission segment length.

Further, in some embodiments, the terminal device may send uplink data to the network device based on the PUSCH transmission segment length determined in step 501. Correspondingly, the network device receives uplink data from the network device based on the PUSCH transmission segment length.

For example, the uplink data may be a radio resource control connection request message (i.e. Msg 3) or uplink data (e.g. Msg 5) sent after the terminal device completes the random access procedure (i.e. enters a connected state).

In other embodiments of the present application, the network device sends indication information to the terminal device, where the indication information is used to indicate the PRACH transmission segment length and the association relationship between the PUSCH transmission segment length and the carrier group. Or, the indication information is used to indicate the PRACH transmission segment length and PUSCH transmission segment length associated with the carrier group.

It should be noted that the indication information may be used to indicate one or more groups of PRACH transmission segment lengths and an association relationship between a PUSCH transmission segment length and a carrier group. Or, the indication information is used to indicate a PRACH transmission segment length and a PUSCH transmission segment length associated with at least one carrier group.

For example, in the embodiment of the present application, the association relationship between the PRACH transmission segment length and the PUSCH transmission segment length and the carrier group may be implemented through an association relationship table. For example, table 2 shows the association relationship between PRACH transmission segment length and PUSCH transmission segment length and carrier group.

TABLE 2

Carrier group	PRACH transmission segment length	PUSCH transmission segment Length
			Carrier group 1	N1	M1
Carrier group 2	N2	M2
			Carrier group 3	N3	M3
…	…	…

For example, as shown in table 2, carrier group 1 is associated with N1 and M1, where N1 is the PRACH transmission segment length and M1 is the PUSCH transmission segment length. In some embodiments, in a specific implementation, the association of the carrier group 1 with N1 and M1 may be achieved by establishing a mapping relationship or association relationship between the index or the identifier of the carrier group 1 and N1 and M1. It should be understood that the foregoing description is merely an introduction of a specific implementation manner of the association between a carrier group and the length of the uplink channel transmission segment, and of course, in the embodiment of the present application, the association relationship between the carrier and the length of the uplink channel transmission segment may be established in other manners, which is not limited thereto. For example, the carrier groups are associated with PRACH transmission segment length and PUSCH transmission segment length, respectively. Taking the association of carrier set 1 with N1 and M1 in table 2 as an example, carrier set 1 is associated with N1 and carrier set 1 is associated with M1.

Embodiment III: the PRACH transmission segment length is associated with a carrier and the PUSCH transmission segment length.

Fig. 6 is a schematic flow chart of a communication method according to another embodiment of the present application, which specifically includes the following steps:

601. the terminal equipment determines a proper PRACH transmission segment length according to the ephemeris information and/or the GNSS positioning information.

The specific implementation manner of step 601 may refer to the description of determining a suitable uplink channel transmission segment length in step 401, which is not described herein.

602. The terminal device selects a carrier associated with the PRACH transmission segment length determined in step 601 and initiates random access to the network device. That is, the terminal device transmits a random access request message to the network device on the carrier selected in step 602 described above. Further, the terminal device sends a random access request message to the network device on the carrier selected in step 602 according to the PRACH transmission segment length.

Correspondingly, the network device receives the random access request message based on a carrier associated with the PRACH transmission segment length. For example, the network device receives the random access request message on a carrier associated with the uplink channel transmission segment length according to the PRACH transmission segment length.

In some embodiments, the association between the PRACH transmission segment length and the carrier may be predefined, or may be indicated to the terminal device by the network device. For example, the network device sends indication information to the terminal device, where the indication information is used to indicate an association relationship between the PRACH transmission segment length and the carrier, or the indication information is used to indicate the PRACH transmission segment length associated with the carrier. It should be noted that the indication information may be used to indicate an association relationship between one or more groups of PRACH transmission segment lengths and carriers. Alternatively, the indication information is used to indicate a PRACH transmission segment length associated with at least one carrier. For the association between the PRACH transmission segment length and the carrier, reference may be made to a specific implementation manner of associating the carrier with the PRACH transmission segment length and the PUSCH transmission segment length in the embodiment, which is not described herein again.

Further, in some embodiments, the terminal device transmits the uplink data according to a PUSCH transmission segment length associated with the PRACH transmission segment length determined in step 601. Correspondingly, the network device receives uplink data based on the PUSCH transmission segment length associated with the PRACH transmission segment length determined in step 601.

It should be noted that, the uplink data may be Msg3, or may be uplink data (e.g., msg 5) sent by the terminal device after the terminal device completes the random access procedure (i.e., enters the connected state), where the terminal device completes the random access procedure (i.e., enters the connected state).

Specifically, the association relationship between the PRACH transmission segment length and the PUSCH transmission segment length may be preconfigured or predefined. For example, the network device may indicate to the terminal device, through the system information, an association of one or more groups of PRACH transmission segment lengths with PUSCH transmission segment lengths, or PUSCH transmission segment lengths associated with one or more PRACH transmission segment lengths.

For example, the association relationship between the PRACH transmission segment length and the PUSCH transmission segment length may be implemented through an association relationship table. For example, the association relationship between the PRACH transmission segment length and the PUSCH transmission segment length is shown in table 3.

TABLE 3 Table 3

Taking the first set of data in table 3 as an example, the PRACH transmission segment length of 1 uplink data retransmission unit is associated with the PUSCH transmission segment length of 2 uplink data retransmission units. And under the condition that the terminal equipment determines that the PRACH transmission section length is 1 uplink data repeated transmission unit, the terminal equipment transmits uplink data based on 2 uplink data repeated transmission units. Namely, the terminal device transmits PUSCH transmission segments of 2 uplink data retransmission units under the condition that 1 PRACH transmission segment of the uplink data retransmission unit is transmitted at a time.

Table 3 is described by taking one PRACH transmission segment length and one PUSCH transmission segment length as an example. In the embodiment of the present application, different PRACH transmission segment lengths may be associated with the same PUSCH transmission segment length.

Embodiment four: the PRACH transmission segment length is associated with a carrier group and the PUSCH transmission segment length.

Fig. 7 is a schematic flow chart of a communication method according to another embodiment of the present application, which specifically includes the following steps:

701. the terminal equipment determines a proper PRACH transmission segment length according to the ephemeris information and/or the GNSS positioning information.

702. The terminal device selects one carrier from the carrier group associated with the PRACH transmission segment length determined in step 701, and initiates random access to the network device. That is, the terminal device transmits a random access request message to the network device on the carrier selected in step 702 described above.

Correspondingly, the network device receives the random access request message based on the carrier group associated with the PRACH transmission segment length. For example, the network device receives the random access request message on a carrier associated with the uplink channel transmission segment length according to the PRACH transmission segment length.

The manner in which the terminal device selects one carrier from the carrier set may be referred to in the related description of the second embodiment, which is not described herein.

Compared with the second embodiment, the second embodiment adds that the terminal device needs to select one carrier from the carrier group to initiate random access, and other related descriptions in the third embodiment can be referred to for determining the length of the PRACH transmission segment, the association relationship between the length of the PRACH transmission segment and the PUSCH transmission segment, and the like, which are not repeated herein. In addition, for the specific implementation of the association relationship between the PRACH transmission segment length and the carrier group, reference may be made to the implementation of the association relationship between the PRACH transmission segment length and the carrier, which is not described herein again.

Fifth embodiment: RO and/or Preamble (Preamble) are associated with PUSCH transmission segment length.

Fig. 8 is a flow chart of a communication method according to another embodiment of the present application, which specifically includes the following steps:

801. and the terminal equipment determines a proper PUSCH transmission segment length according to the ephemeris information and/or the GNSS positioning information.

For example, the terminal device determines the change rate of the current TA and the doppler change rate according to ephemeris information and/or GNSS positioning information; then, the terminal equipment determines a proper PUSCH transmission segment length according to the change rate of the current TA and the Doppler change rate.

802. The terminal device initiates random access to the network device according to the RO associated with the PUSCH transmission segment length determined in step 801 and/or the Preamble associated with the PUSCH transmission segment length determined in step 801. That is, the terminal device transmits a random access request message to the network device according to RO associated with the PUSCH transmission segment length determined in step 801 and/or Preamble associated with the PUSCH transmission segment length determined in step 801.

Correspondingly, the network device receives the random access request message based on the RO associated with the PUSCH transmission segment length and/or the preamble associated with the PUSCH transmission segment length.

Further, in some embodiments, the terminal device sends the uplink data according to the PUSCH transmission segment length determined in step 801 above. Correspondingly, the network equipment receives uplink data based on the length of the PUSCH transmission section.

For example, the terminal device transmits Msg3 according to the PUSCH transmission segment length determined in step 801 above. For another example, after the terminal device completes random access and enters a connection state, uplink data (such as Msg 5) is sent according to the PUSCH transmission segment length determined in step 801.

For example, the network device determines the PUSCH transmission segment length according to the RO and/or the preamble corresponding to the received random access request message, and then receives uplink data according to the PUSCH transmission segment length, so as to implement uplink communication.

Furthermore, in some embodiments of the present application, the association relationship between RO and/or Preamble (Preamble) and PUSCH transmission segment length may be predefined, or may be indicated by the network device to the terminal device. For example, the network device transmits, to the terminal device, indication information for indicating an association relationship between one or more sets of ROs and/or preambles and PUSCH transmission segment lengths, or for indicating PUSCH transmission segment lengths associated with at least one RO and/or Preamble. It should be noted that one RO or preamble may be associated with one or more PUSCH transmission segment lengths, but one PUSCH transmission segment length is associated with one RO and/or preamble.

Example six: the beam is associated with a carrier.

Fig. 9 is a schematic flow chart of a communication method according to another embodiment of the present application, which specifically includes the following steps:

901. and the terminal equipment determines the current beam according to the ephemeris information and/or the GNSS positioning information.

For example, the terminal device determines the current location information according to the ephemeris information and/or GNSS positioning information, and determines the downlink beam covering the terminal device according to the location information, where it can be understood that the downlink beam covering the terminal device is the beam where the terminal device is currently located.

902. The terminal device selects a carrier associated with the beam determined in step 901 and initiates random access to the network device. That is, the terminal device transmits Msg1 to the network device on the carrier associated with the beam determined in step 901.

Further, in some embodiments, the network device receives the Msg1, sends the Msg2 to the terminal device, where the Msg2 is used to indicate the PUSCH transmission segment length, so that the terminal device receives the Msg2, and may acquire the PUSCH transmission segment length based on the Msg2, so that the terminal device sends the Msg3 based on the PUSCH transmission segment length; or after the terminal equipment completes random access and enters a connection state, uplink data (such as Msg 5) is sent.

In other embodiments of the present application, the association relationship between the beam and the carrier may be indicated to the terminal device by the network device, or may be predefined, which is not limited. For example, the network device transmits, to the terminal device, indication information for indicating an association relationship between at least one beam and a carrier, or indication information for indicating a beam associated with at least one carrier, a carrier associated with at least one beam, or the like. For example, the indication information may be carried by the network device in the system information and sent to the terminal device. It will be appreciated that the network device may also carry the above indication information by other information or messages and send it to the terminal device.

It should be noted that, in the above embodiments, the terminal device determines the uplink channel transmission segment length based on at least one of the ephemeris information and the GNSS positioning information, but in the embodiments of the present application, the terminal device may determine an appropriate uplink channel transmission segment length by combining other information besides the reference ephemeris information or the GNSS positioning information.

The above embodiments can be used alone or in combination with each other to achieve different technical effects.

In the embodiments provided in the present application, the communication method provided in the embodiments of the present application is described from the point of view that the network device and the terminal device are the execution subjects. In order to implement the functions in the communication method provided in the embodiments of the present application, the terminal device and the network device may include hardware structures and/or software modules, and implement the functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Some of the functions described above are performed in a hardware configuration, a software module, or a combination of hardware and software modules, depending on the specific application of the solution and design constraints.

Fig. 10 is a schematic structural diagram of a communication device 1000 according to an embodiment of the present application, which may include: a determining module 1010 and a transmitting module 1020; wherein,,

A determining module 1010, configured to determine, by a terminal device, first information according to ephemeris information and/or GNSS positioning information, where the first information is used to indicate an uplink channel transmission segment length or a beam, and the uplink channel transmission segment length or the beam is associated with a resource for random access;

a sending module 1020, configured to send a random access request message based on the resource by the terminal device.

In one possible implementation, the uplink channel transmission segment length is associated with a carrier, or the uplink channel transmission segment length is associated with a carrier group, which includes carriers.

In one possible implementation, the first information is used to indicate a physical random access channel PRACH transmission segment length and a physical uplink shared channel PUSCH transmission segment length.

In a possible implementation manner, the sending module 1020 is further configured to send uplink data according to the PUSCH transmission segment length by the terminal device.

In one possible implementation, the first information is used to indicate a PRACH transmission segment length, where the PRACH transmission segment length is associated with a PUSCH transmission segment length.

In a possible implementation manner, the sending module 1020 is further configured to send uplink data according to a PUSCH transmission segment length associated with a PRACH transmission segment length by a terminal device.

In one possible implementation, the uplink channel transport segment length is associated with RO and/or a preamble.

In one possible implementation, the first information is used to indicate PUSCH transmission segment length.

In one possible implementation, the beam is associated with a carrier.

In one possible implementation manner, the communication apparatus 1000 further includes:

a receiving module 1030, configured to receive a random access response message by the terminal device, where the random access response message is used to indicate a PUSCH transmission segment length.

In a possible implementation manner, the receiving module 1030 is further configured to receive indication information, where the indication information is used to indicate an uplink channel transmission segment length or a beam associated with a resource used for random access.

In one possible implementation, the communication device 30 may be a chip or a terminal device.

Fig. 11 is a schematic structural diagram of a communication device 1100 according to an embodiment of the present application, which may include: a receiving module 1110 and a transmitting module 1120; wherein,,

a receiving module 1110, configured to receive, by a network device, a random access request message based on a resource for random access, where the resource is associated with an uplink channel transmission segment length or a beam;

A sending module 1120, configured to send a random access response message to the terminal device by the network device.

In one possible implementation, the carrier is associated with an uplink channel transmission segment length, or the carrier group is associated with an uplink channel transmission segment length, the carrier group comprising carriers.

In one possible implementation, the uplink channel transmission segment length includes a physical random access channel PRACH transmission segment length and a physical uplink shared channel PUSCH transmission segment length; or,

In one possible implementation, the receiving module 1110 is further configured to receive, by a network device, a random access request message on a resource according to a PRACH transmission segment length associated with the resource.

In one possible implementation, the resources are random access occasions RO and/or preambles, the resources being associated with an uplink channel transmission segment length.

In a possible implementation manner, the receiving module 1110 is further configured to receive, by a network device, a random access request message according to an RO and/or a preamble associated with an uplink channel transmission segment length.

In one possible implementation, the uplink channel transport segment length is the PUSCH transport segment length.

In one possible implementation, the receiving module 1110 is further configured to receive, by a network device, a random access request message based on a beam associated with a resource.

In one possible implementation, a random access response message is used to indicate PUSCH transmission segment length.

In a possible implementation manner, the receiving module 1110 is further configured to receive uplink data according to a PUSCH transmission segment length by a network device.

In one possible implementation, the sending module 1120 is further configured to send indication information to the network device, where the indication information is used to indicate an uplink channel transmission segment length or a beam associated with a resource used for random access.

In one possible implementation, the communication device 40 may be a chip or a network device.

Fig. 12 is a schematic structural diagram of a communication device 1200 according to an embodiment of the present application, where the communication device 1200 may include: at least one processor; and at least one memory communicatively coupled to the processor. The communication apparatus 1200 may be a network device or a terminal device. The memory stores program instructions executable by the processor, and if the communication apparatus 1200 is a network device, the processor calls the program instructions to execute the actions executed by the network device in the communication method provided in the embodiment of the present application, and if the communication apparatus 1200 is a terminal device, the processor calls the program instructions to execute the actions executed by the terminal device in the communication method provided in the embodiment of the present application.

As shown in fig. 12, the communications apparatus 1200 may be embodied in the form of a general purpose computing device. The components of the communications apparatus 1200 can include, but are not limited to: one or more processors 1210, a memory 1220, a communication bus 1240 and a communication interface 1230 that connect the different system components (including the memory 1220 and the processor 1210).

The communication bus 1240 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a graphics accelerator port, a processor, or a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include industry standard architecture (Industry Standard Architecture, ISA) bus, micro channel architecture (Micro Channel Architecture, MAC) bus, enhanced ISA bus, video electronics standards association (Video Electronics Standards Association, VESA) local bus, and peripheral component interconnect (Peripheral Component Interconnection, PCI) bus.

Communication device 1200 typically includes a variety of computer system readable media. Such media can be any available media that is accessible by the communications device 1200 and includes both volatile and nonvolatile media, removable and non-removable media.

Memory 1220 may include computer system readable media in the form of volatile memory, such as random access memory (Random Access Memory, RAM) and/or cache memory. The communications device 1200 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. Although not shown in fig. 12, a disk drive for reading from and writing to a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading from or writing to a removable non-volatile optical disk such as, for example, compact disk read only memory (Compact Disc Read Only Memory, CD-ROM), digital versatile disk read only memory (Digital Video Disc Read Only Memory, DVD-ROM), or other optical media, may be provided. In such cases, each drive may be coupled to the communication bus 1240 via one or more data medium interfaces. Memory 1220 may include at least one program product having a set (e.g., at least one) of program modules configured to carry out the functions of the embodiments of the present application.

A program/utility having a set (at least one) of program modules may be stored in the memory 1220, such program modules include, but are not limited to, an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment. Program modules generally perform the functions and/or methods in the embodiments described herein.

The communications apparatus 1200 can also communicate with one or more external devices (e.g., keyboard, pointing device, display, etc.), one or more devices that enable a user to interact with the communications apparatus 1200, and/or any device (e.g., network card, modem, etc.) that enables the communications apparatus 1200 to communicate with one or more other computing devices. Such communication may occur through communication interface 1230. Also, the communication apparatus 1200 may communicate with one or more networks (e.g., local area network (Local Area Network, LAN), wide area network (Wide Area Network, WAN) and/or public network, such as the internet) via a network adapter (not shown in fig. 12) that may communicate with other modules of the electronic device via the communication bus 1240. It should be appreciated that although not shown in fig. 5, other hardware and/or software modules may be used in connection with the communication device 1200, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, disk array (Redundant Arrays of Independent Drives, RAID) systems, tape drives, data backup storage systems, and the like.

From the foregoing description of the embodiments, it will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of functional modules is illustrated, and in practical application, the above-described functional allocation may be implemented by different functional modules according to needs, i.e. the internal structure of the apparatus is divided into different functional modules to implement all or part of the functions described above. The specific working processes of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which are not described herein.

The functional units in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the embodiments of the present application may be essentially or a part contributing to the prior art or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: flash memory, removable hard disk, read-only memory, random access memory, magnetic or optical disk, and the like.

The foregoing is merely a specific embodiment of the present application, but the protection scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of communication, the method comprising:

the terminal equipment determines first information according to ephemeris information and/or GNSS positioning information, wherein the first information is used for indicating the length of an uplink channel transmission section or a wave beam, and the length of the uplink channel transmission section or the wave beam is associated with resources for random access;

and the terminal equipment sends a random access request message based on the resource.

2. The method of claim 1, wherein the resource is a carrier, the uplink channel transmission segment length is associated with the resource, comprising:

the uplink channel transmission segment length is associated with the carrier, or the uplink channel transmission segment length is associated with a carrier group, the carrier group including the carrier.

3. The method according to claim 1 or 2, wherein the first information is used for indicating an uplink channel transmission segment length, and comprises:

The first information is used for indicating the length of a physical random access channel PRACH transmission section and the length of a physical uplink shared channel PUSCH transmission section.

4. A method according to claim 3, characterized in that the method further comprises:

5. The method according to claim 1 or 2, wherein the first information is used for indicating an uplink channel transmission segment length, and comprises:

the first information is used for indicating a PRACH transmission segment length, wherein the PRACH transmission segment length is associated with a PUSCH transmission segment length.

6. The method of claim 5, wherein the method further comprises:

and the terminal equipment sends uplink data according to the PUSCH transmission section length correlated with the PRACH transmission section length.

7. The method according to claim 1, wherein the resource is a random access occasion RO and/or a preamble, and the uplink channel transmission segment length is associated with the resource, comprising:

the uplink channel transmission segment length is associated with the RO and/or the preamble.

8. The method of claim 7, wherein the first information is used to indicate an uplink channel transmission segment length, comprising:

The first information is used for indicating the length of a PUSCH transmission segment.

9. The method of claim 1, wherein the first information is used to indicate a beam, the beam being associated with the resource, comprising:

the beam is associated with a carrier.

10. The method according to claim 9, wherein the method further comprises:

the terminal equipment receives a random access response message, wherein the random access response message is used for indicating the length of a PUSCH transmission section.

11. The method according to any one of claims 1-10, further comprising:

12. A method of communication, the method comprising:

13. The method of claim 12, wherein the resource is a carrier, the resource being associated with an uplink channel transmission segment length, comprising:

The carrier is associated with an uplink channel transmission segment length, or the carrier group is associated with an uplink channel transmission segment length, and the carrier group includes the carrier.

14. The method according to claim 12, wherein the uplink channel transmission segment length comprises a physical random access channel, PRACH, transmission segment length and a physical uplink shared channel, PUSCH, transmission segment length; or,

the length of the uplink channel transmission section is the length of the PRACH transmission section, and the length of the PRACH transmission section is related to the length of the PUSCH transmission section.

15. The method of claim 14, wherein the network device receiving the random access request message based on the resources for random access comprises:

the network device receives the random access request message on the resource according to the PRACH transmission segment length associated with the resource.

16. The method according to claim 12, characterized in that the resources are random access occasions, ROs, and/or preambles, the resources being associated with an uplink channel transmission segment length.

17. The method of claim 16, wherein the network device receiving the random access request message based on the resources for random access comprises:

The network device receives a random access request message according to the RO and/or the preamble associated with the uplink channel transmission segment length.

18. The method according to claim 16 or 17, wherein the uplink channel transport segment length is a PUSCH transport segment length.

19. The method of claim 12, wherein the resource is a carrier, the resource is associated with a beam, the network device receives a random access request message based on the resource for random access, comprising:

the network device receives a random access request message based on a beam associated with the resource.

20. The method of claim 19, wherein the random access response message is used to indicate a PUSCH transmission segment length.

21. The method of claim 14, 18 or 20, further comprising:

and the network equipment receives uplink data according to the length of the PUSCH transmission section.

22. The method according to claim 12, wherein the method further comprises:

the network device sends indication information, where the indication information is used to indicate an uplink channel transmission segment length or a beam associated with the resource for random access.

23. A communication device, comprising: a processor and a memory for storing a computer program; the processor is configured to run the computer program to implement the communication method according to any of claims 1-11.

24. The communication apparatus according to claim 23, wherein the communication apparatus is a chip or the communication apparatus is a terminal device.

25. A communication device, comprising: a processor and a memory for storing a computer program; the processor is configured to execute the computer program to implement the communication method according to any of claims 12-22.

26. The communication apparatus according to claim 25, wherein the communication apparatus is a chip or the communication apparatus is a network device.

27. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program which, when run on a computer, implements the method according to any one of claims 1-11 or the method according to any one of claims 12-22.