Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be understood that the technical solutions of the embodiments of the present invention can be applied to various communication systems, for example: a Long Term Evolution (LTE) System, an LTE Frequency Division Duplex (FDD) System, an LTE Time Division Duplex (TDD) System, a Universal Mobile Telecommunications System (UMTS) or Worldwide Interoperability for Microwave Access (WiMAX) communication System, a 5G System, a New Radio (NR) System, or a subsequent Evolution communication System.
In the embodiment of the present invention, the Terminal device may include, but is not limited to, a Mobile Station (MS), a Mobile Terminal (Mobile Terminal), a Mobile phone (Mobile Telephone), a User Equipment (UE), a handset (handset), a portable device (portable Equipment), a vehicle (vehicle), etc., and the Terminal device may communicate with one or more core networks through a Radio Access Network (RAN), for example, the Terminal device may be a Mobile phone (or referred to as a "cellular" phone), a computer with a wireless communication function, and the Terminal device may also be a portable, pocket, handheld, computer-embedded, or vehicle-mounted Mobile apparatus.
As shown in fig. 1, an embodiment of the present invention provides a data transmission method 100, which may be executed by a terminal device, and includes the following steps:
s102: if the second uplink grant is received before the first data is transmitted through a Hybrid Automatic Repeat reQuest (HARQ) process corresponding to the first uplink grant (UL grant), the target data is transmitted through the HARQ process corresponding to the target uplink grant.
Wherein the target uplink grant is one of a first uplink grant and a second uplink grant; the target data is one of the first data and the second data.
In the embodiment of the present invention, the first uplink grant is used to schedule transmission of the first data, and the first data includes data in a random access process. As mentioned above, the random access includes 4-step RACH and 2-step RACH, and optionally, the first data may specifically be Msg3 in 4-step RACH; or uplink data in MsgA in 2-step RACH.
The MsgA mentioned in each embodiment of the present invention may specifically be a random access message sent by a terminal device to a network device in a 2-step RACH; the MsgB mentioned in the subsequent embodiments of the present invention may specifically be a random access response message sent by the network device to the terminal device in the 2-step RACH.
In this embodiment of the present invention, the second uplink grant is received by the terminal device in the random access process, and the second uplink grant is used to schedule data transmission other than the first data, where the data other than the first data includes the second data. Specifically, the second uplink grant may be used to schedule second data transmission, where the second data may be high-priority data, low-priority data, or the like.
Optionally, the HARQ process corresponding to the first uplink grant is the same as the HARQ process corresponding to the second uplink grant.
In an example, the target uplink grant is a first uplink grant, and the target data is first data, so that S102 may be to transmit the first data through a HARQ process corresponding to the first uplink grant, where in this example, the priority of the second uplink grant is lower than the priority of the first uplink grant, or the priority of data scheduled by the second uplink grant is lower than the priority of the first data, and the first data is scheduled by the first uplink grant. In this example, since the first data includes data in the random access process, S102 transmits the first data through the HARQ process corresponding to the first uplink grant, and by ignoring the second uplink grant, the smooth execution of the random access process is not affected.
In another example, the target uplink grant is a second uplink grant, and the target data is second data, so that S102 may be to transmit the second data through a HARQ process corresponding to the second uplink grant. In this example, the priority of the second uplink grant may be higher than the priority of the first uplink grant.
In the data transmission method provided in the embodiment of the present invention, in the random access process, if the terminal device receives the second uplink grant before transmitting the first data through the HARQ process corresponding to the first uplink grant, the terminal device transmits the first data through the HARQ process corresponding to the first uplink grant, or transmits the second data through the HARQ process corresponding to the second uplink grant, thereby solving the problem that the terminal device cannot determine how to process the received uplink grant, and simultaneously solving the problem that the HARQ process corresponding to the first uplink grant and the HARQ process corresponding to the second uplink grant is the same, which causes unnecessary HARQ cache data loss, thereby ensuring the reliability and effectiveness of data transmission.
Optionally, as an embodiment, before S102 of the above embodiment 100, the following steps may be further included: and receiving the first uplink grant, and submitting the first uplink grant and HARQ information corresponding to the first uplink grant to the HARQ entity. In a specific application, if the second uplink grant is received after the first uplink grant is received and before the first data is sent, the target data is transmitted through the HARQ corresponding to the target uplink grant.
Optionally, as an embodiment, after receiving the second uplink grant, the HARQ entity may further submit the received second uplink grant and HARQ information corresponding to the second uplink grant to the HARQ entity.
Optionally, in the step of transmitting the target data through the HARQ process corresponding to the target uplink grant mentioned in S102 in each of the above embodiments, the target uplink grant is one of the first uplink grant and the second uplink grant.
Optionally, in a case that a first preset condition is satisfied, the target uplink grant is a first uplink grant, and the first preset condition may include: the HARQ cache performed by the first uplink grant corresponding to the HARQ is non-empty; the priority of the second uplink authorization is lower than at least one of the priorities of the first uplink authorization; thus, the above embodiment may further include the steps of: ignoring the second uplink grant. In this embodiment, since the second uplink grant is ignored, the target uplink grant is the first uplink grant, and the terminal device may transmit the first data through the HARQ process corresponding to the first uplink grant. The example solves the problem of unnecessary HARQ buffer data loss caused by the same HARQ process corresponding to the first uplink grant and the second uplink grant, thereby ensuring the reliability and effectiveness of data transmission
Optionally, in this embodiment, when the first preset condition is not satisfied, the target uplink grant is a second uplink grant, and the terminal device may transmit the second data through the HARQ process corresponding to the second uplink grant.
The first preset condition is not satisfied in this embodiment, for example, the priority of the second uplink grant is higher than the priority of the first uplink grant; or, the protocol supports prioritizing different uplink grants, etc.
In this embodiment, the terminal device transmits the second data through the HARQ process corresponding to the second uplink grant, and optionally, before this, the terminal device may further obtain the second data to be transmitted from the multiplexing and assembling entity.
In the foregoing embodiment, the priority of the second uplink grant is lower than the priority of the first uplink grant, and specifically, the terminal device may obtain the priority of the second uplink grant by at least one of the following manners:
1) the second uplink grant is not received on a Physical Downlink Control Channel (PDCCH) scrambled by a target Radio Network Temporary Identity (RNTI); wherein the target RNTI is used for scheduling transmission of the second data.
2) Downlink Control Information (DCI) corresponding to a second uplink grant includes indication Information, where the indication Information indicates that a priority of the second uplink grant is lower than a priority of the first uplink grant.
Optionally, as an embodiment, before transmitting the target data through the HARQ process corresponding to the target uplink grant in S102 of the embodiment 100, the method may further include the following steps: and starting or restarting a timer associated with the HARQ process corresponding to the first uplink grant under the condition that a second preset condition is met.
The embodiment can determine that the target UL grant is the first UL grant or the second UL grant during the running period of the timer associated with the HARQ process corresponding to the first uplink grant, and therefore the reliability of the operation executed by the embodiment is improved due to the limitation condition of the timer.
Wherein the second preset condition comprises at least one of the following:
1) receiving the first uplink grant;
2) obtaining the first data from a multiplexing and assembly entity;
3) the first data is stored in the Msg3 cache;
4) and the first data is stored in an HARQ buffer of an HARQ process corresponding to the first uplink authorization.
Specifically, the time at which the timer is started or restarted may be one of the following:
1) receiving the first uplink grant;
2) the moment when the first data is obtained from the multiplexing and assembling entity;
3) the time when the first data is stored in the Msg3 cache;
4) the first data is stored at a time in the HARQ buffer of the HARQ process corresponding to the first uplink grant.
Optionally, as an embodiment, before starting or restarting the timer associated with the HARQ process corresponding to the first uplink grant in the above embodiment, the method further includes: judging whether the timer runs or not; if the timer is running, stopping the timer; and if the timer is not running, not executing the operation.
Optionally, after the target data is transmitted through the HARQ process corresponding to the target uplink grant in this embodiment, the method may further include the following steps: stopping the timer when a third preset condition is met;
wherein the third preset condition comprises at least one of:
1) the random access procedure is successfully completed;
2) during the timer running, the target uplink grant is the second uplink grant;
3) contention resolution is considered unsuccessful;
4) reporting a random access problem to a high layer;
5) the random access procedure is not successfully completed;
6) and the HARQ buffer of the HARQ process corresponding to the first uplink authorization is emptied.
The above embodiment starts or restarts the timer associated with the HARQ process corresponding to the first uplink grant, so that the determination condition that the target uplink grant is the first uplink grant or the second uplink grant may be:
1) during the running period of the timer, if a first preset condition is met, the target uplink authorization is a first uplink authorization; wherein, the embodiment may further ignore the second uplink grant. The first preset condition includes: the priority of the second uplink grant is lower than the priority of the first uplink grant.
Optionally, in this embodiment, before the terminal device transmits the first data through the HARQ process corresponding to the first uplink grant, the target timer may also be stopped.
2) During the running period of the timer, if a first preset condition is not met, the target uplink grant is the second uplink grant; the first preset condition includes: the priority of the second uplink grant is lower than the priority of the first uplink grant. This embodiment may also obtain the second data to be transmitted from a multiplexing and assembling entity.
3) Before transmitting target data through a HARQ process corresponding to a target uplink grant, if the timer is not running (e.g., stopped running), the target uplink grant is the second uplink grant.
In the foregoing embodiment, the first preset condition refers to that the priority of the second uplink grant is lower than the priority of the first uplink grant, and specifically, the terminal device may be determined by at least one of the following manners:
1) the second uplink grant is not received on the PDCCH scrambled by the target RNTI; wherein the target RNTI is used for scheduling transmission of the second data.
2) The DCI corresponding to the second uplink grant comprises indication information, and the indication information indicates that the priority of the second uplink grant is lower than that of the first uplink grant.
To describe the data transmission method provided by the above embodiments of the present invention in detail, the following description will be made in conjunction with specific embodiments executed by several terminal devices.
Embodiment one, also referred to hereafter as method 200.
S202: the UE initiates random access.
In this step, the UE may initiate a 4-step RACH on a serving cell, and receive a corresponding RAR UL grant during RAR window operation.
In this step, the UE may also initiate a 2-step RACH on a serving cell, select a UL grant (or MsgA grant) for transmitting MsgA data according to the resource configuration, and then receive the corresponding MsgA grant.
The RAR UL grant or MsgA grant received in this step corresponds to the first uplink grant (or first UL grant) in the previous embodiments.
Optionally, the first UL grant received in this step is received in MsgB in 2-step RACH, and the scenario may specifically be: and the MsgB received by the UE has no competition resolving identification, the UE backs the fallback to the 4-step RACH, and the Msg3 is sent to the network equipment.
Optionally, the first UL grant received in this step is received in a 2-step RACH, where the MsgA used for scheduling the UL grant for retransmission may specifically be: the UE does not receive the MsgB within a certain window time, and then the UE performs the 2-step RACH attempt again to receive the MsgA grant, i.e., the UL grant.
S204: the UE delivers the received first UL grant to the HARQ entity.
S206: the UE receives the second UL grant and delivers the received second UL grant to the HARQ entity.
The second UL grant in this step is the RAR UL grant received in S202 or the UL grant other than the MsgA grant received in S202, and corresponds to the second uplink grant (or called the second UL grant) in the previous embodiments.
Optionally, the UL grant may be used to schedule data transmission outside of the random access procedure. Alternatively, the UL grant may be a configured grant (configured grant).
Alternatively, the UL grant may be a dynamic scheduling grant (dynamic grant).
S208: performing an operation related to the second UL grant; or
The received second UL grant is ignored.
Optionally, in this step, in the case that the first preset condition is satisfied, the received second UL grant is ignored, and the random access procedure of S202 is continuously performed. The first preset condition includes: the priority of the UL grant received in step S206 is lower than the priority of the UL grant received in step S202.
Optionally, in this step, in case that a first preset condition is not satisfied, an operation related to the second UL grant is performed. The method specifically comprises the following steps: the priority of the UL grant received in step S206 is higher than the priority of the UL grant received in step S202; and the terminal obtains the data to be transmitted from the multiplexing and assembling entity according to the UL grant, stores the data into the HARQ cache of the HARQ process corresponding to the UL grant, and finally transmits the data through the HARQ process corresponding to the grant.
In the data transmission method provided by the embodiment of the invention, in the random access process, before the first data is transmitted through the HARQ process corresponding to the first uplink authorization, if the second uplink authorization is received, the first data is transmitted through the HARQ process corresponding to the first uplink authorization, or the second data is transmitted through the HARQ process corresponding to the second uplink authorization, so that the problem that how to process the received uplink authorization cannot be determined by the terminal equipment is solved, and meanwhile, the problem that unnecessary HARQ cache data is lost due to the fact that the HARQ processes corresponding to the first uplink authorization and the second uplink authorization are the same is solved, thereby ensuring the reliability and effectiveness of data transmission.
Embodiment two, or method 300.
S302: and receiving configuration information, wherein the configuration information is used for indicating the starting duration of the timer.
In this step, the UE may receive random access configuration information broadcasted by the network device side, where the configuration information at least includes timer start duration information.
S304: the UE initiates random access.
In this step, the UE may initiate a 4-step RACH on a serving cell, and receive a corresponding RAR UL grant during RAR window operation.
In this step, the UE may also initiate a 2-step RACH on a serving cell, and the UE selects one MsgA grant according to the resource configuration, and then receives the corresponding MsgA grant.
The RAR UL grant or MsgA grant received in this step corresponds to the first uplink grant in the previous embodiments.
Optionally, the first UL grant received in this step is received in MsgB in 2-step RACH, and the scenario may specifically be: and the MsgB received by the UE has no competition resolving identification, the UE backs the fallback to the 4-step RACH, and the Msg3 is sent to the network equipment.
Optionally, the first UL grant received in this step is received in a 2-step RACH, where the MsgA used for scheduling the UL grant for retransmission may specifically be: the UE does not receive the MsgB within a certain window time, and then the UE performs the 2-step RACH attempt again to receive the MsgA grant, i.e., the UL grant.
S306: the timer is started according to predefined rules.
Wherein the predefined rule includes at least one of:
1) receiving a first uplink grant, for example, receiving a RAR UL grant or a MsgA grant in step S304;
2) obtaining first data from the multiplexing and assembling entity, wherein the first data can be specifically Msg3 in 4-step RACH; or is uplink data in MsgA in 2-step RACH;
3) the first data is stored in the Msg3 cache;
4) and the first data is stored in an HARQ buffer of an HARQ process corresponding to the first uplink authorization.
S308: the UE delivers the received first UL grant to the HARQ entity.
S310: the UE receives the second UL grant and delivers the received second UL grant to the HARQ entity.
The second UL grant in this step is the RAR UL grant received in S304 or the UL grant other than the msggagrant received in S304, and corresponds to the second uplink grant in the foregoing embodiments.
Alternatively, the UL grant may be for scheduling data transmission outside of the random access procedure.
Alternatively, the UL grant may be a configured grant (configured grant).
Alternatively, the UL grant may be a dynamic scheduling grant (dynamic grant).
S312: performing an operation related to the second UL grant; or
The received second UL grant is ignored.
Optionally, in this step, during the running of the timer, in the case that the first preset condition is met, the received second UL grant is ignored, and the random access procedure of S304 is continuously executed. The first preset condition includes: the priority of the UL grant received in step S310 is lower than the priority of the UL grant received in step S304.
Optionally, in this step, during the running of the timer, in case that a first preset condition is not satisfied, an operation related to the second UL grant is performed. The method specifically comprises the following steps: the priority of the UL grant received in step S310 is higher than the priority of the UL grant received in step S304; and the terminal obtains the data to be transmitted from the multiplexing and assembling entity according to the second UL grant, stores the data into the HARQ cache of the HARQ process corresponding to the second UL grant, and finally transmits the data through the HARQ process corresponding to the grant.
Alternatively, in this step, in a case where the timer is not running (stopped running), an operation related to the UL grant is directly performed. The method specifically comprises the following steps: and the terminal obtains the data to be transmitted from the multiplexing and assembling entity according to the second UL grant, stores the data into the HARQ buffer of the HARQ process corresponding to the second UL grant, and finally transmits the data through the HARQ process corresponding to the second UL grant.
S314: the timer is stopped.
If the operation of the target timer is not stopped at the time when the timer is still running under the execution of the above-described respective conditions, this step stops the target timer.
Optionally, this step may stop the timer if a third preset condition is met, where the third preset condition includes at least one of:
the random access procedure is successfully completed;
during the timer running, the target uplink grant is the second uplink grant;
contention resolution is considered unsuccessful;
reporting a random access problem to a high layer;
the random access procedure is not successfully completed;
and the HARQ buffer of the HARQ process corresponding to the first uplink authorization is emptied.
In the data transmission method provided by the embodiment of the invention, in the random access process, before the first data is transmitted through the HARQ process corresponding to the first uplink authorization, if the second uplink authorization is received, the first data is transmitted through the HARQ process corresponding to the first uplink authorization, or the second data is transmitted through the HARQ process corresponding to the second uplink authorization, so that the problem that how to process the received uplink authorization cannot be determined by the terminal equipment is solved, and meanwhile, the problem that unnecessary HARQ cache data is lost due to the fact that the HARQ processes corresponding to the first uplink authorization and the second uplink authorization are the same is solved, thereby ensuring the reliability and effectiveness of data transmission.
The data transmission method according to the embodiment of the present invention is described in detail above with reference to fig. 1 to 3. A terminal device according to an embodiment of the present invention will be described in detail below with reference to fig. 4.
Fig. 4 is a schematic structural diagram of a terminal device according to an embodiment of the present invention. As shown in fig. 4, the terminal device 400 includes: a transmission module 402 for
If a second uplink grant is received before the first data is transmitted through the HARQ process corresponding to the first uplink grant, transmitting target data through the HARQ process corresponding to the target uplink grant;
wherein the target uplink grant is one of the first uplink grant and the second uplink grant; the target data is one of first data and second data; the first uplink grant is used for scheduling transmission of the first data, and the first data comprises data in a random access process; the second uplink grant is used for scheduling data transmission except the first data, and the data except the first data comprises the second data.
In the embodiment of the invention, in the random access process, if the terminal equipment receives the second uplink authorization before the first data is transmitted through the HARQ process corresponding to the first uplink authorization, or the second data is transmitted through the HARQ process corresponding to the second uplink authorization, so that the problem of unnecessary HARQ cache data loss caused by the fact that the HARQ processes corresponding to the first uplink authorization and the second uplink authorization are the same is solved, and the reliability and the effectiveness of data transmission are ensured.
Optionally, as an embodiment, the HARQ process corresponding to the first uplink grant is the same as the HARQ process corresponding to the second uplink grant.
Optionally, as an embodiment, before receiving the second uplink grant, the transmission module 402 is further configured to transmit the second uplink grant to the ue
Receiving the first uplink grant;
and submitting the first uplink grant and HARQ information corresponding to the first uplink grant to a HARQ entity.
Optionally, as an embodiment, before receiving the second uplink grant, the transmission module 402 is further configured to transmit the second uplink grant to the ue
And submitting the second uplink grant and the HARQ information corresponding to the second uplink grant to the HARQ entity.
Optionally, as an embodiment, in a case that a first preset condition is met, the target uplink grant is the first uplink grant;
wherein the transmission module 402 is further configured to: ignoring the second uplink grant;
the first preset condition includes: the priority of the second uplink grant is lower than the priority of the first uplink grant.
Optionally, as an embodiment, in a case that a first preset condition is not satisfied, the target uplink grant is the second uplink grant;
the first preset condition includes: the priority of the second uplink grant is lower than the priority of the first uplink grant.
Optionally, as an embodiment, the transmission module 402 is further configured to
Obtaining the second data to be transmitted from a multiplexing and assembling entity.
Optionally, as an embodiment, the priority of the second uplink grant is lower than the priority of the first uplink grant by at least one of:
the second uplink authorization is not received on a Physical Downlink Control Channel (PDCCH) scrambled by a target Radio Network Temporary Identifier (RNTI); wherein the target RNTI is used for scheduling transmission of the second data;
the downlink control information DCI corresponding to the second uplink grant includes indication information, where the indication information indicates that the priority of the second uplink grant is lower than the priority of the first uplink grant.
Optionally, as an embodiment, the terminal device 400 further includes: a timer processing module for
Under the condition that a second preset condition is met, starting or restarting a timer associated with the HARQ process corresponding to the first uplink grant;
wherein the second preset condition comprises at least one of:
receiving the first uplink grant;
obtaining the first data from a multiplexing and assembly entity;
the first data is stored in the Msg3 cache;
and the first data is stored in an HARQ buffer of an HARQ process corresponding to the first uplink authorization.
Optionally, as an embodiment, the terminal device 400 further includes: a timer processing module, configured to determine whether a timer associated with a HARQ process corresponding to the first uplink grant is running before starting or restarting the timer; and if the timer is running, stopping the timer.
Optionally, as an embodiment, during the running of the timer, if a first preset condition is met, the target uplink grant is the first uplink grant;
wherein the transmission module 402 is further configured to: ignoring the second uplink grant;
the first preset condition includes: the priority of the second uplink grant is lower than the priority of the first uplink grant.
Optionally, as an embodiment, during the running of the timer, if a first preset condition is not met, the target uplink grant is the second uplink grant;
the first preset condition includes: the priority of the second uplink grant is lower than the priority of the first uplink grant.
Optionally, as an embodiment, the transmission module 402 is further configured to
Obtaining the second data to be transmitted from a multiplexing and assembling entity.
Optionally, as an embodiment, the terminal device 400 further includes: and the timer processing module is used for stopping the timer.
Optionally, as an embodiment, in a case that the timer is not running, the target uplink grant is the second uplink grant.
Optionally, as an embodiment, the priority of the second uplink grant is lower than the priority of the first uplink grant by at least one of:
the second uplink grant is not received on a PDCCH scrambled by a target RNTI; wherein the target RNTI is used for scheduling transmission of the second data;
the DCI corresponding to the second uplink grant comprises indication information, and the indication information indicates that the priority of the second uplink grant is lower than that of the first uplink grant.
Optionally, as an embodiment, the terminal device 400 further includes: the timer processing module is used for stopping the timer under the condition that a third preset condition is met;
wherein the third preset condition comprises at least one of:
the random access procedure is successfully completed;
during the timer running, the target uplink grant is the second uplink grant;
contention resolution is considered unsuccessful;
reporting a random access problem to a high layer;
the random access procedure is not successfully completed;
and the HARQ buffer of the HARQ process corresponding to the first uplink authorization is emptied.
The terminal device 400 according to the embodiment of the present invention may refer to the flows corresponding to the methods 100 to 300 according to the embodiment of the present invention, and each unit/module and the other operations and/or functions described above in the terminal device 400 are respectively for implementing the corresponding flows in the methods 100 to 300, and can achieve the same or equivalent technical effects, and are not described herein again for brevity.
Fig. 5 is a block diagram of a terminal device of another embodiment of the present invention. The terminal device 500 shown in fig. 5 includes: at least one processor 501, memory 502, at least one network interface 504, and a user interface 503. The various components in the terminal device 500 are coupled together by a bus system 505. It is understood that the bus system 505 is used to enable connection communications between these components. The bus system 505 includes a power bus, a control bus, and a status signal bus in addition to a data bus. For clarity of illustration, however, the various buses are labeled as bus system 505 in FIG. 5.
The user interface 503 may include, among other things, a display, a keyboard, or a pointing device (e.g., a mouse, trackball, touch pad, or touch screen, among others.
It is to be understood that the memory 502 in embodiments of the present invention may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of illustration and not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic random access memory (ddr Data Rate SDRAM, ddr SDRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memory 502 of the subject systems and methods described in connection with the embodiments of the invention is intended to comprise, without being limited to, these and any other suitable types of memory.
In some embodiments, memory 502 stores elements, executable modules or data structures, or a subset thereof, or an expanded set thereof as follows: an operating system 5021 and application programs 5022.
The operating system 5021 includes various system programs, such as a framework layer, a core library layer, a driver layer, and the like, and is used for implementing various basic services and processing hardware-based tasks. The application 5022 includes various applications, such as a Media Player (Media Player), a Browser (Browser), and the like, for implementing various application services. The program for implementing the method according to the embodiment of the present invention may be included in the application program 5022.
In this embodiment of the present invention, the terminal device 500 further includes: a computer program stored on the memory 502 and executable on the processor 501, the computer program, when executed by the processor 501, implementing the steps of the methods 100 to 300 as follows.
The method disclosed by the above-mentioned embodiments of the present invention may be applied to the processor 501, or implemented by the processor 501. The processor 501 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 501. The Processor 501 may be a general-purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components. The various methods, steps and logic blocks disclosed in the embodiments of the present invention 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 invention may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules may reside in ram, flash memory, rom, prom, or eprom, registers, among other computer-readable storage media known in the art. The computer readable storage medium is located in the memory 502, and the processor 501 reads the information in the memory 502 and performs the steps of the above method in combination with the hardware thereof. In particular, the computer readable storage medium has stored thereon a computer program which, when executed by the processor 501, implements the steps of the embodiments of the methods 100 to 300 as described above.
It is to be understood that the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or any combination thereof. For a hardware implementation, the Processing units may be implemented within one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), general purpose processors, controllers, micro-controllers, microprocessors, other electronic units configured to perform the functions described herein, or a combination thereof.
For a software implementation, the techniques described in this disclosure may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described in this disclosure. The software codes may be stored in a memory and executed by a processor. The memory may be implemented within the processor or external to the processor.
The terminal device 500 can implement the processes implemented by the terminal device in the foregoing embodiments, and in order to avoid repetition, the descriptions are omitted here.
An embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements the processes of method embodiments 100 to 300, and can achieve the same technical effects, and in order to avoid repetition, the computer program is not described herein again. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.