Communication method and device and computer readable storage medium

Abstract

Provided are a communication method and apparatus, and a computer readable storage medium, the communication method comprising: receiving first information, the first information indicating transmission resources used for repeatedly transmitting a physical uplink shared channel (PUSCH) during at least two hop beam residence periods, the first information comprising at least one of the following items: an initial transmission position, an initial transmission position, and an initial transmission position; the number of times of repeated transmission and time-frequency resources. According to the method and the device, the PUSCH can be ensured to smoothly complete multiple times of repeated transmission, and resource waste is avoided.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and in particular, to a communication method, a device, and a computer-readable storage medium. Background Art

[0002] In the current 3rd Generation Partnership Project (3GPP) standard, satellites serve the ground coverage area in the form of multiple beams, that is, during the satellite overflight period, a fixed area on the ground can always be served. However, due to the constraints of on-board resources and the uneven distribution of the population's geographical location, the demand for on-board resources in different regions shows unevenness in time domain and spatial domain, and the demand for network time, space, and frequency domain resources shows high dynamic characteristics. The above characteristics lead to the phenomenon of "uneven busy and idle" frequently occurring in each beam, which cannot meet the on-demand coverage and efficient transmission requirements of diverse tasks, resulting in waste of communication resources.

[0003] To solve the above problems, the hopping beam technology has gradually become a research hotspot. The hopping beam technology is applied to the service link and serves the satellite coverage area through a set of predefined beam patterns. Through time division multiplexing, a small number of beams are used to serve the ground coverage area. With the introduction of hopping beams, problems such as resource scheduling of terminal devices need to be solved urgently. Summary of the Invention

[0004] This application can ensure the successful completion of multiple repeated transmissions of the PUSCH, avoid resource waste, and improve resource utilization.

[0005] To achieve the above object, this application provides the following technical solutions:

[0006] In a first aspect, a communication method is provided. The communication method includes: receiving first information, where the first information indicates transmission resources for repeating the transmission of a physical uplink shared channel (PUSCH) during the residence of at least two hopping beams. The first information includes at least one of the following: a starting transmission position, the number of repeated transmissions, and time-frequency resources. The technical solution of this application can enable the terminal device to complete multiple repeated transmissions of the PUSCH during the residence of at least two hopping beams by indicating the transmission resources during the residence of at least two hopping beams, and avoid resource waste caused by the transmission resources of the PUSCH falling during the non-residence period of the hopping beam.

[0007] Optionally, the starting transmission position includes a first offset value of the starting position of the first PUSCH transmission during the residence of the first hopping beam from the time slot where the signaling for scheduling the PUSCH transmission is located, and a second offset value of the starting transmission position of the PUSCH during the residence of other hopping beams from the starting position of the residence of the hopping beam.

[0008] Optionally, the first information includes time-frequency resources, and the time-frequency resources include time-frequency resources during each hopping beam dwelling period.

[0009] Optionally, the first information includes the number of repeated transmissions, and the number of repeated transmissions of the PUSCH during different hopping beam dwelling periods may be the same or different.

[0010] Optionally, the first information indicates transmission resources for repeating the transmission of a group of PUSCHs during each of the at least two hopping beam dwelling periods.

[0011] Optionally, the communication method further includes: receiving second information, where the second information indicates the timing duration of dwelling in the active partial bandwidth BWP; timing during the hopping beam dwelling period and stopping timing during the non-hopping beam dwelling period; or timing during the non-hopping beam dwelling period and during the hopping beam dwelling period. In the technical solution of this application, the terminal device stops counting during the non-hopping beam dwelling period, which can avoid invalid timing when there is no uplink and downlink data transmission during the non-hopping beam dwelling period, improve the accuracy of timing, and thus ensure the effectiveness of BWP switching. Alternatively, by setting the timing duration to a relatively large value, the terminal device times both during the non-hopping beam dwelling period and during the hopping beam dwelling period, thereby avoiding premature timeout of the timing during the non-hopping beam dwelling period, and thus ensuring the effectiveness of BWP switching.

[0012] Optionally, the timing during the hopping beam dwelling period and the stopping of timing during the non-hopping beam dwelling period include: stopping timing during the non-hopping beam dwelling period and continuing timing during the next hopping beam dwelling period.

[0013] Optionally, the timing during the hopping beam dwelling period and the stopping of timing during the non-hopping beam dwelling period include: stopping timing during the non-hopping beam dwelling period and restarting timing during the hopping beam dwelling period.

[0014] Optionally, the numerical values of the timing duration indicated by the second information include at least one of the following: 3200 milliseconds, 3840 milliseconds, 4480 milliseconds, 5120 milliseconds.

[0015] In a second aspect, this application also discloses a communication method. The communication method includes: sending first information, where the first information indicates transmission resources for repeating the transmission of a physical uplink shared channel (PUSCH) during at least two hopping beam dwelling periods, and the first information includes at least one of the following: starting transmission position, number of repeated transmissions, and time-frequency resources. Through the technical solution of this application, by indicating the transmission resources during at least two hopping beam dwelling periods through the first information, the terminal device can complete multiple repeated transmissions of the PUSCH during at least two hopping beam dwelling periods, and avoid resource waste caused by the transmission resources of the PUSCH falling during the non-hopping beam dwelling period.

