WO2015043319A1 - Recording method, recording device, playing method and playing device - Google Patents
Recording method, recording device, playing method and playing device Download PDFInfo
- Publication number
- WO2015043319A1 WO2015043319A1 PCT/CN2014/083841 CN2014083841W WO2015043319A1 WO 2015043319 A1 WO2015043319 A1 WO 2015043319A1 CN 2014083841 W CN2014083841 W CN 2014083841W WO 2015043319 A1 WO2015043319 A1 WO 2015043319A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- recording
- session
- audio session
- playing
- module
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
- G11B27/00—Editing; Indexing; Addressing; Timing or synchronising; Monitoring; Measuring tape travel
- G11B27/02—Editing, e.g. varying the order of information signals recorded on, or reproduced from, record carriers
- G11B27/031—Electronic editing of digitised analogue information signals, e.g. audio or video signals
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
- G11B20/00—Signal processing not specific to the method of recording or reproducing; Circuits therefor
- G11B20/10—Digital recording or reproducing
- G11B20/10527—Audio or video recording; Data buffering arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
Definitions
- the present disclosure relates to a field of mobile terminal, and more particularly, to a recording method, a recording device, a playing method and a playing device.
- an application with a recording function may be configured as "Required background modes", so that the application may run in the background and perform recording.
- examples of the present disclosure may provide a recording method, a recording device, a playing method and a playing device.
- the technical scheme may be as follows.
- An example may provide a recording method, including:
- Another example may provide a recording device, including:
- a recovery notification receiving module to receive a recovery notification and obtain that an audio session is released according to the recovery notification
- a session configuration module to configure a category of the audio session as playing and recording and configure an attribute of the audio session as MixWithOthers
- a session obtaining module to obtain the audio session
- a session re-configuring module to configure the category of the audio session as recording and perform the recording in a background.
- Another example may provide a playing method, including:
- configuring a category of the audio session as playing and recording configuring an attribute of the audio session as MixWithOthers; obtaining the audio session;
- Another example may provide a playing device, including:
- a recovery notification receiving module to receive a recovery notification and obtain that an audio session is released according to the recovery notification
- a session configuration module to configure a category of the audio session as playing and recording and configure an attribute of the audio session as
- a session obtaining module to obtain the audio session
- a session re-configuring module to configure the category of the audio session as playing and perform the playing in a background.
- the category of the audio session may be configured as the playing and recording and the attribute of the audio session may be configured as the MixWithOthers to obtain the audio session.
- the category of the audio session may be configured as recording and the recording may be re-performed in the background.
- FIG. 1 is a flow chart illustrating a recording method in accordance with an example of the present disclosure
- Figure 2 is a flow chart illustrating another recording method in accordance with an example of the present disclosure
- Figure 3 is a schematic diagram illustrating structure of a recording device in accordance with an example of the present disclosure
- Figure 4 is a schematic diagram illustrating structure of another recording device in accordance with an example of the present disclosure
- Figure 5 is a flow chart illustrating a playing method in accordance with an example of the present disclosure
- Figure 6 is a schematic diagram illustrating structure of a playing device in accordance with an example of the present disclosure.
- Figure 7 is a schematic diagram illustrating structure of another recording device in accordance with an example of the present disclosure.
- Figure 8 is a schematic diagram illustrating structure of another playing device in accordance with an example of the present disclosure. DETAILED DESCRIPTION
- the present disclosure is described by referring mainly to example(s) thereof.
- numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. It will be readily apparent however, that the present disclosure may be practiced without limitation to these specific details. In other instances, some methods and structures have not been described in detail so as not to unnecessarily obscure the present disclosure.
- the term “includes” means includes but not limited to, the term “including” means including but not limited to.
- the term “based on” means based at least in part on.
- the terms "a” and “an” are intended to denote at least one of a particular element.
- the application performing the recording in the background may stop recording. Since the phone application and an application running in a foreground have a higher priority, the iOS system may send a global notification to applications performing the recording in the background to inform a phone event or music playing event. Accordingly, the applications performing the recording in the background may stop recording and release an audio session.
- the audio session may be a session for playing audio and recording in the iOS system. All phone, music playing or recording applications may need to obtain the audio session to make a phone, play the audio or perform the recording. When all phone, music playing or recording applications using the audio session stop or suspend, the audio session may be released.
- the application performing the recording in the background may be interrupted by the phone application or the music playing application, when the phone application or the music playing application is closed, the application, which has stopped recording in the background, cannot automatically obtain the audio session and the application performing the recording in the background cannot automatically restart and continue to perform the recording. Since the recording operation may be interrupted by each phone operation or music playing operation, requirement of the application, which may need to keep recording in the background, cannot be satisfied.
- a system may send a notification to the first application to inform the first application that the second application may have stopped running and the audio session may be re-obtained.
- An example of the present disclosure may provide a technical scheme for continuing to perform the recording after the first application performing the recording in the background is interrupted by the second application with a higher priority. The present disclosure may be described and introduced hereinafter in detail in accordance with several examples.
- figure 1 is a flow chart illustrating a recording method in accordance with an example of the present disclosure.
- the recording method may be applied to an electronic device.
- the recording method may include following blocks.
- a recovery notification may be received.
- the recovery notification may be used for informing a first application, which may suspend recording in the background, that an audio session may have been released by a second application with a higher priority.
- a category of the audio session may be configured as playing and recording and an attribute of the audio session may be configured as MixWithOthers.
- the audio session may be obtained.
- the category of the audio session may be configured as recording and the recording may be performed in a background.
- the category of the audio session may be configured as the playing and recording and the attribute of the audio session may be configured as the MixWithOthers to obtaining the audio session.
- the category of the audio session may be configured as recording and the recording may be re-performed in the background.
- the problem that the recording cannot automatically re-start after the application performing the recording in the background is interrupted by the phone application or the music playing application may be solved.
- An effect that the first application performing the recording in the background may automatically re-start after the first application is interrupted by the second application with the higher priority may be achieved.
- the above mentioned electronic device may be an iOS electronic device.
- the electronic device may be a mobile phone, a tablet PC or a portable mobile device. This kind of device may be called an iDevice including the electronic device launched by Apple.
- the first letter of the name of the electronic device may be "i".
- figure 2 is a flow chart of another recording method in accordance with an example of the present disclosure.
- the recording method may be applied to an electronic device.
- the recording method may include following blocks.
- a code may be configured in an Operating System (OS) or a first application.
- the code may be used for configuring a category and attribute of an audio session after a recovery notification is received by the first application.
- the code may be used for configuring the category and attribute of the audio session after the first application receives the recovery notification.
- the code may be compiled into a static database and added to the OS or the first application. Alternatively, a module including the code may be directly added to the OS or the first application. [0034] In block 202, a suspend notification may be received. The suspend notification may be used for informing the first application performing the recording in a background that a second application with the higher priority may occupy the audio session.
- the first application performing the recording in the background may receive the suspend notification from the OS.
- the suspend notification may be used for informing the first application performing the recording in the background that the second application with the higher priority may need to use the audio session.
- the second application with the higher priority may be a phone application or an application running in a foreground.
- the audio session may be a session for managing playing of the audio and recording. All applications which need to play the audio or perform the recording may play the audio or perform the recording after obtaining the audio session. When the application playing the audio or performing the recording is suspended or stopped, the audio session may be released.
- the recording may be suspended, the audio session may be released and the second application with the higher priority may use the audio session.
- the system may send the suspend notification to the first application performing the recording in the background to inform the first application that the second application with the higher priority may need to use the audio session.
- the first application performing the recording in the background may suspend recording and release the audio session.
- the system may inform the first application performing the recording in the background to suspend the recording and inform the first application that the phone application may need to use the audio session.
- the first application may suspend the recording and release the audio session.
- a recovery notification may be received. The recovery notification may be used for informing the first application which may suspend performing the recording in the background that the audio session may have been released by the second application with the higher priority.
- the first application which may suspend performing the recording in the background may receive the recovery notification.
- the recovery notification may be used for informing the first application which may suspend performing the recording in the background that the audio session may have been released by the second application with the higher priority.
- the system may send the recovery notification to the first application, which may suspend the recording in the background, to inform the first application that the audio session may be released.
- the audio session may be re-obtained and the recording may be restarted.
- a category of the audio session may be configured as playing and recording and an attribute of the audio session may be configured as MixWithOthers.
- the first application may re-obtain the audio session.
- the audio session may be re-obtained.
- the first application which may suspend the recording in the background, may re-obtain the audio session.
- the category of the audio session may be configured as the recording, and the recording may be performed in the background.
- the attribute of audio session may be Not-MixWithOthers in default.
- the attribute of the audio session cannot be configured as MixWithOthers. Therefore, if the category of the audio session is configured as recording, the attribute of MixWithOthers may be invalid, which may ensure that the first application performing the recording in the background may not affect normal playing performed by the mobile terminal, such as a ringtone or a text tone.
- the first application performing the recording in the background is interrupted by the second application with the higher priority, blocks 204 to 207 may be repeated to continue to perform the recording in the background.
- the category of the audio session may be configured as playing and recording and the attribute of the audio session may be configured as MixWithOthers to re-obtain the audio session.
- the category of the audio session may be configured as recording and the recording may restart in the background.
- the problem that the recording cannot automatically re-start after the first application performing the recording in the background is interrupted by the phone application or the music playing application may be solved.
- An effect that the first application performing the recording in the background may automatically re-start after the first application is interrupted by the second application with the higher priority may be achieved.
- the code for configuring the category and attribute of the audio session may be configured in the OS or the first application, by which the application, which may suspend the recording in the background, may re-obtain the audio session to continue to perform the recording in the background.
- Examples of the devices for executing the recording methods in examples of the present disclosure may be described hereinafter. Refer to the examples of the recording methods of the present disclosure for those details, which may not be disclosed in examples of the recording devices of the present disclosure.
- figure 3 is a schematic diagram illustrating structure of a recording device in accordance with an example of the present disclosure.
- the recording device may be implemented with software, hardware or combination thereof and may be an electronic device or partial of an electronic device.
- the electronic device may include a mobile phone, tablet PC or a portable mobile device.
- the recording device may include: a recovery notification receiving module 310, a session configuration module 320, a session obtaining module 330 and a session re-configuring module 340.
- the recovery notification receiving module 310 may be configured to receive a recovery notification and obtain that an audio session is released according to the recovery notification.
- the recovery notification may be used for informing a first application, which may suspend performing recording in the background that the audio session may be released by a second application with a higher priority.
- the session configuration module 320 may be configured to configure a category of the audio session as playing and recording and configure an attribute of the audio session as MixWithOthers.
- the session obtaining module 330 may be configured to obtain the audio session.
- the session re-configuring module 340 may be configured to configure the category of the audio session as recording and perform the recording in a background.
- the category of the audio session may be configured as the playing and recording and the attribute of the audio session may be configured as the MixWithOthers.
- the category of the audio session may be configured as recording and the recording may be re-performed in the background.
- the problem that the recording cannot automatically re-start after the application performing the recording in the background is interrupted by the phone application or the music playing application may be solved.
- An effect that the first application performing the recording in the background may automatically re-start after the first application is interrupted by the second application with the higher priority may be achieved.
- FIG 4 is a schematic diagram illustrating structure of another recording device in accordance with an example of the present disclosure.
- the recording device may be implemented with software, hardware or combination thereof and may be an electronic device or partial of an electronic device.
- the electronic device may include a mobile phone, tablet PC or a portable mobile device.
- the recording device may include: a suspend notification receiving module 301 , a session releasing module 302, a recovery notification receiving module 310, a code configuration module 311 , a session configuration module 320, a session obtaining module 330 and a session re-configuring module 340.
- the suspend notification receiving module 301 may be configured to receive a suspend notification.
- the suspend notification may be used for informing a first application performing recording in a background that a second application with a higher priority may need to use an audio session.
- the session releasing module 302 may be configured to suspend the recording according to the suspend notification and release the audio session, so that the second application with the higher priority may occupy the audio session.
- the recovery notification receiving module 310 may be configured to receive a recovery notification and obtain that the audio session is released according to the recovery notification.
- the recovery notification may be used for informing the first application, which may suspend performing the recording in the background that the audio session may be released by the second application with a higher priority.
- the code configuration module 311 may be configured to configure a code in an Operating System (OS).
- OS Operating System
- the code may be used for configuring the category and attribute of the audio session after the first application receives the recovery notification.
- the code may be configured in the first application.
- the code may be used for configuring the category and attribute of the audio session after the first application receives the recovery notification.
- the session configuration module 320 may be configured to configure a category of the audio session as playing and recording and configure an attribute of the audio session as MixWithOthers.
- the session obtaining module 330 may be configured to obtain the audio session.
- the session re-configuring module 340 may be configured to configure the category of the audio session as recording and perform the recording in a background.
- the suspend notification receiving module 301 , session releasing module 302, recovery notification receiving module 310, code configuration module 311 , session configuration module 320, session obtaining module 330 and session re-configuring module 340 may be software modules, e.g., sets of machine readable instructions, stored in a hardware memory device.
- the suspend notification receiving module 301 , session releasing module 302, recovery notification receiving module 310, code configuration module 311 , session configuration module 320, session obtaining module 330 and session re-configuring module 340 may be hardware modules on a hardware device.
- the suspend notification receiving module 301 , session releasing module 302, recovery notification receiving module 310, code configuration module 311 , session configuration module 320, session obtaining module 330 and session re-configuring module 340 may include a combination of software and hardware modules.
- the category of the audio session may be configured as playing and recording and the attribute of the audio session may be configured as MixWithOthers to re-obtain the audio session.
- the category of the audio session may be configured as recording and the recording operation may restart in the background.
- the problem that the recording cannot automatically re-start after the first application performing the recording in the background is interrupted by the phone application or the music playing application may be solved.
- An effect that the first application performing the recording in the background may automatically re-start after the first application is interrupted by the second application with the higher priority may be achieved.
- the code for configuring the category and attribute of the audio session may be configured in the OS or the first application, by which the application, which may suspend the recording in the background, may re-obtain the audio session to continue to perform the recording in the background.
- figure 5 is a flow chart illustrating a playing method in accordance with an example of the present disclosure.
- the playing method may include following blocks.
- a recovery notification may be received. It may be obtained that an audio session may be released according to the recovery notification.
- a category of the audio session may be configured as playing and recording.
- an attribute of the audio session may be configured as MixWithOthers.
- the audio session may be obtained.
- the category of the audio session may be configured as playing.
- a playing operation may be performed in a background.
- a suspend notification may be received, the playing operation may be suspended according to the suspend notification and the audio session may be released.
- a code may be configured in an OS.
- the category of the audio session may be configured as the playing and recording according to the code and the attribute of the audio session may be configured as the MixWithOthers according to the code.
- FIG 6 is a schematic diagram illustrating structure of a playing device in accordance with an example of the present disclosure.
- the playing device may include: a recovery notification receiving module 601 , a session configuration module 602, a session obtaining module 603 and a session re-configuring module 604.
- the recovery notification receiving module 601 may be configured to receive a recovery notification and obtain that an audio session is released according to the recovery notification.
- the session configuration module 602 may be configured to configure a category of the audio session as playing and recording and configure an attribute of the audio session as MixWithOthers.
- the session obtaining module 603 may be configured to obtain the audio session.
- the session re-configuring module 604 may be configured to configure the category of the audio session as playing and perform the playing in a background.
- the playing device may further include: a suspend notification receiving module 605, configured to receive a suspend notification.
- the playing device may further include: a session releasing module 606, configured to suspend the playing according to the suspend notification and release the audio session.
- the playing device may further include: a code configuration module 607, to configure a code in an Operating System (OS), configure the category of the audio session as the playing and recording according to the code and configure the attribute of the audio session as the MixWithOthers according to the code.
- OS Operating System
- the recovery notification receiving module 601 , session configuration module 602, session obtaining module 603, session re-configuring module 604, suspend notification receiving module 605, session releasing module 606 and code configuration module 607 may be software modules, e.g., sets of machine readable instructions, stored in a hardware memory device.
- the recovery notification receiving module 601 , session configuration module 602, session obtaining module 603, session re-configuring module 604, suspend notification receiving module 605, session releasing module 606 and code configuration module 607 may be hardware modules on a hardware device.
- the recovery notification receiving module 601 , session configuration module 602, session obtaining module 603, session re-configuring module 604, suspend notification receiving module 605, session releasing module 606 and code configuration module 607 may include a combination of software and hardware modules.
- figure 7 is a schematic diagram illustrating structure of another recording device in accordance with an example of the present disclosure.
- the recording device may include: a storage medium 701 , a processor 702, a bus 703, peripherals 704, a database 705 and a communication module 706.
- the storage medium 701 , processor 702, peripherals 704, database 705 and communication module 706 may connect with the bus 703.
- the storage medium 701 may store the recovery notification receiving module 310, session configuration module 320, session obtaining module 330 and session re-configuring module 340.
- the storage medium 701 may further store the suspend notification receiving module 301 , session releasing module 302 and code configuration module 311 .
- the processor 702 may include any appropriate processor or processors. Further, processor 702 can include multiple cores for multi-thread or parallel processing.
- Storage medium 701 may include memory modules, such as Read-only memory (ROM), Random Access Memory (RAM), flash memory modules, and erasable and rewritable memory, and mass storages, such as CD-ROM, U-disk, and hard disk, etc.
- the processor 702 may communicate with the storage medium 701 and execute above operations performed by the suspend notification receiving module 301 , session releasing module 302, recovery notification receiving module 310, code configuration module 311 , session configuration module 320, session obtaining module 330 and session re-configuring module 340.
- peripherals 704 may include I/O devices such as a keyboard and mouse, and communication module 706 may include network devices for establishing connections through the communication network.
- Database 705 may include one or more databases for storing certain data and for performing certain operations on the stored data, such as database searching.
- the suspend notification receiving module 301 , session releasing module 302, recovery notification receiving module 310, code configuration module 311 , session configuration module 320, session obtaining module 330 and session re-configuring module 340 may be machine readable instructions.
- the storage medium 701 may be a non-transitory computer readable storage medium.
- figure 8 is a schematic diagram illustrating structure of another playing device in accordance with an example of the present disclosure.
- the playing device may include: a storage medium 801 , a processor 802, a bus 803, peripherals 804, a database 805 and a communication module 806.
- the storage medium 801 , processor 802, peripherals 804, database 805 and communication module 806 may connect with the bus 803.
- the storage medium 801 may store the recovery notification receiving module 601 , session configuration module 602, session obtaining module 603 and session re-configuring module 604.
- the storage medium 801 may further store the suspend notification receiving module 605, session releasing module 606 and code configuration module 607.
- the processor 802 may include any appropriate processor or processors. Further, processor 802 can include multiple cores for multi-thread or parallel processing.
- Storage medium 801 may include memory modules, such as Read-only memory (ROM), Random Access Memory (RAM), flash memory modules, and erasable and rewritable memory, and mass storages, such as CD-ROM, U-disk, and hard disk, etc.
- the processor 802 may communicate with the storage medium 801 and execute above operations performed by the recovery notification receiving module 601 , session configuration module 602, session obtaining module 603, session re-configuring module 604, suspend notification receiving module 605, session releasing module 606 and code configuration module 607.
- peripherals 804 may include I/O devices such as a keyboard and mouse, and communication module 806 may include network devices for establishing connections through the communication network.
- Database 805 may include one or more databases for storing certain data and for performing certain operations on the stored data, such as database searching.
- the recovery notification receiving module 601 , session configuration module 602, session obtaining module 603, session re-configuring module 604, suspend notification receiving module 605, session releasing module 606 and code configuration module 607 may be machine readable instructions.
- the storage medium 801 may be a non-transitory computer readable storage medium.
- a hardware module may be implemented mechanically or electronically.
- a hardware module may comprise dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC)) to perform certain operations.
- FPGA field programmable gate array
- ASIC application-specific integrated circuit
- a hardware module may also comprise programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. It will be appreciated that the decision to implement a hardware module mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.
Landscapes
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Telephone Function (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
- Management Or Editing Of Information On Record Carriers (AREA)
Abstract
An example of the present disclosure may provide a recording method. A recovery notification may be received. It may be obtained that an audio session may be released according to the recovery notification. A category of the audio session may be configured as playing and recording. An attribute of the audio session may be configured as MixWithOthers. The audio session may be obtained. The category of the audio session may be configured as recording and the recording may be performed in the background.
Description
RECORDING METHOD, RECORDING DEVICE, PLAYING METHOD AND
PLAYING DEVICE
This application claims the benefit of priority from Chinese Patent Application, No. 201310443450.3, entitled "Recording method, apparatus and electronic device" and filed on September 26, 2013, the entire content of which is hereby incorporated by reference.
FIELD OF THE INVENTION
[0001] The present disclosure relates to a field of mobile terminal, and more particularly, to a recording method, a recording device, a playing method and a playing device.
BACKGROUND
[0002] In the present iOS system, an application with a recording function may be configured as "Required background modes", so that the application may run in the background and perform recording.
SUMMARY
[0003] In order to solve a problem that a recording operation cannot automatically re-start after an application performing the recording operation in a background is interrupted by a phone application or a music playing application, examples of the present disclosure may provide a recording method, a recording device, a playing method and a playing device. The technical scheme may be as follows.
[0004] An example may provide a recording method, including:
receiving a recovery notification;
obtaining that an audio session is released according to the recovery notification;
configuring a category of the audio session as playing and recording;
configuring an attribute of the audio session as MixWithOthers;
obtaining the audio session;
configuring the category of the audio session as recording; and
performing the recording in a background.
[0005] Another example may provide a recording device, including:
a recovery notification receiving module, to receive a recovery notification and obtain that an audio session is released according to the recovery notification;
a session configuration module, to configure a category of the audio session as playing and recording and configure an attribute of the audio session as MixWithOthers;
a session obtaining module, to obtain the audio session; and
a session re-configuring module, to configure the category of the audio session as recording and perform the recording in a background.
[0006] Another example may provide a playing method, including:
receiving a recovery notification;
obtaining that an audio session is released according to the recovery notification;
configuring a category of the audio session as playing and recording;
configuring an attribute of the audio session as MixWithOthers; obtaining the audio session;
configuring the category of the audio session as playing; and
performing the playing in a background. [0007] Another example may provide a playing device, including:
a recovery notification receiving module, to receive a recovery notification and obtain that an audio session is released according to the recovery notification;
a session configuration module, to configure a category of the audio session as playing and recording and configure an attribute of the audio session as
MixWithOthers;
a session obtaining module, to obtain the audio session; and
a session re-configuring module, to configure the category of the audio session as playing and perform the playing in a background. [0008] After the recovery notification is received, the category of the audio session may be configured as the playing and recording and the attribute of the audio session may be configured as the MixWithOthers to obtain the audio session. After the audio session is obtained, the category of the audio session may be configured as recording and the recording may be re-performed in the background. With the example of the present disclosure, a problem that the recording cannot automatically re-start after an application performing the recording in a background is interrupted by a phone application or a music playing application may be solved.
BRIEF DESCRIPTION OF THE DRAWINGS [0009] In order to clearly describe the technical scheme in the present disclosure, a brief description is given to accompanying figures used in following examples. Obviously, the accompanying figures described hereinafter are some examples in the present disclosure. An ordinary skilled in the art may obtain other figures with these accompanying figures without creative work. [0010] Figure 1 is a flow chart illustrating a recording method in accordance with an example of the present disclosure;
[0011] Figure 2 is a flow chart illustrating another recording method in accordance with an example of the present disclosure;
[0012] Figure 3 is a schematic diagram illustrating structure of a recording device in accordance with an example of the present disclosure; [0013] Figure 4 is a schematic diagram illustrating structure of another recording device in accordance with an example of the present disclosure;
[0014] Figure 5 is a flow chart illustrating a playing method in accordance with an example of the present disclosure;
[0015] Figure 6 is a schematic diagram illustrating structure of a playing device in accordance with an example of the present disclosure;
[0016] Figure 7 is a schematic diagram illustrating structure of another recording device in accordance with an example of the present disclosure; and
[0017] Figure 8 is a schematic diagram illustrating structure of another playing device in accordance with an example of the present disclosure. DETAILED DESCRIPTION
[0018] For simplicity and illustrative purposes, the present disclosure is described by referring mainly to example(s) thereof. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. It will be readily apparent however, that the present disclosure may be practiced without limitation to these specific details. In other instances, some methods and structures have not been described in detail so as not to unnecessarily obscure the present disclosure. As used throughout the present disclosure, the term "includes" means includes but not limited to, the term "including" means including but not limited to. The term "based on" means based at least in part on. In addition, the terms "a" and "an" are intended to denote at least one of a particular element.
[0019] When an application with a recording function runs in the background and a phone application or a music playing application is used, the application performing the recording in the background may stop recording. Since the phone application and an application running in a foreground have a higher priority, the
iOS system may send a global notification to applications performing the recording in the background to inform a phone event or music playing event. Accordingly, the applications performing the recording in the background may stop recording and release an audio session. The audio session may be a session for playing audio and recording in the iOS system. All phone, music playing or recording applications may need to obtain the audio session to make a phone, play the audio or perform the recording. When all phone, music playing or recording applications using the audio session stop or suspend, the audio session may be released. [0020] Since the application performing the recording in the background may be interrupted by the phone application or the music playing application, when the phone application or the music playing application is closed, the application, which has stopped recording in the background, cannot automatically obtain the audio session and the application performing the recording in the background cannot automatically restart and continue to perform the recording. Since the recording operation may be interrupted by each phone operation or music playing operation, requirement of the application, which may need to keep recording in the background, cannot be satisfied.
[0021] According to an example of the present disclosure, after a first application performing the recording in the background is interrupted by a second application with a higher priority and the second application stops running, a system may send a notification to the first application to inform the first application that the second application may have stopped running and the audio session may be re-obtained. An example of the present disclosure may provide a technical scheme for continuing to perform the recording after the first application performing the recording in the background is interrupted by the second application with a higher priority. The present disclosure may be described and introduced hereinafter in detail in accordance with several examples.
[0022] Referring to figure 1 , figure 1 is a flow chart illustrating a recording method in accordance with an example of the present disclosure. In this example, the recording method may be applied to an electronic device. The recording method may include following blocks.
[0023] In block 102, a recovery notification may be received.
[0024] In this block, the recovery notification may be used for informing a first application, which may suspend recording in the background, that an audio session may have been released by a second application with a higher priority. [0025] In block 104, a category of the audio session may be configured as playing and recording and an attribute of the audio session may be configured as MixWithOthers.
[0026] In block 106, the audio session may be obtained.
[0027] In block 108, after the audio session is obtained, the category of the audio session may be configured as recording and the recording may be performed in a background.
[0028] With the recording method provided by the present disclosure, after the recovery notification is received, the category of the audio session may be configured as the playing and recording and the attribute of the audio session may be configured as the MixWithOthers to obtaining the audio session. After the audio session is obtained, the category of the audio session may be configured as recording and the recording may be re-performed in the background. With the example of the present disclosure, the problem that the recording cannot automatically re-start after the application performing the recording in the background is interrupted by the phone application or the music playing application may be solved. An effect that the first application performing the recording in the background may automatically re-start after the first application is interrupted by the second application with the higher priority may be achieved.
[0029] The above mentioned electronic device may be an iOS electronic device. The electronic device may be a mobile phone, a tablet PC or a portable mobile device. This kind of device may be called an iDevice including the electronic device launched by Apple. The first letter of the name of the electronic device may be "i".
[0030] Referring to figure 2, figure 2 is a flow chart of another recording method in accordance with an example of the present disclosure. In this example, the recording method may be applied to an electronic device. The recording method
may include following blocks.
[0031] In block 201 , a code may be configured in an Operating System (OS) or a first application. The code may be used for configuring a category and attribute of an audio session after a recovery notification is received by the first application. [0032] The code may be used for configuring the category and attribute of the audio session after the first application receives the recovery notification.
[0033] The code may be compiled into a static database and added to the OS or the first application. Alternatively, a module including the code may be directly added to the OS or the first application. [0034] In block 202, a suspend notification may be received. The suspend notification may be used for informing the first application performing the recording in a background that a second application with the higher priority may occupy the audio session.
[0035] The first application performing the recording in the background may receive the suspend notification from the OS. The suspend notification may be used for informing the first application performing the recording in the background that the second application with the higher priority may need to use the audio session. The second application with the higher priority may be a phone application or an application running in a foreground. [0036] The audio session may be a session for managing playing of the audio and recording. All applications which need to play the audio or perform the recording may play the audio or perform the recording after obtaining the audio session. When the application playing the audio or performing the recording is suspended or stopped, the audio session may be released. [0037] In block 203, the recording may be suspended, the audio session may be released and the second application with the higher priority may use the audio session.
[0038] Since the phone application or the application running in the foreground has higher priority, the system may send the suspend notification to the first application performing the recording in the background to inform the first
application that the second application with the higher priority may need to use the audio session. The first application performing the recording in the background may suspend recording and release the audio session.
[0039] For instance, when the first application is performing the recording in the background and a call is gotten from another user, the system may inform the first application performing the recording in the background to suspend the recording and inform the first application that the phone application may need to use the audio session. After receiving the suspend notification, the first application may suspend the recording and release the audio session. [0040] In block 204, a recovery notification may be received. The recovery notification may be used for informing the first application which may suspend performing the recording in the background that the audio session may have been released by the second application with the higher priority.
[0041] The first application which may suspend performing the recording in the background may receive the recovery notification. The recovery notification may be used for informing the first application which may suspend performing the recording in the background that the audio session may have been released by the second application with the higher priority.
[0042] For instance, after the phone is hung up, the system may send the recovery notification to the first application, which may suspend the recording in the background, to inform the first application that the audio session may be released. After the first application, which may suspend the recording in the background, the audio session may be re-obtained and the recording may be restarted. [0043] In block 205, a category of the audio session may be configured as playing and recording and an attribute of the audio session may be configured as MixWithOthers.
[0044] After the category of the audio session may be configured as the playing and recording and the attribute of the audio session may be configured as the MixWithOthers by the code, the first application may re-obtain the audio session.
[0045] In block 206, the audio session may be re-obtained.
[0046] The first application, which may suspend the recording in the background, may re-obtain the audio session.
[0047] In block 207, after the audio session is obtained, the category of the audio session may be configured as the recording, and the recording may be performed in the background.
[0048] According to an example, if the category of the audio session is configured as the recording, the attribute of audio session may be Not-MixWithOthers in default.
[0049] If the category of the audio session is configured as recording, the attribute of the audio session cannot be configured as MixWithOthers. Therefore, if the category of the audio session is configured as recording, the attribute of MixWithOthers may be invalid, which may ensure that the first application performing the recording in the background may not affect normal playing performed by the mobile terminal, such as a ringtone or a text tone. [0050] It should be noted that when the first application performing the recording in the background is interrupted by the second application with the higher priority, blocks 204 to 207 may be repeated to continue to perform the recording in the background.
[0051] With the recording method provided by this example of the present disclosure, after the recovery notification is received, the category of the audio session may be configured as playing and recording and the attribute of the audio session may be configured as MixWithOthers to re-obtain the audio session. After the audio session is obtained, the category of the audio session may be configured as recording and the recording may restart in the background. The problem that the recording cannot automatically re-start after the first application performing the recording in the background is interrupted by the phone application or the music playing application may be solved. An effect that the first application performing the recording in the background may automatically re-start after the first application is interrupted by the second application with the higher priority may be achieved. With the example of the present disclosure, after the application, which may suspend the recording in the background, receives the
recovery notification, the code for configuring the category and attribute of the audio session may be configured in the OS or the first application, by which the application, which may suspend the recording in the background, may re-obtain the audio session to continue to perform the recording in the background. [0052] Examples of the devices for executing the recording methods in examples of the present disclosure may be described hereinafter. Refer to the examples of the recording methods of the present disclosure for those details, which may not be disclosed in examples of the recording devices of the present disclosure. [0053] Referring to figure 3, figure 3 is a schematic diagram illustrating structure of a recording device in accordance with an example of the present disclosure. The recording device may be implemented with software, hardware or combination thereof and may be an electronic device or partial of an electronic device. The electronic device may include a mobile phone, tablet PC or a portable mobile device. The recording device may include: a recovery notification receiving module 310, a session configuration module 320, a session obtaining module 330 and a session re-configuring module 340.
[0054] The recovery notification receiving module 310 may be configured to receive a recovery notification and obtain that an audio session is released according to the recovery notification.
[0055] The recovery notification may be used for informing a first application, which may suspend performing recording in the background that the audio session may be released by a second application with a higher priority.
[0056] The session configuration module 320 may be configured to configure a category of the audio session as playing and recording and configure an attribute of the audio session as MixWithOthers.
[0057] The session obtaining module 330 may be configured to obtain the audio session.
[0058] The session re-configuring module 340 may be configured to configure the category of the audio session as recording and perform the recording in a background.
[0059] With the recording device provided by the present disclosure, after the recovery notification is received, the category of the audio session may be configured as the playing and recording and the attribute of the audio session may be configured as the MixWithOthers. After the audio session is obtained, the category of the audio session may be configured as recording and the recording may be re-performed in the background. With this example of the present disclosure, the problem that the recording cannot automatically re-start after the application performing the recording in the background is interrupted by the phone application or the music playing application may be solved. An effect that the first application performing the recording in the background may automatically re-start after the first application is interrupted by the second application with the higher priority may be achieved.
[0060] Referring to figure 4, figure 4 is a schematic diagram illustrating structure of another recording device in accordance with an example of the present disclosure. The recording device may be implemented with software, hardware or combination thereof and may be an electronic device or partial of an electronic device. The electronic device may include a mobile phone, tablet PC or a portable mobile device. The recording device may include: a suspend notification receiving module 301 , a session releasing module 302, a recovery notification receiving module 310, a code configuration module 311 , a session configuration module 320, a session obtaining module 330 and a session re-configuring module 340.
[0061] The suspend notification receiving module 301 may be configured to receive a suspend notification. [0062] According to an example, the suspend notification may be used for informing a first application performing recording in a background that a second application with a higher priority may need to use an audio session.
[0063] The session releasing module 302 may be configured to suspend the recording according to the suspend notification and release the audio session, so that the second application with the higher priority may occupy the audio session.
[0064] The recovery notification receiving module 310 may be configured to
receive a recovery notification and obtain that the audio session is released according to the recovery notification.
[0065] According to an example, the recovery notification may be used for informing the first application, which may suspend performing the recording in the background that the audio session may be released by the second application with a higher priority.
[0066] The code configuration module 311 may be configured to configure a code in an Operating System (OS).
[0067] According to an example, the code may be used for configuring the category and attribute of the audio session after the first application receives the recovery notification. Alternatively, the code may be configured in the first application. The code may be used for configuring the category and attribute of the audio session after the first application receives the recovery notification.
[0068] The session configuration module 320 may be configured to configure a category of the audio session as playing and recording and configure an attribute of the audio session as MixWithOthers.
[0069] The session obtaining module 330 may be configured to obtain the audio session.
[0070] The session re-configuring module 340 may be configured to configure the category of the audio session as recording and perform the recording in a background.
[0071] According to an example, the suspend notification receiving module 301 , session releasing module 302, recovery notification receiving module 310, code configuration module 311 , session configuration module 320, session obtaining module 330 and session re-configuring module 340 may be software modules, e.g., sets of machine readable instructions, stored in a hardware memory device. In another example, the suspend notification receiving module 301 , session releasing module 302, recovery notification receiving module 310, code configuration module 311 , session configuration module 320, session obtaining module 330 and session re-configuring module 340 may be hardware modules on a hardware device. In a further example, the suspend notification receiving
module 301 , session releasing module 302, recovery notification receiving module 310, code configuration module 311 , session configuration module 320, session obtaining module 330 and session re-configuring module 340 may include a combination of software and hardware modules. [0072] With the recording device provided by this example of the present disclosure, after the recovery notification is received, the category of the audio session may be configured as playing and recording and the attribute of the audio session may be configured as MixWithOthers to re-obtain the audio session. After the audio session is obtained, the category of the audio session may be configured as recording and the recording operation may restart in the background. The problem that the recording cannot automatically re-start after the first application performing the recording in the background is interrupted by the phone application or the music playing application may be solved. An effect that the first application performing the recording in the background may automatically re-start after the first application is interrupted by the second application with the higher priority may be achieved. With the example of the present disclosure, after the application, which may suspend the recording in the background, receives the recovery notification, the code for configuring the category and attribute of the audio session may be configured in the OS or the first application, by which the application, which may suspend the recording in the background, may re-obtain the audio session to continue to perform the recording in the background.
[0073] Referring to figure 5, figure 5 is a flow chart illustrating a playing method in accordance with an example of the present disclosure. The playing method may include following blocks.
[0074] In block 501 , a recovery notification may be received. It may be obtained that an audio session may be released according to the recovery notification.
[0075] In block 502, a category of the audio session may be configured as playing and recording. [0076] In block 503, an attribute of the audio session may be configured as MixWithOthers.
[0077] In block 504, the audio session may be obtained.
[0078] In block 505, the category of the audio session may be configured as playing.
[0079] In block 506, a playing operation may be performed in a background. [0080] According to an example of the present disclosure, a suspend notification may be received, the playing operation may be suspended according to the suspend notification and the audio session may be released.
[0081] According to an example of the present disclosure, a code may be configured in an OS. The category of the audio session may be configured as the playing and recording according to the code and the attribute of the audio session may be configured as the MixWithOthers according to the code.
[0082] Referring to figure 6, figure 6 is a schematic diagram illustrating structure of a playing device in accordance with an example of the present disclosure. Referring to figure 6, the playing device may include: a recovery notification receiving module 601 , a session configuration module 602, a session obtaining module 603 and a session re-configuring module 604.
[0083] The recovery notification receiving module 601 may be configured to receive a recovery notification and obtain that an audio session is released according to the recovery notification. [0084] The session configuration module 602 may be configured to configure a category of the audio session as playing and recording and configure an attribute of the audio session as MixWithOthers.
[0085] The session obtaining module 603 may be configured to obtain the audio session. [0086] The session re-configuring module 604 may be configured to configure the category of the audio session as playing and perform the playing in a background.
[0087] According to an example, the playing device may further include: a suspend notification receiving module 605, configured to receive a suspend notification.
[0088] According to an example, the playing device may further include: a session releasing module 606, configured to suspend the playing according to the suspend notification and release the audio session.
[0089] According to an example, the playing device may further include: a code configuration module 607, to configure a code in an Operating System (OS), configure the category of the audio session as the playing and recording according to the code and configure the attribute of the audio session as the MixWithOthers according to the code.
[0090] According to an example, the recovery notification receiving module 601 , session configuration module 602, session obtaining module 603, session re-configuring module 604, suspend notification receiving module 605, session releasing module 606 and code configuration module 607 may be software modules, e.g., sets of machine readable instructions, stored in a hardware memory device. In another example, the recovery notification receiving module 601 , session configuration module 602, session obtaining module 603, session re-configuring module 604, suspend notification receiving module 605, session releasing module 606 and code configuration module 607 may be hardware modules on a hardware device. In a further example, the recovery notification receiving module 601 , session configuration module 602, session obtaining module 603, session re-configuring module 604, suspend notification receiving module 605, session releasing module 606 and code configuration module 607 may include a combination of software and hardware modules.
[0091] Referring to figure 7, figure 7 is a schematic diagram illustrating structure of another recording device in accordance with an example of the present disclosure.
[0092] The recording device may include: a storage medium 701 , a processor 702, a bus 703, peripherals 704, a database 705 and a communication module 706.
[0093] The storage medium 701 , processor 702, peripherals 704, database 705 and communication module 706 may connect with the bus 703.
[0094] The storage medium 701 may store the recovery notification receiving
module 310, session configuration module 320, session obtaining module 330 and session re-configuring module 340.
[0095] According to an example, the storage medium 701 may further store the suspend notification receiving module 301 , session releasing module 302 and code configuration module 311 .
[0096] The processor 702 may include any appropriate processor or processors. Further, processor 702 can include multiple cores for multi-thread or parallel processing. Storage medium 701 may include memory modules, such as Read-only memory (ROM), Random Access Memory (RAM), flash memory modules, and erasable and rewritable memory, and mass storages, such as CD-ROM, U-disk, and hard disk, etc. The processor 702 may communicate with the storage medium 701 and execute above operations performed by the suspend notification receiving module 301 , session releasing module 302, recovery notification receiving module 310, code configuration module 311 , session configuration module 320, session obtaining module 330 and session re-configuring module 340.
[0097] Further, peripherals 704 may include I/O devices such as a keyboard and mouse, and communication module 706 may include network devices for establishing connections through the communication network. Database 705 may include one or more databases for storing certain data and for performing certain operations on the stored data, such as database searching.
[0098] According to an example, the suspend notification receiving module 301 , session releasing module 302, recovery notification receiving module 310, code configuration module 311 , session configuration module 320, session obtaining module 330 and session re-configuring module 340 may be machine readable instructions. The storage medium 701 may be a non-transitory computer readable storage medium.
[0099] Referring to figure 8, figure 8 is a schematic diagram illustrating structure of another playing device in accordance with an example of the present disclosure.
[00100]The playing device may include: a storage medium 801 , a processor 802,
a bus 803, peripherals 804, a database 805 and a communication module 806.
[00101]The storage medium 801 , processor 802, peripherals 804, database 805 and communication module 806 may connect with the bus 803.
[00102]The storage medium 801 may store the recovery notification receiving module 601 , session configuration module 602, session obtaining module 603 and session re-configuring module 604.
[00103] According to an example, the storage medium 801 may further store the suspend notification receiving module 605, session releasing module 606 and code configuration module 607. [00104] The processor 802 may include any appropriate processor or processors. Further, processor 802 can include multiple cores for multi-thread or parallel processing. Storage medium 801 may include memory modules, such as Read-only memory (ROM), Random Access Memory (RAM), flash memory modules, and erasable and rewritable memory, and mass storages, such as CD-ROM, U-disk, and hard disk, etc. The processor 802 may communicate with the storage medium 801 and execute above operations performed by the recovery notification receiving module 601 , session configuration module 602, session obtaining module 603, session re-configuring module 604, suspend notification receiving module 605, session releasing module 606 and code configuration module 607.
[00105] Further, peripherals 804 may include I/O devices such as a keyboard and mouse, and communication module 806 may include network devices for establishing connections through the communication network. Database 805 may include one or more databases for storing certain data and for performing certain operations on the stored data, such as database searching.
[00106] According to an example, the recovery notification receiving module 601 , session configuration module 602, session obtaining module 603, session re-configuring module 604, suspend notification receiving module 605, session releasing module 606 and code configuration module 607 may be machine readable instructions. The storage medium 801 may be a non-transitory computer readable storage medium.
[00107] In various embodiments, a hardware module may be implemented mechanically or electronically. For example, a hardware module may comprise dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC)) to perform certain operations. A hardware module may also comprise programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. It will be appreciated that the decision to implement a hardware module mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.
[00108] What has been described and illustrated herein are examples of the disclosure along with some variations. The terms, descriptions and figures used herein are set forth by way of illustration only and are not meant as limitations. Many variations are possible within the scope of the disclosure, which is intended to be defined by the following claims -- and their equivalents - in which all terms are meant in their broadest reasonable sense unless otherwise indicated.
Claims
1 . A recording method, comprising:
receiving a recovery notification;
obtaining that an audio session is released according to the recovery notification;
configuring a category of the audio session as playing and recording;
configuring an attribute of the audio session as MixWithOthers;
obtaining the audio session;
configuring the category of the audio session as recording; and
performing the recording in a background.
2. The method according to claim 1 , further comprising:
receiving a suspend notification;
suspending the recording according to the suspend notification; and releasing the audio session.
3. The method according to claim 1 or 2, further comprising:
configuring a code in an Operating System (OS);
wherein configuring the category of the audio session as playing and recording and configuring the attribute of the audio session as MixWithOthers comprises:
configuring the category of the audio session as the playing and recording according to the code and configuring the attribute of the audio session as the MixWithOthers according to the code.
4. A recording device, comprising:
a recovery notification receiving module, to receive a recovery notification and obtain that an audio session is released according to the recovery notification;
a session configuration module, to configure a category of the audio session as playing and recording and configure an attribute of the audio session as MixWithOthers;
a session obtaining module, to obtain the audio session; and a session re-configuring module, to configure the category of the audio session as recording and perform the recording in a background.
5. The device according to claim 4, further comprising:
a suspend notification receiving module, to receive a suspend notification; and
a session releasing module, to suspend recording according to the suspend notification and release the audio session.
6. The device according to claim 4 or 5, further comprising:
a code configuration module, to configure a code in an Operating System (OS), configure the category of the audio session as the playing and recording according to the code and configure the attribute of the audio session as the MixWithOthers according to the code.
7. A playing method, comprising:
receiving a recovery notification;
obtaining that an audio session is released according to the recovery notification;
configuring a category of the audio session as playing and recording;
configuring an attribute of the audio session as MixWithOthers;
obtaining the audio session;
configuring the category of the audio session as playing; and
performing the playing in a background.
8. The method according to claim 7, further comprising:
receiving a suspend notification;
suspending the playing according to the suspend notification; and
releasing the audio session.
9. The method according to claim 7 or 8, further comprising:
configuring a code in an Operating System (OS);
wherein configuring the category of the audio session as playing and recording and configuring the attribute of the audio session as MixWithOthers comprises:
configuring the category of the audio session as the playing and recording according to the code and configuring the attribute of the audio session as the MixWithOthers according to the code.
10. A playing device, comprising:
a recovery notification receiving module, to receive a recovery notification and obtain that an audio session is released according to the recovery notification;
a session configuration module, to configure a category of the audio session as playing and recording and configure an attribute of the audio session as MixWithOthers;
a session obtaining module, to obtain the audio session; and
a session re-configuring module, to configure the category of the audio session as playing and perform the playing in a background.
11 . The device according to claim 10, further comprising:
a suspend notification receiving module, to receive a suspend notification; and
a session releasing module, to suspend the playing according to the suspend notification and release the audio session.
12. The device according to claim 10 or 11 , further comprising:
a code configuration module, to configure a code in an Operating System (OS), configure the category of the audio session as the playing and recording according to the code and configure the attribute of the audio session as the MixWithOthers according to the code.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201310443450.3 | 2013-09-26 | ||
CN201310443450.3A CN104519191B (en) | 2013-09-26 | 2013-09-26 | The way of recording, device and electronic equipment |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2015043319A1 true WO2015043319A1 (en) | 2015-04-02 |
Family
ID=52742004
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2014/083841 WO2015043319A1 (en) | 2013-09-26 | 2014-08-07 | Recording method, recording device, playing method and playing device |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN104519191B (en) |
WO (1) | WO2015043319A1 (en) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP6759046B2 (en) * | 2016-10-14 | 2020-09-23 | キヤノン株式会社 | Radiographer, control method of radiographer, program |
CN111580776B (en) * | 2020-04-28 | 2023-07-21 | 广州市百果园信息技术有限公司 | Audio function recovery method, device, terminal and storage medium |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101378426A (en) * | 2008-09-02 | 2009-03-04 | 深圳华为通信技术有限公司 | Method and terminal for preventing disturb |
CN103227851A (en) * | 2013-03-05 | 2013-07-31 | 广东欧珀移动通信有限公司 | Method and device for communication terminal recording |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101409609A (en) * | 2007-10-09 | 2009-04-15 | 北京信威通信技术股份有限公司 | Method and apparatus for high-efficiency reliable voice transmission in wireless system |
-
2013
- 2013-09-26 CN CN201310443450.3A patent/CN104519191B/en active Active
-
2014
- 2014-08-07 WO PCT/CN2014/083841 patent/WO2015043319A1/en active Application Filing
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101378426A (en) * | 2008-09-02 | 2009-03-04 | 深圳华为通信技术有限公司 | Method and terminal for preventing disturb |
CN103227851A (en) * | 2013-03-05 | 2013-07-31 | 广东欧珀移动通信有限公司 | Method and device for communication terminal recording |
Also Published As
Publication number | Publication date |
---|---|
CN104519191A (en) | 2015-04-15 |
CN104519191B (en) | 2018-05-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2016078624A1 (en) | Method and device for controlling popping up of window by identifying full screen mode | |
EP3355223A1 (en) | Unlock method and mobile terminal | |
US9250958B2 (en) | System, method, and apparatus for improving application-launch latencies | |
US20130275915A1 (en) | Appratus and method for loading application of portable device | |
CN106778248B (en) | Method and device for starting application program Activity | |
JP5945074B2 (en) | Method, device, and mobile terminal for API intercept related applications | |
US11337042B2 (en) | Short message processing method and apparatus, and electronic device | |
US9639256B2 (en) | Method for starting activity of mobile terminal and the mobile terminal | |
US10869176B1 (en) | Near field communication (NFC) enhanced computing systems | |
US9116698B2 (en) | Intelligent selection of operating state upon change of power state | |
WO2015062321A1 (en) | Method and device for displaying information relevant to unknown incoming/outgoing phone number | |
WO2017045533A1 (en) | Method and device for displaying state of user equipment on pre-set interface of application program | |
WO2020224238A1 (en) | Blockchain node depolyment method, device and equipment, and storage medium | |
CN105940375B (en) | Dynamic reassignment for multiple operating system devices | |
CN106406944A (en) | Control method and system for forbidding self-starting of application | |
US9509832B2 (en) | Recommending preferred ringer settings for a mobile communications device | |
WO2016183918A1 (en) | Method and device for processing storage space | |
US10212272B1 (en) | Near field communication enhanced computing systems | |
US9692876B2 (en) | Suppress and resume notifications based on motion | |
CN104794046B (en) | The method and system of symbolic program running log | |
WO2015043319A1 (en) | Recording method, recording device, playing method and playing device | |
WO2017080383A1 (en) | Method and device for loading software module | |
WO2017024519A1 (en) | Startup method of smart terminal system, device and smart terminal | |
WO2017166640A1 (en) | Application calling method and terminal | |
CN104834553A (en) | Service concurrent processing method for user terminal and user terminal |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 14849960 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 14849960 Country of ref document: EP Kind code of ref document: A1 |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205N DATED 02/06/2016) |