Detailed Description
The following description of the technical solutions according to the embodiments of the present application will be given with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art to which the application pertains without inventive faculty, are intended to fall within the scope of the application.
The embodiment of the application can be applied to various communication systems, such as a global system for mobile communication (Global System of Mobile communication, GSM) system, a code division multiple access (Code Division Multiple Access, CDMA) system, a wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, a general packet Radio Service (GENERAL PACKET Radio Service, GPRS), a long term evolution (Long Term Evolution, LTE) system, a long term evolution (Advanced long term evolution, LTE-A) system, a New air interface (New Radio, NR) system, an evolution system of NR system, an LTE (LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, an NR (NR-based access to unlicensed spectrum, NR-U) system on unlicensed spectrum, a universal mobile communication system (Universal Mobile Telecommunication System, UMTS), a wireless local area network (Wireless Local Area Networks, WLAN), a wireless fidelity (WIRELESS FIDELITY, WIFI), a next-generation communication system or other communication systems and the like.
Generally, the number of connections supported by the conventional Communication system is limited and easy to implement, however, as the Communication technology advances, the mobile Communication system will support not only conventional Communication but also, for example, device-to-Device (D2D) Communication, machine-to-machine (Machine to Machine, M2M) Communication, machine type Communication (MACHINE TYPE Communication, MTC), inter-vehicle (Vehicle to Vehicle, V2V) Communication, and the like, and the embodiments of the present application can also be applied to these Communication systems.
Optionally, the communication system in the embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, or an independent (Standalone, SA) networking scenario.
The frequency spectrum of the application of the embodiment of the application is not limited. For example, the embodiment of the application can be applied to licensed spectrum and unlicensed spectrum.
An exemplary communication system 100 to which embodiments of the present application may be applied is shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within the coverage area.
Fig. 1 illustrates one network device and two terminal devices by way of example, and the communication system 100 may alternatively include multiple network devices and may include other numbers of terminal devices within the coverage area of each network device, as embodiments of the application are not limited in this regard.
Optionally, the communication system 100 may further include a network controller, a mobility management entity, and other network entities, which are not limited by the embodiment of the present application.
It should be understood that a device having a communication function in a network/system according to an embodiment of the present application may be referred to as a communication device. Taking the communication system 100 shown in fig. 1 as an example, the communication device may include a network device 110 and a terminal device 120 with communication functions, where the network device 110 and the terminal device 120 may be specific devices described above, which are not described herein, and the communication device may further include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in the embodiment of the present application.
It should be understood that the terms "system" and "network" are used interchangeably herein. The term "and/or" is merely an association relationship describing the associated object, and means that three relationships may exist, for example, a and/or B may mean that a exists alone, while a and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.
Embodiments of the present application are described in connection with terminal devices and network devices, where a terminal device may also be referred to as a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a User terminal, a wireless communication device, a User agent, a User Equipment, or the like. The terminal device may be a Station (ST) in a WLAN, may be a cellular telephone, a cordless telephone, 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) device, a handheld device with wireless communication functionality, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, and a next generation communication system, e.g. a terminal device in an NR network or a terminal device in a future evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.
By way of example, and not limitation, in embodiments of the present application, the terminal device may also be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device comprises full functions, large size and complete or partial functions which can be realized independently of a smart phone, such as a smart watch, a smart glasses and the like, and is only focused on certain application functions, and needs to be matched with other devices such as the smart phone for use, such as various smart bracelets, smart jewelry and the like for physical sign monitoring.
The network device may be a device for communicating with the mobile device, the network device may be an Access Point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or an Access Point, or a vehicle device, a wearable device, and a network device in NR network or a base station (gNB) or a network device in future evolved PLMN network, etc.
In the embodiment of the application, the network equipment provides service for the cell, the terminal equipment communicates with the network equipment through the transmission resource (such as frequency domain resource or spectrum resource) used by the cell, the cell can be a cell corresponding to the network equipment (such as a base station), the cell can belong to a macro base station or a base station corresponding to a small cell (SMALL CELL), the small cell can comprise a urban cell (Metro cell), a Micro cell (Micro cell), a Pico cell (Pico cell), a Femto cell (Femto cell) and the like, and the small cells have the characteristics of small coverage area and low transmitting power and are suitable for providing high-rate data transmission service.
It should be appreciated that Multiple-Input Multiple-Output (MIMO) technology may be employed in the present application.
Before introducing the technical scheme of the present application, the following first describes SRS, an uplink transmission scheme based on a codebook, and an indication manner of SRS resources in the uplink transmission scheme based on the codebook:
(1)SRS
SRS can be used for uplink channel information acquisition, downlink channel information acquisition and uplink beam management. The New Radio (NR) system performs SRS management and configuration in the manner of SRS resource set. The network device may configure a plurality of SRS resource sets for the terminal device according to different purposes, where each SRS resource set includes one or more SRS resources, and each SRS resource includes 1, 2, or 4 ports. The configuration information of each SRS resource set includes a usage indication, which may be configured as "beamManagement", "codebook", "nonCodebook" or "ANTENNASWITCHING", and is used for uplink beam management, uplink channel information acquisition based on a codebook, uplink channel information acquisition based on a non-codebook uplink transmission scheme, and downlink channel information acquisition based on SRS antenna switching, respectively.
(2) Uplink transmission scheme based on codebook
Fig. 2 is a flowchart of a codebook-based uplink transmission scheme, and as shown in fig. 2, the codebook-based uplink transmission scheme in the NR system R16 includes the following steps:
Step S210, the terminal equipment sends at least one SRS to the network equipment according to the SRS resources configured by the network equipment.
In step S220, the network device measures the channel of at least one SRS to obtain a channel measurement result, and selects an SRS resource, a transmission layer number, a transmission precoding matrix indicator (TRANSMITTED PRECODING MATRIX INDICATOR, TPMI), demodulation reference signal (Demodulation REFERENCE SGNAL, DMRS) port indicator information, PUSCH resource allocation and a corresponding modulation and coding strategy (Modulation and Coding Scheme, MCS) in the SRS set according to the channel measurement result.
Step S230, the network device sends DCI to the terminal device.
The DCI comprises SRS resource indication (SRS Resource Indicator, SRI), transmission layer number, TPMI, DMRS port indication information, PUSCH resource allocation and corresponding MCS, wherein the SRI is used for indicating SRS resources selected by network equipment.
In step S240, the terminal device performs modulation coding on the PUSCH data according to the MCS, determines the precoding matrix and the number of transmission layers used when the data is transmitted by using the SRI, the TPMI and the number of transmission layers, and selects the precoder of the PUSCH from the codebook by using the TPMI.
Step S250, the terminal equipment performs precoding transmission on the PUSCH through the selected precoder according to the precoding matrix and the transmission layer number.
Wherein, the DMRS of PUSCH and the data of PUSCH are precoded in the same way.
In step S260, the network device estimates an uplink channel according to the DMRS, and demodulates and decodes the data PUSHC.
It should be understood that, as can be seen from the above-mentioned uplink transmission scheme based on the codebook, in R16, the terminal device performs PUSCH transmission according to one SRS resource.
(3) SRI in codebook-based uplink transmission scheme
The PUSCH transmission scheme is configured through higher layer signaling, and before the network device configures the Uplink transmission scheme for the terminal device through higher layer signaling, the network device can only schedule the PUSCH through DCI format 0_0 (i.e., DCI in format 0_0), where no SRI exists in the DCI format 0_0, and when the PUSCH is scheduled through DCI format 0_0, the PUSCH is transmitted using a single port, i.e., using the same Uplink transmission beam as the physical Uplink control channel (Physical Uplink Control Channel, PUCCH) identified as the smallest in the Uplink (UL) portion BandWidth (BandWidth Part, BWP) is used.
When the network device schedules PUSCH through DCI format 0_1 or DCI format 0_2, the DCI carries SRI, where the size of the SRI field is determined according to the usage indication configured by the network device for the SRS resource set and information such as the number of SRS resources in the SRS resource set. For example, when the usage of the network device for SRS resource set configuration is indicated as 'codebook', the SRI field is of sizeAnd sets corresponding bits according to the specifically selected SRS resources. If the number of SRS resources in the SRS resource set is 4, the size of the SRI field is 2 bits, and different bits in the SRI field correspond to different SRS resources, see table 1 specifically:
TABLE 1
Index corresponding to different bits |
SRI resources |
0 |
SRI resource 0 |
1 |
SRI resource 1 |
2 |
SRI resource 2 |
3 |
SRI resource 4 |
Similarly, if the number of SRS resources in the SRS resource set is 2, the size of the SRI field is 1 bit, and different bits in the SRI field correspond to different SRS resources, see table 2 for details:
TABLE 2
Index corresponding to different bits |
SRI resources |
0 |
SRI resource 0 |
1 |
SRI resource 1 |
Similarly, if the number of SRS resources in the SRS resource set is 3, the size of the SRI field is 2 bits, and different bits in the SRI field correspond to different SRS resources, see in particular Table 3: table 3
Index corresponding to different bits |
SRI resources |
0 |
SRI resource 0 |
1 |
SRI resource 1 |
2 |
SRI resource 2 |
3 |
Reservation |
In summary, in R16, when the terminal device sends PUSCH, it can only transmit according to one SRS resource, and correspondingly, the SRI in DCI indicates only one SRS resource. However, in R17, enhancement transmission of PUSCH based on multiple TRP is required, meaning that the same PUSCH needs to be transmitted to different TRP through different beams, whereas in the prior art, the case that the network device indicates only one SRS resource through DCI cannot be flexibly adapted to enhancement transmission scheme of PUSCH based on multiple TRP or PUSCH transmission scheme based on single TRP.
In order to solve the above technical problem, the SRI in the present application may indicate a plurality of SRS resources for different services to be applicable to a PUSCH enhanced transmission scheme under multiple TRPs, or indicate one SRS resource to be applicable to a PUSCH enhanced transmission scheme under a single TRP.
The technical scheme of the application will be described in detail as follows:
fig. 3 is an interaction flow chart of a wireless communication method according to an embodiment of the present application, as shown in fig. 3, the method includes the following steps:
step S310, the terminal device sends at least one SRS to the network device.
Step S320, the network device measures the channels of at least one SRS to obtain a channel measurement result of at least one SRS, and selects at least one SRS resource in the SRS resource set of the terminal device according to the channel measurement result of at least one SRS.
Step S330, the network device sends first indication information to the terminal device, wherein the first indication information is used for indicating at least one SRS resource selected by the network device.
Optionally, the network device configures a transmission scheme of the uplink channel to be a codebook-based uplink transmission scheme.
Optionally, the network device may configure the terminal device with an SRS resource set, where the SRS resource set includes a "codebook" usage indication, and indicates that the SRS resource set is used for codebook-based uplink channel information acquisition.
It should be understood that the network device may also configure a plurality of SRS resource sets for the terminal device, where one SRS resource set is selected for codebook-based uplink channel information acquisition.
Alternatively, if the terminal device transmits a plurality of SRS to the network device, the beams used for transmitting the SRS are different.
Optionally, for any one of the at least one SRS, when the channel measurement result of the SRS meets a preset condition, the network device selects an SRS resource corresponding to the SRS. Or the channel measurement result of the SRS and the SRS resource have a correspondence, and the terminal device may select at least one SRS resource in the SRS resource set according to the correspondence and the channel measurement result of the at least one SRS obtained by performing channel measurement.
Alternatively, the preset condition may be configured by a network device, and the specific content of the preset condition is not limited by the present application.
Optionally, the correspondence between the SRS channel measurement result and the SRS resource may be configured by the network device, and the present application does not limit the specific content of the correspondence.
Alternatively, the terminal device may consider the traffic types when selecting SRS resources, for example, some traffic types require PUSCH transmission under a single TRP, and some traffic types require PUSCH transmission under multiple TRP.
It should be appreciated that the present application is not limited to the method of selecting SRS resources in the SRS resource set.
Alternatively, the first indication information may be carried in DCI or a medium access control unit (MEDIA ACCESS Control Control Element, MAC CE), which is not limited by the present application.
Optionally, the first indication information is SRI.
It should be appreciated that when the network device selects one SRS resource, the one SRS resource is used for uplink channel transmission from the terminal device to the single transceiver point TRP, and when the network device selects a plurality of SRS resources, the plurality of SRS resources are used for uplink channel transmission from the terminal device to the plurality of TRPs.
Optionally, after the terminal device receives the first indication information, the terminal device may perform uplink channel transmission according to at least one SRS resource. For example, the terminal device obtains the transmission layer number, the TPMI, the DMRS port indication information, the PUSCH resource allocation and the corresponding MCS for any one of the SRS resources selected in addition to the first indication information, and may modulate and encode the PUSCH data according to the MCS, determine the precoding matrix and the transmission layer number used when the data is transmitted by using the first indication information, the TPMI and the transmission layer number, and select the precoder of the PUSCH from the codebook using the TPMI. And the terminal equipment performs precoding transmission on the PUSCH through the selected precoder according to the precoding matrix and the transmission layer number.
Alternatively, the uplink channel may be a PUSCH, which the present application is not limited to.
It should be understood that the uplink channel transmission in the present application refers to uplink channel enhanced transmission, for example, when the uplink channel is PUSCH, then the uplink channel transmission herein refers to enhanced transmission of PUSCH.
As described above, the first indication information is used to indicate at least one SRS resource selected by the network device, where the at least one SRS resource is used for uplink channel transmission from the terminal device to a single TRP or multiple TRP, and this indication manner is described below by way of example:
The first example includes that the network device may configure an uplink transmission scheme of a PUSCH as an uplink transmission scheme based on a codebook, the network device configures an SRS resource set, the function of the resource set is configured as the codebook, 2 SRS resources are configured in the resource set, and are respectively SRS resource 0 and SRS resource 1, the terminal device may send at least one SRS to the network device, and the network device performs measurement on at least one SRS according to at least one SRS, so as to obtain a channel measurement result of at least one SRS. And the network equipment selects SRS resource 0in the SRS resource set of the terminal equipment according to the channel measurement result of the at least one SRS. The network device sends first indication information 00 to the terminal device, wherein the first indication information 00 is used for indicating SRS resource 0 selected by the network device. Or the network device selects SRS resources 0 and 1 in the SRS resource set of the terminal device according to the channel measurement result of at least one SRS. The network device sends first indication information 10 to the terminal device, where the first indication information is used to indicate SRS resource 0 and SRS resource 1 selected by the network device.
The correspondence between the indication information in the SRI domain and the SRS resource is shown in table 4. TABLE 4 Table 4
Indication information in SRI domain |
SRS resources |
00 |
SRS resource 0 |
01 |
SRS resource 1 |
10 |
SRS resource 0 and SRS resource 1 |
Based on this, the terminal device may select SRS resource 0 for uplink PUSCH transmission of a single TRP according to the first indication information 00. The terminal device may select SRS resource 0 and SRS resource 1 for uplink PUSCH transmission of multiple TRP according to the first indication information 10.
The second example is that the network device may configure the uplink transmission scheme of the PUSCH as the uplink transmission scheme based on the codebook, the network device configures an SRS resource set, the action of the resource set is configured as the codebook, 3 SRS resources are configured in the resource set, and are respectively SRS resource 0, SRS resource 1 and SRS resource 2, wherein SRS resources 0 and 1 are two SRS resources with the same beam configuration, and SRS resource 2 and SRS resource 0 and 1 are respectively two SRS resources with different beam configurations. The network equipment performs measurement on the channels of the at least one SRS according to the at least one SRS to obtain a channel measurement result of the at least one SRS. And the network equipment selects SRS resources 0 and 2 in the SRS resource set of the terminal equipment according to the channel measurement result of at least one SRS. The network device sends first indication information 011 to the terminal device, where the first indication information 011 is used to indicate SRS resource 0 and SRS resource 2 selected by the network device.
The correspondence between the indication information in the SRI domain and the SRS resource is shown in table 5.
TABLE 5
Indication information in SRI domain |
SRS resources |
000 |
SRS resource 0 |
001 |
SRS resource 1 |
010 |
SRS resource 2 |
011 |
SRS resource 0 and SRS resource 2 |
100 |
SRS resource 1 and SRS resource 2 |
Based on this, the terminal device may select SRS resource 0 and SRS resource 2 for uplink PUSCH transmission of multiple TRP according to the first indication information 011.
Optionally, the length of the indication domain where the first indication information is located, i.e. the SRI domain, is determined according to the number of resources in the SRS resource set. For example, in example one, the number of resources in the SRS resource set is 2, the length of the SRI field is 2 bits, i.e., the SRI field occupies 2 bits, and in example two, the number of resources in the SRS resource set is 3, the length of the SRI field is 3 bits, i.e., the SRI field occupies 3 bits.
Alternatively, the network device may transmit second indication information to the terminal device to indicate SRS resources having the same beam configuration. So that the terminal device can learn which SRS resources correspond to the same beam configuration, e.g., in example two SRS resources 0 and 1 are two SRS resources with the same beam configuration.
Optionally, the second indication information is semi-statically configured by the network device through higher layer signaling or dynamically configured through physical layer signaling, but is not limited thereto.
Alternatively, the higher layer signaling may be RRC signaling.
Alternatively, the physical layer signaling may be DCI signaling or MAC CE signaling.
Optionally, the second indication information is spatial relationship information (spatialrelationinfo) of the SRS resource configuration for the network device with the same beam configuration.
Optionally, in order to be suitable for the scenario of multiple TRPs, if the first indication information is used to instruct the network device to select multiple SRS resources in the SRS resource set of the terminal device according to the channel measurement result of at least one SRS, the multiple SRS resources are multiple SRS resources with different beam configurations, and based on this, the terminal device may send PUSCH to different TRPs through different beams.
In summary, in the present application, a network device sends first indication information to a terminal device, where the first indication information is used to indicate at least one SRS resource selected by the network device. When the network device selects one SRS resource, the one SRS resource is used for uplink channel transmission from the terminal device to the single receiving and transmitting point TRP, and when the network device selects a plurality of SRS resources, the plurality of SRS resources are used for uplink channel transmission from the terminal device to the plurality of TRPs. Thus, the method can be flexibly applicable to the enhanced transmission scheme of the PUSCH based on multiple TRPs or the PUSCH transmission scheme based on single TRP.
Fig. 4 shows a schematic block diagram of a terminal device 400 according to an embodiment of the application. As shown in fig. 4, the terminal device 400 includes a communication unit 410 configured to send at least one SRS to a network device, and receive first indication information, where the first indication information is configured to instruct the network device to select at least one SRS resource in an SRS resource set of the terminal device according to a channel measurement result of the at least one SRS, where the at least one SRS resource is used for uplink channel transmission from the terminal device to a single TRP or multiple TRP.
Optionally, the length of the indication domain where the first indication information is located is determined according to the number of resources in the SRS resource set.
Optionally, the communication unit 410 is further configured to receive second indication information, where the second indication information is used to indicate SRS resources with the same beam configuration.
Optionally, the second indication information is semi-statically configured by the network device through higher layer signaling or dynamically configured through physical layer signaling.
Optionally, the second indication information is spatial relationship information of SRS resource configurations for the network device having the same beam configuration.
Optionally, if the first indication information is used to indicate the network device to select a plurality of SRS resources in the SRS resource set of the terminal device according to the channel measurement result of the at least one SRS, the plurality of SRS resources are a plurality of SRS resources with different beam configurations.
Optionally, the channel measurement result of the at least one SRS has a correspondence with the at least one SRS resource.
Optionally, the correspondence is network device configured.
Optionally, the first indication information is carried in DCI or MAC CE.
Optionally, the communication unit 410 is further configured to perform uplink channel transmission according to at least one SRS resource.
Optionally, the uplink channel is PUSCH.
Optionally, the SRS resource set is used for uplink channel information acquisition based on the codebook.
Alternatively, in some embodiments, the communication unit may be a communication interface or transceiver, or an input/output interface of a communication chip or a system on a chip. The processing unit may be one or more processors.
It should be understood that the terminal device 400 according to the embodiment of the present application may correspond to the terminal device in the embodiment of the method of fig. 3, and the above and other operations and/or functions of each unit in the terminal device 400 are respectively for implementing the corresponding flow of the terminal device in the embodiment of the method of fig. 3, which is not described herein for brevity.
Fig. 5 shows a schematic block diagram of a network device 500 according to an embodiment of the application. As shown in fig. 5, the network device 500 includes a communication unit 510 and a processing unit 520. Wherein the communication unit 510 is configured to receive at least one SRS. The processing unit 520 is configured to measure the channels of the at least one SRS, obtain a channel measurement result for the at least one SRS, and select at least one SRS resource in the SRS resource set of the terminal device according to the channel measurement result for the at least one SRS. The communication unit 510 is further configured to send first indication information to the terminal device, where the first indication information is configured to instruct the network device to select at least one SRS resource in the SRS resource set of the terminal device according to a channel measurement result for the at least one SRS, and the at least one SRS resource is used for uplink channel transmission from the terminal device to the single TRP or the multiple TRP.
Optionally, the length of the indication domain where the first indication information is located is determined according to the number of resources in the SRS resource set.
Optionally, the communication unit 510 is further configured to send second indication information to the terminal device, where the second indication information is used to indicate SRS resources with the same beam configuration.
Optionally, the second indication information is semi-statically configured by the network device through higher layer signaling or dynamically configured through physical layer signaling.
Optionally, the second indication information is spatial relationship information of SRS resource configurations for the network device having the same beam configuration.
Optionally, if the first indication information is used to indicate the network device to select a plurality of SRS resources in the SRS resource set of the terminal device according to the channel measurement result of the at least one SRS, the plurality of SRS resources are a plurality of SRS resources with different beam configurations.
Optionally, the channel measurement result of the at least one SRS has a correspondence with the at least one SRS resource.
Optionally, the correspondence is network device configured.
Optionally, the first indication information is carried in DCI or MAC CE.
Optionally, the communication unit 510 is further configured to receive an uplink channel transmission through at least one SRS resource.
Optionally, the uplink channel is PUSCH.
Optionally, the SRS resource set is used for uplink channel information acquisition based on the codebook.
Alternatively, in some embodiments, the communication unit may be a communication interface or transceiver, or an input/output interface of a communication chip or a system on a chip. The processing unit may be one or more processors.
It should be understood that the network device 500 according to the embodiment of the present application may correspond to a method embodiment on the network device side, and the foregoing and other operations and/or functions of each unit in the network device 500 are respectively for implementing the corresponding flow of the network device in the method embodiment on the network device side, which are not described herein for brevity.
Fig. 6 is a schematic structural diagram of a communication device 600 provided in an embodiment of the present application. The communication device 600 shown in fig. 6 comprises a processor 610, from which the processor 610 may call and run a computer program to implement the method in an embodiment of the application.
Optionally, as shown in fig. 6, the communication device 600 may also include a memory 620. Wherein the processor 610 may call and run a computer program from the memory 620 to implement the method in an embodiment of the application.
The memory 620 may be a separate device from the processor 610 or may be integrated into the processor 610.
Optionally, as shown in fig. 6, the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, and in particular, may send information or data to other devices, or receive information or data sent by other devices.
The transceiver 630 may include a transmitter and a receiver, among others. Transceiver 630 may further include antennas, the number of which may be one or more.
Optionally, the communication device 600 may be specifically a network device according to the embodiment of the present application, and the communication device 600 may implement a corresponding flow implemented by the network device in each method according to the embodiment of the present application, which is not described herein for brevity.
Optionally, the communication device 600 may be specifically a terminal device in the embodiment of the present application, and the communication device 600 may implement a corresponding flow implemented by the terminal device in each method in the embodiment of the present application, which is not described herein for brevity.
Fig. 7 is a schematic structural view of an apparatus of an embodiment of the present application. The apparatus 700 shown in fig. 7 includes a processor 710, and the processor 710 may call and execute a computer program from a memory to implement the method in an embodiment of the present application.
Optionally, as shown in fig. 7, the apparatus 700 may further comprise a memory 720. Wherein the processor 710 may call and run a computer program from the memory 720 to implement the method in an embodiment of the application.
Wherein the memory 720 may be a separate device from the processor 710 or may be integrated into the processor 710.
Optionally, the apparatus 700 may further comprise an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and in particular, may obtain information or data sent by other devices or chips.
Optionally, the apparatus 700 may further comprise an output interface 740. The processor 710 may control the output interface 740 to communicate with other devices or chips, and in particular, may output information or data to other devices or chips.
Optionally, the apparatus may be applied to a network device in the embodiment of the present application, and the apparatus may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.
Optionally, the apparatus may be applied to a terminal device in the embodiment of the present application, and the apparatus may implement a corresponding flow implemented by the terminal device in each method in the embodiment of the present application, which is not described herein for brevity.
Alternatively, the device according to the embodiment of the present application may be a chip. For example, a system-on-chip or a system-on-chip, etc.
Fig. 8 is a schematic block diagram of a communication system 800 provided by an embodiment of the present application. As shown in fig. 8, the communication system 800 includes a terminal device 810 and a network device 820.
The terminal device 810 may be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 820 may be used to implement the corresponding functions implemented by the network device or the base station in the above method, which are not described herein for brevity.
It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The Processor may be a general purpose Processor, a digital signal Processor (DIGITAL SIGNAL Processor, DSP), an Application SPECIFIC INTEGRATED Circuit (ASIC), an off-the-shelf programmable gate array (Field Programmable GATE ARRAY, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.
It will be appreciated that the memory in embodiments of the application may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available, such as static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate Synchronous dynamic random access memory (Double DATA RATE SDRAM, DDR SDRAM), enhanced Synchronous dynamic random access memory (ENHANCED SDRAM, ESDRAM), synchronous link dynamic random access memory (SYNCHLINK DRAM, SLDRAM), and Direct memory bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.
It should be appreciated that the above memory is exemplary and not limiting, and for example, the memory in the embodiments of the present application may be static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate synchronous dynamic random access memory (double DATA RATE SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (ENHANCED SDRAM, ESDRAM), synchronous connection dynamic random access memory (SYNCH LINK DRAM, SLDRAM), direct Rambus RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.
The embodiment of the application also provides a computer readable storage medium for storing a computer program.
Optionally, the computer readable storage medium may be applied to a network device or a base station in the embodiment of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the network device or the base station in each method of the embodiment of the present application, which is not described herein for brevity.
Optionally, the computer readable storage medium may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the computer program causes a computer to execute a corresponding procedure implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, which is not described herein for brevity.
The embodiment of the application also provides a computer program product comprising computer program instructions.
Optionally, the computer program product may be applied to a network device or a base station in the embodiment of the present application, and the computer program instructions cause a computer to execute corresponding flows implemented by the network device or the base station in the methods in the embodiments of the present application, which are not described herein for brevity.
Optionally, the computer program product may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, which are not described herein for brevity.
The embodiment of the application also provides a computer program.
Optionally, the computer program may be applied to a network device or a base station in the embodiment of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the network device or the base station in each method in the embodiment of the present application, which is not described herein for brevity.
Optionally, the computer program may be applied to a mobile terminal/terminal device in the embodiment of the present application, and when the computer program runs on a computer, the computer is caused to execute corresponding processes implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein for brevity.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.
In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit 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 functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. For such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. The storage medium includes a U disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, an optical disk, or other various media capable of storing program codes.
The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.