[0016] Optionally, the starting transmission position includes a first offset value of the starting position of the first PUSCH transmission during the first-hop beam dwell from the time slot where the signaling for scheduling the PUSCH transmission is located, and a second offset value of the starting transmission position of the PUSCH during the dwell periods of other hop beams from the starting position of the dwell of the hop beam.

[0017] Optionally, the first information includes time-frequency resources, and the time-frequency resources include the time-frequency resources during each hop beam dwell period.

[0018] Optionally, the communication method further includes: sending second information, where the second information indicates the timing duration of dwelling in the active partial bandwidth BWP; timing during the hop beam dwell period and stopping timing during the non-dwell period of the hop beam; or, timing during the non-dwell period of the hop beam and during the dwell period of the hop beam.

[0019] In a third aspect, the present application also discloses a communication device, where the communication device includes: a communication module, configured to receive first information, where the first information indicates transmission resources for repeating the transmission of a physical uplink shared channel PUSCH during at least two hop beam dwell periods, and the first information includes at least one of the following: starting transmission position, number of repeat transmissions, and time-frequency resources.

[0020] In a fourth aspect, the present application also discloses a communication device, where the communication device includes: a communication module, configured to send first information, where the first information indicates transmission resources for repeating the transmission of a physical uplink shared channel PUSCH during at least two hop beam dwell periods, and the first information includes at least one of the following: starting transmission position, number of repeat transmissions, and time-frequency resources.

[0021] In a fifth aspect, a computer-readable storage medium is provided, on which a computer program is stored, and the computer program is run by a processor to execute any method provided in the first aspect or the second aspect.

[0022] In a sixth aspect, a communication device is provided, including a memory and a processor, where a computer program that can run on the processor is stored on the memory, and the processor runs the computer program to execute any method provided in the first aspect.

[0023] In a seventh aspect, a communication device is provided, including a memory and a processor, where a computer program that can run on the processor is stored on the memory, and the processor runs the computer program to execute any method provided in the second aspect.

[0024] In an eighth aspect, a computer program product is provided, on which a computer program is stored, and the computer program is run by a processor to execute any method provided in the first aspect or the second aspect.

[0025] In a ninth aspect, a communication system is provided, including the above-mentioned terminal device and the above-mentioned network device.

[0026] In a tenth aspect, an embodiment of the present application further provides a chip (or a data transmission device), on which a computer program is stored, and when the computer program is executed by the chip, the steps of the above method are implemented.

[0027] In an eleventh aspect, an embodiment of the present application further provides a system chip, which is applied to a terminal. The chip system includes at least one processor and an interface circuit. The interface circuit and the at least one processor are interconnected by a line. The at least one processor is configured to execute instructions to execute any one of the methods provided in the first aspect or the second aspect.

[0028] Compared with the prior art, the technical solution of the present application has the following beneficial effects:

[0029] In the technical solution of the present application, a first piece of information is received. The first piece of information indicates transmission resources for repeating the transmission of a Physical Uplink Shared Channel (PUSCH) during at least two hopping beam dwell periods. The first piece of information includes at least one of the following: a starting transmission position, a number of repeated transmissions, and time-frequency resources. By indicating the transmission resources during at least two hopping beam dwell periods through the first piece of information, the terminal device can complete multiple repeated transmissions of the PUSCH during at least two hopping beam dwell periods, avoiding resource waste caused by the transmission resources of the PUSCH falling during non-hopping beam dwell periods.

[0030] Further, the technical solution of the present application receives a second piece of information, which indicates the timing duration of dwelling in an active partial bandwidth (BWP); timing during the hopping beam dwell period and stopping timing during the non-hopping beam dwell period; or, timing during the non-hopping beam dwell period and during the hopping beam dwell period. In the technical solution of the present application, the terminal device stops timing during the non-hopping beam dwell period, which can avoid invalid timing when there is no uplink and downlink data transmission during the non-hopping beam dwell period, improving the accuracy of timing, and thus ensuring the effectiveness of BWP switching. Or, by setting the timing duration to a larger value, the terminal device times both during the non-hopping beam dwell period and during the hopping beam dwell period, thereby avoiding premature timeout of the timing during the non-hopping beam dwell period, and thus ensuring the effectiveness of BWP switching. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 is a schematic diagram of a multi-beam satellite communication system in the prior art;

[0032] Figure 2 is a schematic diagram of a beam dwell period in the prior art;

[0033] Figure 3 is a schematic diagram of a beam dwell period and a DRX period in the prior art;

[0034] Figure 4 It is an interaction flowchart of a communication method provided by an embodiment of the present application;

[0035] Figure 5 It is a schematic diagram of a specific application scenario provided by an embodiment of the present application;

[0036] Figure 6 It is a schematic diagram of another specific application scenario provided by an embodiment of the present application

[0037] Figure 7 It is an interaction flowchart of another communication method provided by an embodiment of the present application;

[0038] Figure 8 It is a schematic structural diagram of a communication device provided by an embodiment of the present application;

[0039] Figure 9 It is a schematic hardware structure diagram of a communication device provided by an embodiment of the present application. Specific embodiments

[0040] The communication systems applicable to the embodiments of the present application include, but are not limited to, Long Term Evolution (LTE) systems, 5th-generation (5G) systems, New Radio (NR) systems, and future evolved systems or multiple communication convergence systems. Among them, the 5G system can be a Non-StandAlone (NSA) 5G system or a StandAlone (SA) 5G system. The technical solutions of the present application are also applicable to different network architectures, including but not limited to relay network architectures, dual-connection architectures, Vehicle-to-Everything architectures, etc.

[0041] The present application mainly relates to the communication between terminal devices and network devices. Among them:

[0042] The network device in the embodiments of the present application may also be referred to as an access network device. For example, it may be a base station (BS) (also referred to as base station equipment). A network device is a device deployed in a radio access network (RAN) to provide wireless communication functions. For example, in the second-generation (2G) network, the device providing base station functions includes a base transceiver station (BTS); in the third-generation (3G) network, the device providing base station functions includes a Node B; in the fourth-generation (4G) network, the device providing base station functions includes an evolved Node B (eNB); in a wireless local area network (WLAN), the device providing base station functions is an access point (AP); in NR, the device providing base station functions is a next-generation base station node (gNB), and a next-generation evolved Node B (ng-eNB). Among them, communication between the gNB and the terminal device uses NR technology, and communication between the ng-eNB and the terminal device uses evolved universal terrestrial radio access (E-UTRA) technology. Both the gNB and the ng-eNB can be connected to the 5G core network. The network device may also be a satellite. The network device in the embodiments of the present application also includes devices that provide base station functions in future new communication systems, etc.

[0043] The terminal equipment in the embodiments of the present application may refer to various forms of access terminals, subscriber units, subscriber stations, mobile stations, mobile stations (Mobile Station, MS), remote stations, remote terminals, mobile devices, user terminals, wireless communication devices, user agents, or user devices. The terminal equipment may also be a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA), a handheld device with wireless communication function, a computing device, or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminal equipment in future 5G networks, or terminal equipment in future evolved Public Land Mobile Networks (PLMNs), etc. The embodiments of the present application do not limit this. The terminal equipment may also be referred to as User Equipment (UE), terminal, etc.

[0044] As described in the background art, with the introduction of beam hopping, problems such as resource scheduling of terminal equipment need to be solved urgently.

[0045] Specifically, in a multi-beam satellite communication system, most satellite resources are allocated to Non-Terrestrial access Network (NTN) cells in a fixed allocation manner. The allocable on-board resources include beams, frequencies, and powers. A multi-beam satellite communication system is as Figure 1 shown. For example, there are N regions on the ground (which can be denoted as wave positions). The satellite can generate N narrow beams or one wide beam to complete the coverage of the ground, where N is a positive integer greater than or equal to 1. Due to the non-uniform population distribution, the number of terminal equipment in some wave positions is large, while the number of terminal equipment in some wave positions is small or even none. Uniform coverage of all wave positions will cause waste of on-board resources.

[0046] In a beam hopping system, for N wave positions, the satellite only needs to generate P beams and complete the coverage of the ground through time division multiplexing, where P is a positive integer greater than or equal to 1. Figure 1 shows the case where N is 7 and P is 2, that is, seven wave positions and two beams. The actual number of wave positions is larger (possibly hundreds of wave positions). After introducing beam hopping, connected terminal equipment faces a series of problems such as repeated scheduling, Band Width Part (BWP) switching, and Discontinuous Reception (DRX).

[0047] During a dwell time of beam hopping (BH), the uplink repeated transmission (Physical Uplink Shared Channel, PUSCH) scheduled by the downlink control information (DCI) may not be able to complete L repetitions, where L is a positive integer greater than or equal to 1. Specifically, as Figure 2 shown, part of the resources required for the PUSCH to be repeated L times fall during the non-dwell period of beam hopping, and there is no uplink or downlink data transmission during the non-dwell period of beam hopping. Therefore, resource waste is caused.

[0048] In addition, in the scenario of timer-based Bandwidth Part (BWP) switching, after the terminal device enters the connected state, it will switch from the default BWP (default BWP) to the active BWP (active BWP), and the network will configure the timer bwp-InactivityTimer. If this timer times out, the terminal device has to fallback to the default BWP to achieve the purpose of energy saving; or when the network device releases the timer, the terminal side stops timing and remains in the current active BWP. After introducing beam hopping, there is no uplink or downlink data transmission during the non-dwell time, and the timer is also working, resulting in invalid counting.

[0049] In addition, after the terminal device enters the connected state, the network device will configure DRX, and the terminal device will enter the sleep state periodically. The network device will send a wake-up signal (such as DCI format 2-6) during the sleep period to indicate whether the terminal device should wake up. After receiving the wake-up signal, the terminal device determines whether to wake up or continue to sleep according to the indication. For C-DRX, DRX may be configured with reference to the beam hopping pattern. However, the terminal device can listen for DCI2_6 during the DRX OFF period to wake up in advance, but if the periods are completely aligned, the terminal will not receive any downlink information during the DRX-OFF period. As Figure 3 shown in a, the beam hopping pattern partially overlaps with the DRX period, and the terminal device can receive the wake-up signal during the DRX-off period. As Figure 3 shown in b, the beam hopping pattern completely overlaps with the DRX period, and the terminal device never receives the wake-up signal. How the terminal device determines whether to wake up is an urgent problem to be solved. The technical solution of this application can enable the terminal device to complete multiple repetitions of PUSCH during at least two beam hopping dwell periods by indicating the transmission resources during at least two beam hopping dwell periods, avoiding resource waste caused by the transmission resources of PUSCH falling during the non-dwell period of beam hopping.

[0050] Further, the technical solution of this application receives second information, where the second information indicates the timing duration of staying in the active partial bandwidth BWP; timing during the hopping beam staying period and stopping timing during the hopping beam non-staying period; or, timing during the hopping beam non-staying period and during the hopping beam staying period. In the technical solution of this application, the terminal device stops timing during the hopping beam non-staying period, which can avoid invalid timing when there is no uplink and downlink data transmission during the hopping beam non-staying period, improve the accuracy of timing, and thus ensure the effectiveness of BWP switching. Or, set the timing duration to a larger value, and the terminal device times both during the hopping beam non-staying period and during the hopping beam staying period, so as to avoid premature timeout of the timing during the hopping beam non-staying period, and thus ensure the effectiveness of BWP switching.

[0051] Further, if the discontinuous reception DRX sleep period is during the hopping beam non-staying period within the hopping beam cycle, then it wakes up during the next DRX wake-up period. Through the above settings, it can be ensured that the terminal device wakes up during the next DRX wake-up period when it does not receive a wake-up signal, realizing the wake-up of the terminal device.

[0052] To make the above objects, features, and advantages of this application more obvious and understandable, the following will specifically describe the embodiments of this application with reference to the accompanying drawings.

[0053] See Figure 4 , the method provided by this application specifically includes the following steps:

[0054] Step 401: The terminal device receives the first information sent by the network device. The first information indicates the transmission resources for repeating the transmission of the physical uplink shared channel PUSCH during at least two hopping beam staying periods.

[0055] Specifically, the first information includes at least one of the following: starting transmission position, number of repeated transmissions, and time-frequency resources.

[0056] Step 402: The terminal device sends the PUSCH to the network device.

[0057] Specifically, the terminal device repeats the transmission of the PUSCH during at least two hopping beam staying periods according to the transmission resources indicated by the first information.

[0058] It should be noted that the sequence numbers of the steps in this embodiment do not represent the limitation of the execution sequence of each step.

[0059] It can be understood that in specific implementations, the communication method can be implemented in the form of a software program, and this software program runs in a processor integrated inside a chip or a chip module. This method can also be implemented in the form of software combined with hardware, and this application does not make any restrictions.

[0060] In this embodiment, by using the first information to indicate the transmission resources during the dwell periods of at least two hopping beams, the terminal device can complete multiple repeated transmissions of PUSCH during the dwell periods of at least two hopping beams, avoid wasting resources caused by the transmission resources of PUSCH falling during the non-dwell periods of the hopping beams, and improve resource utilization.

[0061] In a non-limiting embodiment, the starting transmission position includes a first offset value of the starting position of the first PUSCH transmission during the first hopping beam dwell period from the time slot where the signaling for scheduling the PUSCH transmission is located, and a second offset value of the starting transmission position of PUSCH during other hopping beam dwell periods from the starting position of the hopping beam dwell.

[0062] Taking the network device configuring the transmission resources during the dwell periods of two hopping beams as an example, the network device configures the starting transmission position, the number of repeated transmissions, and the time-frequency resources during the dwell periods of the two hopping beams through DCI. For example, the network device configures two parameters (in units of time slots), k2 and the first offset value k2', where k2 represents the offset value of the starting position of the first PUSCH transmission from the time slot n where the DCI for scheduling the PUSCH transmission is located. The first offset value k2' is a newly added value, representing the offset value of the transmission position of PUSCH during the next hopping beam dwell period from the hopping beam boundary.

[0063] For details, please refer to Figure 5 , at time T1 during the first hopping beam dwell period, the terminal device receives the DCI sent by the network device. The DCI carries the offset k2 between the starting time T2 of the first PUSCH transmission during the first hopping beam dwell period and T1, and the offset k2' between the starting time T4 of the first hopping beam dwell and the starting time T5 of the first PUSCH transmission during the second hopping beam dwell period. In addition, T3 represents the end time of the PUSCH time-domain resources during the first hopping beam dwell period, and T6 represents the end position of the PUSCH time-domain resources during the second hopping beam dwell period.

[0064] Similarly, a first indication field is added in the DCI, and the first indication field includes the time-frequency resources during each hopping beam dwell period.

[0065] That is to say, compared with only indicating a set of starting transmission positions and time-frequency resources in the prior art, the embodiment of the present application indicates the time-frequency resources during at least two hopping beam dwell periods. Taking the network device configuring the transmission resources during the dwell periods of two hopping beams as an example, by adding a new indication field in the DCI, the transmission resources during the second hopping beam dwell period are indicated.

[0066] In a non-limiting embodiment, the signaling for scheduling the PUSCH transmission may include a second indication field, and the second indication field includes the number of repeated transmissions.

[0067] In a specific embodiment, the number of repeated transmissions of PUSCH during different hopping beam dwell periods is the same. If the number of repeated transmissions of PUSCH during different hopping beam dwell periods is the same, then the networked device can configure only one number of repeated transmissions, and the terminal device applies this number of repeated transmissions during each hopping beam dwell period before the number of repeated transmissions is updated.

[0068] In another specific embodiment, the number of repeated transmissions of PUSCH during different hopping beam dwell periods is different. If the number of repeated transmissions of PUSCH during different hopping beam dwell periods is different, then the networked device needs to configure a number of repeated transmissions for each hopping beam dwell period, and the terminal device uses the corresponding number of repeated transmissions during each different hopping beam dwell period.

[0069] In a non - restrictive embodiment, the first information indicates the transmission resources for repeating a set of PUSCH during each of at least two hopping beam dwell periods.

[0070] In this embodiment, the network device can perform grouped scheduling on the repeated - transmitted PUSCH. Then the first indication information can indicate the transmission resources in groups during at least two hopping beam dwell periods.

[0071] For example, when 32 PUSCH repeated transmissions are required, the network device can perform scheduling with a granularity of 8 repeated transmissions as a group. The transmission resources of a group of PUSCH ensure that 8 repeated transmissions can be completed during each hopping beam dwell period. Except for the first dwell period, the starting transmission positions, the occupied time - domain resources (number of time slots), and the frequency - domain resources (physical resource blocks) during other dwell periods can be the same.

[0072] Specifically, refer to Figure 6 , Figure 6 which shows the distribution of PUSCH transmission resources during four hopping beam dwell periods. The first information can indicate the following information: the first group of PUSCH transmission resources during the first hopping beam dwell period, the second group of PUSCH transmission resources during the second hopping beam dwell period, the third group of PUSCH transmission resources during the third hopping beam dwell period, and the fourth group of PUSCH transmission resources during the fourth hopping beam dwell period. Among them, the first group of PUSCH transmission resources, the second group of PUSCH transmission resources, the third group of PUSCH transmission resources, and the fourth group of PUSCH transmission resources all refer to the resources that can complete 8 PUSCH repeated transmissions.

[0073] In a non - restrictive embodiment, the accuracy of timing is improved by agreeing on the actions of timing on the terminal device and network device sides.

[0074] Please refer to Figure 7, in step 701, the terminal device receives the second information sent by the network device. The second information indicates the timing duration of staying in the active BWP, that is, it indicates the timing duration for the terminal device to switch from entering the active partial bandwidth BWP to the default BWP. Specifically, the terminal device stays in the default BWP in the idle state, switches from the default BWP to the active BWP when entering the connected state, and switches from the active BWP to the default BWP after the timing duration expires.

[0075] In step 702, the terminal device starts timing during the beam hopping residence period and stops timing during the beam hopping non-residence period.

[0076] In this embodiment, the timing operation can be completed by a timer set in the terminal device.

[0077] As mentioned above, after introducing beam hopping, there is no uplink and downlink data transmission during the non-residence time, and the timer is still working, resulting in invalid timing. To ensure the accuracy of timing, in the embodiments of the present application, timing is performed during the beam hopping residence period and timing is stopped during the beam hopping non-residence period.

[0078] Specifically, after the terminal device enters the RRC connected state, it will switch from the default BWP to the active BWP for data transmission. The network configures a timer bwp-InactivityTimer, and the timing duration of this timer is configured by the aforementioned second information. The timer normally times during the beam hopping residence period, stops timing during the beam hopping non-residence period, and continues timing in the next beam hopping residence period. When the timer expires, the terminal switches from the active BWP to the default BWP.

[0079] In a non-limiting embodiment, the terminal device switches from the active BWP to the default BWP during the beam hopping non-residence period and stops timing, and switches from the default BWP to the active BWP during the beam hopping residence period and starts timing again.

[0080] Specifically, during the beam hopping non-residence period, the terminal switches to the default BWP and resets the timer. During the beam hopping residence period of the device, the terminal switches to the active BWP and the timer starts.

[0081] By making the terminal device stop timing during the beam hopping non-residence period, the embodiments of the present application can avoid invalid timing when there is no uplink and downlink data transmission during the beam hopping non-residence period, improve the accuracy of timing, and thus ensure the effectiveness of BWP switching.

[0082] In step 703, the terminal device times during both the beam hopping non-residence period and the beam hopping residence period. In this case, the timing duration is selected from multiple values with the largest numerical values among the candidate durations.

[0083] Specifically, when configuring the BWP timer, the network device can configure a relatively large value (currently up to 2560 ms), such as 3200 milliseconds (ms), 3840 ms, 4480 ms, 5120 ms, etc. In this case, the terminal device can keep timing during the beam hopping non-resident period.

[0084] In the embodiment of the present application, by setting the timing duration to a relatively large value, the terminal device times both during the beam hopping non-resident period and the beam hopping resident period, thereby avoiding premature timeout of the timing during the beam hopping non-resident period and ensuring the effectiveness of BWP switching.

[0085] It should be noted that the terminal device can selectively execute one of step 702 and step 703.

[0086] It can be understood that the relevant behaviors of the above-mentioned terminal device timing can be specified by communication standard protocols, and the present application does not limit this.

[0087] In a non-limiting embodiment, if the discontinuous reception (DRX) sleep period is within the beam hopping non-resident period of the beam hopping cycle, the terminal device wakes up during the next DRX wake-up period. Through the above settings, it can be ensured that the terminal device wakes up during the next DRX wake-up period when no wake-up signal is received, realizing the wake-up of the terminal device.

[0088] Specifically, if the terminal does not detect a wake-up signal outside the DRX wake-up period (which can also be referred to as the on duration), such as DCI 2-6, or the wake-up signal is in the beam hopping non-resident period (i.e., the network sends a wake-up signal during the beam hopping non-resident period), then the network device and the terminal device default that the terminal device is in the wake-up state, and the terminal device wakes up during the next DRX wake-up period.

[0089] It can be understood that the relevant behaviors of the above-mentioned terminal device wake-up can be specified by communication standard protocols, and the present application does not limit this.

[0090] For more specific implementation manners of the embodiments of the present application, please refer to the foregoing embodiments, and details are not described herein again.

[0091] Please refer to Figure 8 , Figure 8 Fig. shows a communication device 80, which may include:

[0092] A communication module 801, configured to receive first information, where the first information indicates transmission resources for repeating the transmission of a physical uplink shared channel (PUSCH) during at least two beam hopping resident periods, and the first information includes at least one of the following: a starting transmission position, a number of repeated transmissions, and time-frequency resources.

[0093] Further, the communication module 801 may also receive second information, where the second information indicates the timing duration of staying in the active BWP.

[0094] Correspondingly, the communication device 80 may include a processing module that times during the beam hopping stay period and stops timing during the beam hopping non-stay period; or, the processing module times during the beam hopping non-stay period and during the beam hopping stay period, and the target timing duration is selected from the M largest values among the candidate durations.

[0095] In a specific implementation, the above-mentioned communication device 80 may correspond to a chip with communication functions in a terminal device, such as a System-On-a-Chip (SOC), a baseband chip, etc.; or correspond to a chip module including a chip with communication functions in a terminal device; or correspond to a chip module with a data processing function chip, or correspond to a terminal device.

[0096] In another non-limiting embodiment, the communication module 801 is used to send first information, where the first information indicates the transmission resources for repeating the transmission of the Physical Uplink Shared Channel (PUSCH) during at least two beam hopping stay periods, and the first information includes at least one of the following: the starting transmission position, the number of repeated transmissions, and the time-frequency resources.

[0097] Further, the communication module 801 may also send second information, where the second information indicates the timing duration of staying in the active BWP.

[0098] In a specific implementation, the above-mentioned communication device 80 may correspond to a chip with communication functions in a network device, such as an SOC, a baseband chip, etc.; or correspond to a chip module including a chip with communication functions in a network device; or correspond to a chip module with a data processing function chip, or correspond to a network device.

[0099] Other related descriptions of the communication device 80 may refer to the relevant descriptions in the foregoing embodiments, and will not be elaborated here.

[0100] Regarding each device and product described in the above embodiments, each module / unit included therein can be a software module / unit, a hardware module / unit, or can be partially a software module / unit and partially a hardware module / unit. For example, for each device and product applied to or integrated into a chip, each module / unit included therein can be implemented in a hardware manner such as a circuit, or at least some of the modules / units can be implemented in a software program manner, and this software program runs on a processor integrated inside the chip, and the remaining (if any) part of the modules / units can be implemented in a hardware manner such as a circuit; for each device and product applied to or integrated into a chip module, each module / unit included therein can be implemented in a hardware manner such as a circuit, and different modules / units can be located in the same component (such as a chip, a circuit module, etc.) or different components of the chip module, or at least some of the modules / units can be implemented in a software program manner, and this software program runs on a processor integrated inside the chip module, and the remaining (if any) part of the modules / units can be implemented in a hardware manner such as a circuit; for each device and product applied to or integrated into a terminal device, each module / unit included therein can be implemented in a hardware manner such as a circuit, and different modules / units can be located in the same component (such as a chip, a circuit module, etc.) or different components inside the terminal device, or at least some of the modules / units can be implemented in a software program manner, and this software program runs on a processor integrated inside the terminal device, and the remaining (if any) part of the modules / units can be implemented in a hardware manner such as a circuit.

[0101] An embodiment of the present application also discloses a storage medium, the storage medium is a computer-readable storage medium, on which a computer program is stored, and when the computer program runs, it can execute Figures 1 to 3 the steps of the method shown in. The storage medium can include a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disc, etc. The storage medium can also include a non-volatile memory or a non-transitory memory, etc.

[0102] Please refer to Figure 9 , an embodiment of the present application also provides a schematic diagram of the hardware structure of a communication device. The device includes a processor 901, a memory 902, and a transceiver 903.

[0103] The processor 901 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the solution of this application. The processor 901 may also include multiple CPUs, and the processor 901 may be a single-CPU processor or a multi-CPU processor. The processor here may refer to one or more devices, circuits, or processing cores for processing data (such as computer program instructions).

[0104] The memory 902 may be a ROM or other type of static storage device that can store static information and instructions, a RAM, or other type of dynamic storage device that can store information and instructions. It may also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM), or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media, or any other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer. The embodiments of this application do not impose any restrictions on this. The memory 902 may exist independently (in this case, the memory 902 may be located outside or inside the device), or may be integrated with the processor 901. Among them, the memory 902 may contain computer program code. The processor 901 is used to execute the computer program code stored in the memory 902, so as to implement the method provided by the embodiments of this application.

[0105] The processor 901, the memory 902, and the transceiver 903 are connected by a bus. The transceiver 903 is used to communicate with other devices or communication networks. Optionally, the transceiver 903 may include a transmitter and a receiver. The device in the transceiver 903 used to implement the receiving function can be regarded as a receiver, and the receiver is used to execute the receiving steps in the embodiments of this application. The device in the transceiver 903 used to implement the sending function can be regarded as a transmitter, and the transmitter is used to execute the sending steps in the embodiments of this application.

[0106] When Figure 9 The shown structural schematic diagram is used to illustrate the structure of the terminal device involved in the above embodiments, the processor 901 is used to control and manage the actions of the terminal device. For example, the processor 901 is used to support the terminal device to executeFigure 4 Steps 401 and 402 in, or Figure 7 Steps 701, 702, and 703 in, and / or actions performed by the terminal device in other processes described in the embodiments of the present application. The processor 901 can communicate with other network entities through the transceiver 903. For example, it can communicate with the above-mentioned network device. The memory 902 is used to store the program code and data of the terminal device.

[0107] When Figure 9 The structural schematic diagram shown is used to illustrate the structure of the network device involved in the above embodiments, the processor 901 is used to control and manage the actions of the network device. For example, the processor 901 is used to support the network device to execute the steps in FIG. Figure 4 Steps 401 and 402 in, or Figure 7 Step 701 in, and / or actions performed by the network device in other processes described in the embodiments of the present application. The processor 901 can communicate with other network entities through the transceiver 903. For example, it can communicate with the above-mentioned terminal device. The memory 902 is used to store the program code and data of the network device.

[0108] In the embodiments of the present application, the unidirectional communication link from the access network to the terminal device is defined as the downlink. The data transmitted on the downlink is downlink data, and the transmission direction of the downlink data is called the downlink direction; while the unidirectional communication link from the terminal device to the access network is the uplink. The data transmitted on the uplink is uplink data, and the transmission direction of the uplink data is called the uplink direction.

[0109] It should be understood that the term "and / or" in this article is only a description of the association relationship between associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this article indicates that the associated objects before and after are in an "or" relationship.

[0110] The "multiple" mentioned in the embodiments of the present application refers to two or more.

[0111] The descriptions such as first and second that appear in the embodiments of the present application are only for schematic and distinguishing description objects, without an order, and do not represent a special limitation on the number of devices in the embodiments of the present application, and cannot constitute any limitation to the embodiments of the present application.

[0112] The "connection" that appears in the embodiments of the present application refers to various connection methods such as direct connection or indirect connection to achieve communication between devices. The embodiments of the present application do not make any limitations on this.

[0113] The above embodiments can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, the above embodiments 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 or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired or wireless manner.

[0114] It should be understood that in various embodiments of the present application, the order of the above processes does not mean the order of execution. The order of execution of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

[0115] In several embodiments provided in the present application, it should be understood that the disclosed methods, devices, and systems can be implemented in other ways. For example, the device embodiments described above are merely illustrative; for example, the division of the units is only a logical function division, and there may be other division methods in actual implementation; for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling, direct coupling, or communication connection to each other can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be in an electrical, mechanical, or other form.

[0116] The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they can be located in one place or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0117] In addition, the functional units in various embodiments of the present application can be integrated into one processing unit, or each unit can be physically included separately, or two or more units can be integrated into one unit. The above integrated units can be implemented in the form of hardware or in the form of a combination of hardware and software functional units.

[0118] The integrated unit implemented in the form of software functional units can be stored in a computer-readable storage medium. The above software functional units are stored in a storage medium and include several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute some steps of the methods described in various embodiments of the present application.

[0119] Although the present application is disclosed as above, the present application is not limited thereto. Any person skilled in the art can make various changes and modifications without departing from the spirit and scope of the present application. Therefore, the protection scope of the present application should be subject to the scope defined by the claims.

Claims

1. A communication method, characterized in that, it includes: receiving a first piece of information, where the first piece of information indicates transmission resources for repeating the transmission of a Physical Uplink Shared Channel (PUSCH) during at least two hopping beam dwell periods, and the first piece of information includes at least one of the following: starting transmission position, number of repeated transmissions, and time-frequency resources.

2. The communication method according to claim 1, characterized in that, the starting transmission position includes a first offset value of the starting position of the first PUSCH transmission during the first hopping beam dwell period from the time slot where the signaling for scheduling the PUSCH transmission is located, and a second offset value of the starting transmission position of the PUSCH during other hopping beam dwell periods from the starting position of the hopping beam dwell.

3. The communication method according to claim 1, characterized in that, the first piece of information includes time-frequency resources, and the time-frequency resources include time-frequency resources during each hopping beam dwell period.

4. The communication method according to claim 3, characterized in that, the first piece of information indicates transmission resources for repeating the transmission of a group of PUSCHs during each hopping beam dwell period among the at least two hopping beam dwell periods.

5. The communication method according to claim 1, characterized in that, the first piece of information includes the number of repeated transmissions, and the number of repeated transmissions of the PUSCH during different hopping beam dwell periods is the same or different.

6. The communication method according to claim 1, characterized in that, it further includes: receiving a second piece of information, where the second piece of information indicates the timing duration of dwelling in an active partial bandwidth (BWP); timing during the hopping beam dwell period and stopping timing during the non-hopping beam dwell period; or, timing during the non-hopping beam dwell period and during the hopping beam dwell period.

7. The communication method according to claim 6, characterized in that, the timing during the hopping beam dwell period and stopping timing during the non-hopping beam dwell period includes: stopping timing during each non-hopping beam dwell period and continuing timing during the next hopping beam dwell period.

8. The communication method according to claim 6, characterized in that, the timing during the hopping beam dwell period and stopping timing during the non-hopping beam dwell period includes: stopping timing during the non-hopping beam dwell period and re-timing during the hopping beam dwell period.

9. The communication method according to claim 6, characterized in that, the timing duration value indicated by the second piece of information includes at least one of the following: 3200 milliseconds, 3840 milliseconds, 4480 milliseconds, 5120 milliseconds.

10. A communication method, characterized in that, it includes: sending a first piece of information, where the first piece of information indicates transmission resources for repeating the transmission of a Physical Uplink Shared Channel (PUSCH) during at least two hopping beam dwell periods, and the first piece of information includes at least one of the following: starting transmission position, number of repeated transmissions, and time-frequency resources.

11. The communication method according to claim 10, characterized in that, The starting transmission position includes a first offset value of the starting position of the first PUSCH transmission during the first-hop beam dwell from the time slot where the signaling for scheduling the PUSCH transmission is located, and a second offset value of the starting transmission position of the PUSCH during other-hop beam dwells from the starting position of the hop-beam dwell.

12. The communication method according to claim 10, wherein, the first information includes time-frequency resources, and the time-frequency resources include time-frequency resources during each hop-beam dwell.

13. The communication method according to claim 10, wherein, it further includes: sending second information, the second information indicating the timing duration of dwelling in the active partial bandwidth BWP; timing during the hop-beam dwell and stopping timing during the non-hop-beam dwell; or, timing during the non-hop-beam dwell and during the hop-beam dwell.

14. A communication device, wherein, it includes: a communication module, configured to receive first information, the first information indicating transmission resources for repeating the transmission of a physical uplink shared channel (PUSCH) during at least two hop-beam dwells, and the first information includes at least one of the following: starting transmission position, number of repeat transmissions, and time-frequency resources.

15. A communication device, wherein, it includes: a communication module, configured to send first information, the first information indicating transmission resources for repeating the transmission of a physical uplink shared channel (PUSCH) during at least two hop-beam dwells, and the first information includes at least one of the following: starting transmission position, number of repeat transmissions, and time-frequency resources.

16. A computer-readable storage medium, on which a computer program is stored, wherein, when the computer program is run by a processor, it executes the steps of the communication method according to any one of claims 1 to 9, or executes the steps of the communication method according to any one of claims 10 to 13.

17. A communication device includes a memory and a processor, and a computer program that can run on the processor is stored on the memory, wherein, when the processor runs the computer program, it executes the steps of the communication method according to any one of claims 1 to 9.

18. A communication device includes a memory and a processor, and a computer program that can run on the processor is stored on the memory, wherein, when the processor runs the computer program, it executes the steps of the communication method according to any one of claims 10 to 13.

Images