A method, system, electronic device, and storage medium for business access

Abstract

A method, system, electronic device, and storage medium for accessing services are disclosed, applicable to the field of terminal technology. The method includes: when a user performs a service operation on a first electronic device and a second electronic device, a control center APK obtains a first identifier corresponding to the first service declared in the system manifest file of a first control center software development kit (SDK). Then, based on the first identifier, a first access instruction containing the first identifier is generated. According to the first access instruction, the control center APK accesses the first control center SDK corresponding to the service APK of the first service, thereby enabling the first control center APK to access the service APK of the first service. Thus, by using different identifiers for different services and generating different first access instructions, when a service layer includes multiple service APKs, the accurate service APK is accessed, ensuring the normal operation of collaborative services.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to a method, system, electronic device, and storage medium for accessing services. Background Technology

[0002] Unified management of multiple devices, enabling collaborative execution of business processes with different devices through a single device control center interface, has become a key aspect of collaborative technology development. Collaborative technology is a distributed technology applied to multiple electronic devices. Utilizing multi-device collaborative technology, two or more electronic devices can collaborate across systems and devices, achieving resource sharing and collaborative operation.

[0003] To achieve unified management of multiple devices in a collaborative manner, a layered architecture including a control layer and a business layer can be deployed at the application layer. The control layer controls the implementation logic of collaborative services, while the business layer completes the collaborative service operations. The business layer can integrate the control center software development kit (SDK), and the control layer can interact with the business side through the control SDK.

[0004] With the development of multi-device collaboration technology, a business layer may include Android application packages (APKs) for multiple businesses, with one business APK corresponding to a control center SDK. This means that when the control center APK accesses a business APK through the control center SDK, existing technologies for accessing business layers containing only one business APK may fail to access the correct business APK, thus preventing collaborative services from functioning properly. Summary of the Invention

[0005] The purpose of this application is to provide a method, system, electronic device, and storage medium for business access, which aims to distinguish different businesses by using different access instructions, so as to achieve accurate access to the business APKs of different integrated control center SDKs.

[0006] Firstly, this application provides a method for accessing services, applied to a first electronic device, wherein the first electronic device has installed a collaborative service Android application package APK and a control center APK. The control center APK is used to control the first electronic device to implement collaborative services through the collaborative service service APK. The method includes:

[0007] When a user performs a service operation on the first electronic device and the second electronic device, the control center APK obtains a first identifier declared in the system manifest file of the first control center SDK, which represents the identifier corresponding to the first service. Based on the first identifier, the control center APK generates a first access instruction containing the first identifier. According to the first access instruction, the control center APK accesses the first control center SDK corresponding to the service APK of the first service, and then accesses the service APK of the first service through the first control center SDK. For example, if the first identifier of the first service is com.ad.A.xietong.ControlcenterARRProvider, a first access instruction containing the identifier of the first service, "content: / / com.ad.A.xietong.conterControlcenterARRProvider / train," is generated. When the first identifier of the first service changes, the corresponding first service changes. Thus, different services correspond to different identifiers, generating different first access instructions, thereby ensuring that when a service layer includes multiple service APKs, the accurate service APK is accessed, enabling collaborative services to function normally.

[0008] In one possible implementation, the first control center SDK is integrated into the business APK of the first service. This allows for direct interaction between the control center APK and the business APK via API interfaces, making the operation simple.

[0009] In one possible implementation, the first identifier includes the business APK package name of the first service and the name of the called component of the first control center SDK. When a user performs a business operation on the first service of the first electronic device and the second electronic device, the business ID of the first service is first obtained. Based on the business ID and a preset mapping relationship between business IDs and business APK package names, the business APK package name of the first service is determined. The first identifier is then obtained based on the business APK package name. Finally, based on the first identifier and a preset mapping relationship between identifiers and access instructions, a first access instruction is generated. In this way, the business side does not need to manually declare authority to obtain the first access instruction, reducing the probability of errors from manually declaring authority.

[0010] In one possible implementation, when a user performs a service operation on a second service of the first electronic device and the second electronic device, the method further includes: the control center APK obtaining a second identifier and generating a second access instruction containing the second identifier. The second identifier is a pre-declared identifier corresponding to the second service in the system manifest file of the second control center SDK. Based on the second access instruction, the control center APK accesses the second control center SDK corresponding to the service APK of the second service, and then accesses the service APK of the second service through the second control center SDK to achieve collaborative service mode switching. Thus, when a user performs a service mode switching operation for the collaborative service between the first electronic device and the second electronic device, the service APK corresponding to the second service is accurately located, resulting in high usability.

[0011] In one possible implementation, the second identifier includes the business APK package name of the second service and the name of the called component of the second control center SDK. When a user performs a service mode switching operation for the collaborative service between the first electronic device and the second electronic device, the service ID of the second service is first obtained. Based on the service ID of the second service and the preset mapping relationship between service IDs and service APK package names, the business APK package name of the first service is determined. The first identifier is obtained based on the business APK package name. Based on the first identifier and the preset mapping relationship between identifiers and access instructions, a first access instruction is generated. In this way, the service side does not need to manually declare authority to obtain the first access instruction, reducing the probability of errors from manually declaring authority.

[0012] In one possible implementation, the first service's APK obtains a third identifier and generates a third access instruction containing that identifier. This third identifier corresponds to one declared in the control center APK's system manifest file. The first control center SDK accesses the control center APK according to the third access instruction, enabling the first service's APK to access the control center APK and execute callback operations. Once the user has implemented the collaborative operation of the first service on both the first and second electronic devices, the control center APK executes a callback of the collaborative operation result according to the third access instruction. This eliminates the need for manual authorization declarations for the entire collaborative service access, ensuring good control and reducing the probability of errors when the original logic is modified.

[0013] Secondly, embodiments of this application provide a system for accessing services, the system comprising:

[0014] The collaborative business includes a business Android application package (APK), a control center (APK), and a first control center software development kit (SDK). When a user performs a first business operation on the first electronic device and the second electronic device, the control center (APK) obtains a first identifier and generates a first access instruction containing the first identifier. The first identifier is a pre-declared identifier in the system manifest file of the first control center (SDK) that corresponds to the first business. The control center (APK) accesses the first control center (SDK) corresponding to the business APK of the first business according to the first access instruction, and then accesses the business APK of the first business through the first control center (SDK).

[0015] Optionally, the first control center SDK is integrated into the business APK of the first service.

[0016] In one possible implementation, the first identifier includes the business APK package name of the first service and the name of the called component of the first control center SDK; wherein, the control center APK is specifically used for: obtaining the business ID of the first service; determining the business APK package name of the first service based on the business ID of the first service and a preset mapping relationship between the business ID and the business APK package name; obtaining the first identifier based on the business APK package name; and generating a first access instruction based on the first identifier and a preset mapping relationship between the identifier and the access instruction.

[0017] In this way, different first access instructions are generated by corresponding different identifiers for different services, so that when a service layer includes multiple service APKs, the correct service APK can be accessed, and collaborative services can proceed normally.

[0018] Thirdly, this application also provides an electronic device, which includes a memory and a processor, the memory being coupled to the processor; the memory stores program instructions that, when executed by the processor, cause the electronic device to perform the method described in any of the first aspects.

[0019] Fourthly, this application also provides a readable storage medium characterized by including computer-readable instructions that, when executed on a computing device, cause the computing device to perform the method described in any one of the first aspects.

[0020] It should be understood that the descriptions of technical features, technical solutions, beneficial effects, or similar language in this application do not imply that all features and advantages can be achieved in any single embodiment. Rather, it is understood that the description of a feature or beneficial effect means that a specific technical feature, technical solution, or beneficial effect is included in at least one embodiment. Therefore, the descriptions of technical features, technical solutions, or beneficial effects in this specification do not necessarily refer to the same embodiment. Furthermore, the technical features, technical solutions, and beneficial effects described in this embodiment can be combined in any suitable manner. Those skilled in the art will understand that embodiments can be implemented without one or more specific technical features, technical solutions, or beneficial effects of a particular embodiment. In other embodiments, additional technical features and beneficial effects may be identified in specific embodiments that do not embody all embodiments. Attached Figure Description

[0021] Figure 1 A schematic diagram illustrating a unified management system for multiple devices in accordance with an embodiment of this application;

[0022] Figure 2 A schematic diagram of the hardware structure of the electronic device provided in the embodiments of this application;

[0023] Figure 3 This is a software structure block diagram of the electronic device 100 according to an embodiment of this application;

[0024] Figure 4 An architectural block diagram of an application layer provided in this application embodiment;

[0025] Figure 5 This application provides an architecture deployment diagram of an application layer.

[0026] Figure 6 A schematic diagram of an access instruction-based invocation provided for this application;

[0027] Figure 7A A schematic diagram illustrating a service access-based method provided in an embodiment of this application;

[0028] Figure 7B A schematic diagram illustrating another service access-based method provided in an embodiment of this application;

[0029] Figure 7C This is a schematic diagram of a service access-based method provided in an embodiment of this application. Detailed Implementation

[0030] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0031] The term "and / or" in this article is merely a description of the association relationship between associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone.

[0032] The terms "first" and "second," etc., used in the specification and claims of this application are used to distinguish different objects, not to describe a specific order of objects. For example, "first target object" and "second target object," etc., are used to distinguish different target objects, not to describe a specific order of target objects.

[0033] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0034] In the description of the embodiments in this application, unless otherwise stated, "multiple" means two or more. For example, multiple processing units means two or more processing units; multiple systems means two or more systems.

[0035] Currently, with the increasing demands of users for terminal technology, unified management of multi-device collaboration has become a key aspect of the development of collaborative technologies. Unified management of multi-device collaboration refers to the ability for users to establish connections with different devices to perform collaborative services through a single device control center interface. For example, the mobile device control center interface displays all other devices that can connect to the mobile device, namely device A, device B, and device C. Within this interface, users can enable collaboration between the mobile device and device A, as well as with devices B and C, and can also terminate ongoing collaborative services between device A and other devices.

[0036] Example illustration: See Figure 1This diagram illustrates a unified management system for multiple devices, as provided in this application embodiment. The main device is a mobile phone (represented by a blue ball enclosing a "pad" icon), and the devices to be connected are tablets (represented by white balls enclosing "pad"), laptops (represented by white balls enclosing "magic book"), large-screen display devices (represented by white balls enclosing "smart TV"), and tablets (represented by white balls enclosing "pad" icons). On the main control center interface, dragging the white "magic book" ball to the main device triggers the connection between the magic book and the tablet; dragging the white "smart TV" ball to the main device triggers the connection between the tablet and the smart TV. From a business perspective, each device may run multiple services simultaneously, such as multi-screen collaboration and follow-on navigation. Dragging the balls essentially involves the main device control center and the secondary device control center issuing commands to trigger the connection and other operations between the two devices.

[0037] To implement this triggered business logic, a layered architecture including a control layer and a business layer can be deployed at the application layer. The control layer controls the implementation logic of the collaborative business, while the business layer completes the collaborative business operations. The business layer can integrate a control center software development kit (SDK), and the control layer can interact with the business side through the control SDK. Alternatively, the business layer can integrate a control center SDK, and the control center SDK can be used to interact with the business layer.

[0038] However, a business layer may include business APKs for multiple businesses, and one of the business APKs corresponds to a control center SDK. This means that when the control center APK accesses the business APK through the control center SDK, the existing technology for accessing a business layer containing only one business APK may not be able to access the correct business APK, thus causing collaborative business to fail to function properly.

[0039] Based on this, this application provides a method for accessing services by assigning different access instructions to the service APKs of different services, thereby achieving the purpose of preparing to access the service APKs that integrate the control center SDK.

[0040] One method for accessing services according to an embodiment of this application can be applied to various types of electronic devices with display functions.

[0041] See Figure 2 This is a schematic diagram of the hardware structure of the electronic device provided in an embodiment of this application. This device can function as either a master device or a slave device in a multi-device collaborative system. Figure 2As shown, the electronic device 100 may include a processor 110, a memory 120, a universal serial bus (USB) interface 130, a radio frequency circuit 140, a mobile communication module 150, a wireless communication module 160, a camera 170, a display screen 180, a touch sensor 190, a barometric pressure sensor 210, and buttons 220, etc.

[0042] Processor 110 may include one or more processing units, such as an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU). Different processing units may be independent devices or integrated into one or more processors, such as in a system-on-a-chip (SoC). Processor 110 may also include memory for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. This memory can store instructions or data that have just been used or are being reused by processor 110.

[0043] In some embodiments, the processor 110 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0044] The memory 120 can be used to store executable program code, including instructions. The memory 120 may include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of the electronic device 100 (such as audio data, phonebook, etc.). Furthermore, the memory 120 may include one or more storage units, such as volatile memory (e.g., dynamic random access memory, DRAM, static random access memory, SRAM), etc.; and non-volatile memory (NVM), such as read-only memory (ROM), flash memory, etc. The processor 110 executes various functional applications and data processing of the electronic device 100 by running instructions stored in the memory 120 and / or instructions stored in memory located in the processor.

[0045] It should be noted that the operating systems referred to in the embodiments of this application include, but are not limited to, Android operating system, iOS operating system, iPad OS, HarmonyOS operating system, Windows operating system, Linux operating system, MAC OS operating system, embedded systems, etc.

[0046] The wireless communication function of the electronic device 100 can be implemented through the radio frequency circuit 140, the mobile communication module 150, the wireless communication module 160, the modem processor, and the baseband processor.

[0047] The radio frequency circuit 140 may include at least one antenna 141 for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 100 may be used to cover one or more communication frequency bands. In some embodiments, the antenna may be used in conjunction with a tuning switch.

[0048] The mobile communication module 150 can provide solutions for wireless communication applications on the electronic device 100, including 2G / 3G / 4G / 5G. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via the antenna 141, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to the modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via the antenna 141. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device.

[0049] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs sound signals through audio devices (including but not limited to speakers, receivers, etc.) or displays images or videos through the display screen 180. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 110 and may be housed in the same device as the mobile communication module 150 or other functional modules.

[0050] The wireless communication module 160 may include a Wi-Fi module, a Bluetooth (BT) module, a GNSS module, a near-field communication (NFC) module, an infrared (IR) module, etc. The wireless communication module 160 may be one or more devices integrating at least one of the above modules. The wireless communication module 160 receives electromagnetic waves via antenna 141, modulates and filters the electromagnetic wave signal, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, modulate and amplify them, and then convert them into electromagnetic waves for radiation via antenna 141.

[0051] In this embodiment, the wireless communication function of the electronic device 100 may include, for example, Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time-Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), 5th Generation Mobile Networks New Radio (5G NR), BT, GNSS, WLAN, NFC, FM, and / or IR functions. GNSS may include Global Positioning System (GPS), Global Navigation Satellite System (GLONASS), BeiDou Navigation Satellite System (BDS), Quasi-Zenith Satellite System (QZSS), and / or Satellite Based Augmentation Systems (SBAS).

[0052] Camera 170 is used to capture still images or videos. Camera 170 includes a lens and a photosensitive element. An object is projected onto the photosensitive element through the lens to generate an optical image. The photosensitive element can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, which is then passed to an ISP for conversion into a digital image signal. The ISP outputs the digital image signal to a DSP for processing. The DSP converts the digital image signal into image signals in standard formats such as RGB, YUV, and RYYB. In some embodiments, electronic device 100 may include one or N cameras 170, where N is a positive integer greater than 1.

[0053] An NPU (Neural Processing Unit) is a computational processor for neural networks (NNs). By borrowing the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it can rapidly process input information and continuously learn on its own. NPUs enable intelligent cognitive applications in electronic devices, such as image recognition, facial recognition, speech recognition, and text understanding.

[0054] The display screen 180 is used to display images, videos, etc. The display screen 180 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a MiniLED, a MicroLED, a Micro-OLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 100 may include one or N displays 180, where N is a positive integer greater than 1.

[0055] Touch sensor 190, also known as a "touch device," can be disposed on display screen 180. The touch sensor 190 and display screen 180 together form a touchscreen, also known as a "touchscreen." Touch sensor 190 is used to detect touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 180. In other embodiments, touch sensor 190 may also be disposed on the surface of electronic device 100, in a different location than display screen 180.

[0056] The barometric pressure sensor 210 is used to measure air pressure. In some embodiments, the electronic device 100 calculates altitude using the air pressure value measured by the barometric pressure sensor 210 to assist in positioning and navigation.

[0057] Buttons 220 include a power button, volume buttons, etc. Buttons 220 can be mechanical buttons or touch-sensitive buttons. Electronic device 100 can receive button input and generate key signal inputs related to user settings and function control of electronic device 100.

[0058] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0059] The software system of electronic device 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This embodiment of the invention uses the layered architecture Android system as an example to exemplify the software structure of electronic device 100.

[0060] Figure 3 This is a software structure block diagram of the electronic device 100 according to an embodiment of this application.

[0061] A layered architecture divides software into several layers, each with a clear role and function. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0062] The application layer can include a series of application packages.

[0063] like Figure 3 As shown, the application package may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, and multi-device collaboration applications.

[0064] The application framework layer provides application programming interfaces (APIs) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0065] like Figure 3 As shown, the application framework layer may include a window manager, content provider, view system, phone manager, resource manager, notification manager, etc.

[0066] The window manager is used to manage windowed applications. It can retrieve screen size, determine the presence of a status bar, lock the screen, and capture screenshots, among other things.

[0067] Content providers store and retrieve data, making that data accessible to applications. This data may include videos, images, audio, made and received phone calls, browsing history and bookmarks, phone books, etc.

[0068] A view system includes visual controls, such as controls for displaying text and controls for displaying images. View systems can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text notification icon could include views for displaying text and views for displaying images.

[0069] The phone manager is used to provide communication functions for electronic device 100. For example, it manages call status (including connection and disconnection).

[0070] The file explorer provides applications with various resources, such as localized strings, icons, images, layout files, video files, and more.

[0071] The notification manager allows applications to display notifications in the status bar. These notifications can be used to deliver informational messages and can disappear automatically after a short pause, requiring no user interaction. For example, the notification manager can be used to notify users of completed downloads or message alerts. The notification manager can also display notifications as icons or scrolling text in the top status bar, such as notifications from background applications, or as dialog boxes on the screen. Examples include displaying text messages in the status bar, emitting sounds, vibrating electronic devices, and flashing indicator lights.

[0072] The Android Runtime consists of core libraries and a virtual machine. The Android runtime is responsible for the scheduling and management of the Android system.

[0073] The core library consists of two parts: one part is the functionalities that need to be called by the Java language, and the other part is the Android core library.

[0074] The application layer and application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0075] System libraries can include multiple functional modules. For example: surface manager, media libraries, 3D graphics processing libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), etc.

[0076] The Surface Manager is used to manage the display subsystem and provides the blending of 2D and 3D layers for multiple applications.

[0077] The media library supports playback and recording of various common audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG.

[0078] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0079] A 2D graphics engine is a drawing engine for 2D drawing.

[0080] The kernel layer is the layer between hardware and software. The kernel layer contains at least the display driver, camera driver, audio driver, and sensor driver.

[0081] The information interaction method described in this application is mainly applied to the application layer of an electronic device. Specifically, it is applied to the capability layer, business layer, and control layer of the application layer. See also Figure 4 This is an architectural block diagram of an application layer provided in an embodiment of this application.

[0082] The business layer includes the control center display interface and a set of business applications. The control center interface is a human-computer interaction interface used to display multi-device collaborative interaction interfaces, including the system user interface (SystemUI), notification bar cards, and the full-screen control center interface.

[0083] SystemUI provides a loading window for the drop-down status bar cards, through which the service status of online services on the device can be loaded.

[0084] Notification bar cards are used to display the business status content of status bar cards.

[0085] The full-screen interface of the control center is used to display the full-screen UI.

[0086] The business application set is used to provide business services, receive business scheduling, and perform business processing. The business application set integrates collaborative services such as keyboard and mouse collaboration, call collaboration, call connection collaboration, and mobile navigation, as well as the corresponding profile software development kits (profile SDKs). The profile SDK is used for writing and reading data to the device service management module. The device service management module is used for device data synchronization. The business application set can also integrate other collaborative services and their corresponding profile SDKs. In this embodiment, other collaborative services are those that enable the connection between the master device and other multiple devices. In this embodiment, the business layer also integrates a control center SDK for interaction with the control layer.

[0087] The control layer, as the core module of the multi-device collaborative unified management architecture, includes a communication module, a device management module, a service status management module, a service scheduling management module, and a settings management module. It also includes a communication module SDK for the communication module, a profile SDK for the device management module, and a profile SDK for the service status management module.

[0088] The communication module enables communication between the two control centers, including cross-device command distribution and cross-device querying, and connects to the capability layer's communication module via the communication module SDK. The communication module also facilitates communication between the control centers before connection establishment. If the master device issues a connection command but the current device cannot initiate it, and the slave device must initiate the connection, the command is then sent to the slave device to establish the connection.

[0089] The Device Management module uses the Profile SDK to obtain real-time information on the online / offline status, capability information, and service status of devices under the same account as the main device from the Device Service Management module. The Device Management module includes online devices, connection status management, and all device capability sets. Online devices are used to query currently online devices; connection status management is used to query whether a current device is connected and whether it can connect; and all device capability sets are used to obtain multiple device statuses for all devices. Device status includes device online / offline information, capability information, and service status.

[0090] The Business Status Management module uses the Profile SDK to read in real-time business information supported by the main device and surrounding online devices from the Device Service Management module. This includes information such as the list of business capabilities supported by this application, business on / off status, whether a business can be scheduled by the control center, specific device types supported by a particular business, specific connection schemes supported by a particular business, and the current business operating status. The Business Status Management module includes the device's business set and business status management. The device's business set queries the set of services supported by this device, while business status management queries the business status supported by surrounding devices and receives updates on external business status changes, synchronizing these updates to the control center's display interface.

[0091] The service scheduling management module is used to determine service conflicts, issue prompts to users, and issue service instructions based on user intent. Specifically, it handles service connection, switching, and disconnection based on user selection and service conflict callbacks. The module includes service conflict scheduling and service connection management. Service conflict scheduling resolves conflicts. For example, both mobile phones and tablets support screen mirroring, but due to notification restrictions, they cannot coexist, requiring service conflict scheduling to resolve the conflict. Service connection management manages whether multiple devices have collaborative services and whether they can connect.

[0092] The settings management module is used to manage the relevant settings of the control center, including mode settings, etc.

[0093] The capability layer includes the communication module's same-account discovery, legacy service discovery compatibility, and connection transmission, used to realize device connection establishment, transmission, and discovery. The capability layer also includes a device service management module, used to realize device data synchronization, such as online / offline information, capability information, service status, and other device data synchronization, and to store it in the DataController of the data layer for schema persistent storage.

[0094] See Figure 5 This is a schematic diagram of the application layer architecture deployment provided in this application embodiment, applied to the Android platform.

[0095] In the Android platform, the architecture diagram exists as an Android Package (APK). Specifically, the system user interface (SystemUI), notification bar cards, and full-screen control center interface included in the business layer exist as APKs. Business application sets, such as notification collaboration, call continuation collaboration, and navigation services, also exist as APKs. Therefore, the business layer is also called the business APK layer, which includes multiple business APKs. Figure 5 The example provided includes systemUI.apk, AA.apk, and PCA.apk. Each service APK represents a specific collaborative service. The communication module, device management module, service status management module, service scheduling management module, and settings management module in the control layer all exist in APK form. Therefore, the control layer is also known as the control center APK.

[0096] The communication module in the capability layer implements services such as same-account discovery, legacy service discovery compatibility, and connection transmission through XMagiclink.apk, while the device service management module implements it through XDevice Profile.apk. The service APKs interact with the control center APK via the control center SDK. The control center APK communicates with XMagiclink.apk through the communication module SDK and interacts with XDevice Profile.apk through the device service management SDK.

[0097] To better illustrate the information interaction method provided in this application embodiment, the following uses an Android device as an example to provide a detailed description of the control center APK accessing the service APK.

[0098] When performing collaborative business operations on a combination of master and slave devices, such as Figure 1As shown, when a user drags a white ball on the main interface of the control center, the control center APK sends scheduling instructions to the business APK through the control center SDK, enabling interaction between the control center APK and the business APK, thereby achieving collaborative business operations.

[0099] To enable interaction between the Control Center APK and the Control Center SDK, communication can be achieved through the `ContentProvider.call()` call mechanism. Specifically, both the Control Center APK and SDK include a `ContentProvider` component. Using `ContentProvider.call()` in conjunction with an access command (e.g., a `Uri`), the specified `ContentProvider` is accessed, thus facilitating communication between the two. The access command can be pre-formatted as: "standard prefix.identifier.data path". The standard prefix indicates that a `ContentProvider` controls this data; the identifier uniquely identifies the `ContentProvider`, allowing the target `ContentProvider` to be located; and the data path determines the dataset. For example: `Content: / / com.example.transportation.provider / train`. Here, `Content: / / ` is the standard prefix, and `com.example.transportation.provider` represents the authority declared in the Android Manifest, allowing the target `ContentProvider` to be found. In other words, the content provider of the control center APK can be found by the control center SDK of the business APK, and the control center SDK of the corresponding business APK can also be found by the control center APK.

[0100] See Figure 6This application provides a schematic diagram of an access instruction-based invocation. The ContentProvider component of the first control center SDK corresponding to the service APK of the first service includes a first data invocation component (i.e., ContentResolve of the service APK of the first service shown in the diagram) and a first invoked component (i.e., ControlCenterAARProvider of the service APK of the first service shown in the diagram). The ContentProvider component of the second control center SDK corresponding to the service APK of the second service includes a second data invocation component (i.e., ContentResolve of the service APK of the second service shown in the diagram) and a second invoked component (i.e., ControlCenterAARProvider of the service APK of the second service shown in the diagram).

[0101] The system comprises the following components: A first data invocation component invokes the ContentProvider of the control center APK to enable the business APK of the first service to access the control center APK. A first invoked component is invoked by the ContentProvider of the control center APK to enable the control center APK to access the business APK. The ContentProvider component of the control center APK includes a third data invocation component (i.e., the ContentResolver of the control center APK shown in the diagram) and a third invoked component (i.e., the ControlCenterProvider shown in the diagram). A second data invocation component invokes either the first invoked component of the first control center SDK or the second invoked component of the second control center SDK to enable the control center APK to access the specific business APK. A third invoked component is invoked by either the first data invocation component of the first control center SDK or the second data invoked component of the second control center SDK to enable different business APKs to access the control center APK.

[0102] In this embodiment, the first data invocation component of the first control center SDK accesses the third invoked component of the control center APK based on a first access instruction. The third data invocation component of the control center APK, based on a third access instruction, accesses either the first invoked component of the first control center SDK or the second invoked component of the second control center SDK to execute callback operations for multi-device collaborative services. The second data invocation component of the second control center SDK accesses the third invoked component of the control center APK based on a second access instruction. The following is in conjunction with... Figures 7A-7C A detailed diagram illustrating how calls are implemented based on different access instructions.

[0103] See Figure 7AThis diagram illustrates a service access-based method provided in an embodiment of this application. The diagram shows a call between a control center APK and a first control center SDK. The method includes the following steps:

[0104] S701: Declare the first identifier in the system manifest file of the first control center SDK.

[0105] The system manifest file is the application manifest of the system, used to provide package names, descriptions of various application components, etc. For example, the AndroidManifest in the Android system is the system manifest file. In this embodiment, a first identifier, such as an authority instruction, needs to be declared in the system manifest file of the first control center SDK. Thus, when the system executes the business operation of the first service of the first electronic device and the second electronic device, it obtains the first identifier, generates a first access instruction, and accesses the first control center SDK corresponding to the business APK of the first service.

[0106] In one possible implementation, the first identifier declared in the system manifest file of the first control center SDK is "business APK package name" + "ControlCenterAARProvider". The business APK package name can also be represented as the application package name, which is the identifier corresponding to the first business declared in the system manifest file of the first control center SDK. Example explanation:

[0107] Table 1. Exemplary Mapping of First Service and First Identifier (i.e., First Access Instruction)

[0108]

[0109] Table 1 shows an exemplary mapping table of the first service and the first identifier (i.e., the first access instruction) provided in this application embodiment. Different services correspond to different application package names, different application package names correspond to different first identifiers, and different identifiers (exemplary authority) correspond to different first access instructions. This allows the control center APK to access different service APKs of the first service using different first access instructions, thus achieving accurate access to the service APK of the first service. The screen projection, keyboard and mouse system, and call collaboration in the table above are merely examples and are not limited to the above mapping relationship and the representation of the first identifier and first access instruction. Thus, based on the first access instruction, the corresponding service APK can be found. In Table 1 and other tables below, "ad" has no specific meaning and can be a phone name or other names; this application embodiment does not specifically limit "ad".

[0110] In one possible implementation, during the control center APK initialization phase, a mapping relationship between service IDs and service APK package names is pre-defined. Thus, when a user performs an operation on the first service of the first electronic device and the second electronic device, the service ID of the first service is obtained, and the service APK package name of the first service is determined based on the mapping relationship between the service ID and the service APK package name. Then, the first identifier is obtained based on the service APK package name.

[0111] Table 2 Mapping between Business ID and Application Package Name (related to Table 2)

[0112]

[0113] Refer to Table 2, which provides a mapping relationship between service IDs and application package names according to an embodiment of this application. The service ID is A.xxx.x, and the corresponding application package name is com.A. Thus, based on the application package name, the first identifier com.ad.A.ControlCenterAARProvider is obtained, and then the first access instruction Content: / / com.ad.A.ControlCenterAARProvider / train is obtained. Based on the first access instruction, the corresponding service APK, i.e., the service APK corresponding to service A, can be found. Specifically, when a user performs a service operation on the first electronic device and the second electronic device, the service ID is obtained as A. Based on the preset mapping relationship between service IDs and application package names, the application package name is determined to be com.ad.A. Based on the application package name, the first identifier com.ad.A.ControlCenterAARProvider can be obtained, and then the first access instruction Content: / / com.ad.A.ControlCenterAARProvider / train is generated. Based on the first access instruction, the corresponding service APK for the first service can be found. Those skilled in the art should understand that A.xxxx.x / B.xxxx. / C.xxx.x / D.xxx.x are merely exemplary representations of business IDs, and A / B / C / D are only business illustrations and do not represent specific businesses. The application package name format is only illustrative and can also be other formats; there are no specific restrictions on the application package name in this application embodiment. However, the business ID must have a pre-defined mapping relationship with the application package name, and the specific mapping form can be set as needed. In this way, the business side does not need to manually declare authority to obtain the first access instruction, reducing the probability of errors from manually declaring authority.

[0114] S702: When the user drags the second electronic device to the first electronic device, a first access command is obtained.

[0115] In one possible implementation, when a user drags a second electronic device to a first electronic device, the service ID of the first service is obtained. Based on the correspondence between the service ID and the application package name, the application package name corresponding to the first service can be determined, and then the first identifier corresponding to the first service can be determined, thereby determining the first access instruction.

[0116] S703: The control center APK accesses the service APK corresponding to the first service according to the first access instruction.

[0117] In this embodiment of the application, when a first access instruction for a first service is determined, the third data calling component of the control center APK calls the first called component of the first control center SDK of the service APK corresponding to the first service according to the first access instruction.

[0118] Thus, when one control center APK corresponds to multiple service APKs that integrate the control center SDK, different service APKs are distinguished through different access commands. The different access commands corresponding to the control center SDKs of different service APKs are pre-declared in the system manifest file. Therefore, when a user performs a collaborative service operation between the first electronic device and the second electronic device, the service APK corresponding to the first service is accurately located, resulting in high usability. Furthermore, the access commands provided in this embodiment do not require inheritance of ControlcenterAARProvider and do not require manual declaration of authority, offering good controllability and avoiding the probability of errors when the original logic is modified.

[0119] See Figure 7B This application also provides another schematic diagram based on business access. This diagram illustrates a call between the control center APK and the control center SDK. This method is mainly applied when the system is based on... Figure 7A This diagram illustrates how, after establishing a service connection for the first service, the service access is switched to the second service. Both the first and second services are device combinations composed of first and second electronic devices, capable of collaborative operation.

[0120] The method includes:

[0121] S801: When a user switches the first service of the first electronic device and the second electronic device to the second service, obtain the second identifier.

[0122] In this embodiment, the second identifier is an identifier corresponding to the second service, pre-declared in the system manifest file of the second control center SDK. For example, the second identifier is declared in the AndroidManifest file of the Android system. Thus, when a user switches from the first service of the first electronic device and the second electronic device to the second service, the second identifier of the second service is obtained, a second access instruction is generated, and the second control center SDK corresponding to the service APK of the second service is accessed.

[0123] In one possible implementation, the second identifier declared in the system manifest file of the second control center SDK is "Business APK Package Name" + "ControlCenterAARProvider". The Business APK Package Name can also be represented as the application package name, which is the identifier corresponding to the second business declared in the system manifest file of the second control center SDK. Example explanation:

[0124] Table 3. Exemplary Mapping of the Second Service and the Second Identifier (i.e., the Second Access Instruction)

[0125]

[0126] Table 3 shows an exemplary mapping table of the second service, the second identifier, and the second access instruction provided in this application embodiment. Different services correspond to different application package names, different application package names correspond to different second identifiers, and different second identifiers correspond to different second access instructions. This allows the control center APK to access the service APKs of different second services using different second access instructions, thereby achieving accurate access to the service APKs of the second services and accurately switching from the first service to the second service. The screen projection, keyboard and mouse system, and call collaboration in the table above are merely illustrative examples and are not limited to the mapping relationships and representations of the second identifiers and second access instructions described above. Thus, based on the second access instruction, the corresponding service APK, i.e., the service APK corresponding to service A, can be found.

[0127] In one possible implementation, during the control center APK initialization phase, a mapping relationship between service IDs and service APK package names is pre-defined. Thus, when a user switches from the first service to the second service on both the first and second electronic devices, the service ID of the second service is obtained. Based on the mapping relationship between the service ID and the service APK package name, the service APK package name of the second service is determined. Then, a second identifier is obtained based on the service APK package name. Example description:

[0128] Table 4 Mapping between Business ID and Application Package Name (related to Table 4)

[0129]

[0130] Refer to Table 4, which provides a mapping relationship between service IDs and application package names according to an embodiment of this application. The service ID is A.xxx.x, and the corresponding application package name is com.ad.A. Thus, based on the application package name, the second identifier, com.ad.A.ControlCenterAARProvider, is obtained, and then the second access instruction Content: / / com.ad.A.ControlCenterAARProvider / train is obtained. Thus, based on the second access instruction, the corresponding service APK, i.e., the service APK corresponding to service A, can be found. Specifically, when a user performs an operation to switch from the first service of the first electronic device to the second service of the second electronic device, the service ID of the second service is obtained as A.xxx.x. Based on the preset mapping relationship between service IDs and application package names, the application package name is determined to be com.ad.A. Based on the application package name, the second identifier com.ad.A.ControlCenterAARProvider can be obtained, and then the second access instruction Content: / / com.ad.A.ControlCenterAARProvider / train is generated. Thus, based on the second access instruction, the corresponding service APK of the second service can be found. Those skilled in the art should understand that A.xxxx.x / B.xxxx. / C.xxx.x / D.xxx.x are merely exemplary representations of business IDs, and A / B / C / D are only business illustrations and do not represent specific businesses. The application package name format is only illustrative and can also be other formats; there are no specific restrictions on the application package name in this application embodiment. However, the business ID must have a preset mapping relationship with the application package name, and the specific mapping form can be set as needed.

[0131] S802: The control center APK accesses the service APK corresponding to the second service according to the second access instruction.

[0132] In this embodiment of the application, when the second access instruction of the second service is determined, the third data calling component of the control center APK calls the second called component of the second control center SDK of the service APK corresponding to the second service according to the second access instruction.

[0133] Thus, when a user performs a business mode switching operation for the collaborative service between the first and second electronic devices, the corresponding service APK for the second service is accurately located, resulting in high usability. Furthermore, the access instructions provided in this embodiment do not require inheritance of ControlcenterAARProvider or manual declaration of authority, offering good controllability and avoiding errors when the original logic is modified. By declaring a second identifier in the system manifest of the control center SDK, the service side does not need to manually declare authority to obtain the second access instruction, reducing the probability of errors from manually declaring authority and enabling accurate switching from the first service to the second service.

[0134] See Figure 7C This is a schematic diagram illustrating the third service-based access method provided in this application embodiment. This method is mainly applied when the system is based on... Figure 7A After the business connection of the first service is established using this method, the control center APK calls back the business connection result of the first service. This method includes:

[0135] S901: After the business connection of the first business is established, the business APK of the first business obtains the third identifier and generates the third access instruction.

[0136] In this embodiment, the third identifier is an identifier declared in the system manifest file of the control center APK. This identifier indicates that the service APK of the first service can access the control center APK. For example, the third identifier is declared in the AndroidManifest file of the Android system. Thus, when a user performs a service operation on the first electronic device and the second electronic device, the control center APK calls back the result of the first service operation, obtains the third identifier, generates a third access instruction, and the service APK of the first service accesses the control center APK according to the third access instruction.

[0137] In one possible implementation, the third identifier declared in the system manifest file of the third control center SDK is "ControlcenterProvider". Example illustration:

[0138] Table 5. Exemplary Mapping of Third Identifiers and Third Access Instructions

[0139] Third sign Third access command ControlcenterProvider Content: / / ControlcenterProvider / train

[0140] Table 5 shows an exemplary mapping table of the third identifier and the third access instruction provided in the embodiments of this application. Since a device has only one control center APK, when accessing the service APK of the first service using the third access instruction, the third identifier can be set according to its own needs, such as "AAAA". However, it should be noted that the third identifier is different from the access instruction required for the control center APK to access the control center SDK. Thus, according to the third access instruction, the service APK of the first service can access the control center APK.

[0141] S902: The business APK of the first service accesses the control center APK according to the third access instruction.

[0142] In this embodiment of the application, after the third access instruction is generated, the first called component of the first control center SDK corresponding to the service APK of the first service calls the third data calling component corresponding to the control center APK according to the third access instruction.

[0143] Thus, once the user completes the collaborative operation of the first service on the first and second electronic devices, the control center APK executes a callback of the collaborative operation result based on the third access instruction. This eliminates the need for access to the entire collaborative service to inherit from ControlcenterAARProvider or ControlcenterProvider, and avoids the need for manual declaration of authority, resulting in good controllability and reducing the probability of errors when the original logic is modified.

[0144] In addition, this application embodiment also provides a system for business access, which includes a business APK for collaborative business, a control center APK, and a first control center SDK.

[0145] This system enables the following: When a user performs a first service operation on a first electronic device and a second electronic device, the control center APK obtains a first identifier and generates a first access instruction containing the first identifier. The first identifier is a pre-declared identifier in the system manifest file of the first control center SDK, corresponding to the first service. Based on the first access instruction, the control center APK accesses the first control center SDK corresponding to the service APK of the first service, and then interacts with the service APK of the first service.

[0146] In one possible implementation, the first control center SDK is integrated into the business APK of the first service.

[0147] In one possible implementation, the first identifier includes the business APK package name of the first service and the name of the called component of the first control center SDK;

[0148] The control center APK is specifically used for: obtaining the service ID of the first service; determining the service APK package name of the first service based on the service ID of the first service and a preset mapping relationship between the service ID and the service APK package name; obtaining the first identifier based on the service APK package name; and generating the first access instruction based on the first identifier and a preset mapping relationship between the identifier and the access instruction.

[0149] The specific implementation of the above modules is the same as the business access method, so it will not be described again here.

[0150] In this way, through this business access system, different first access instructions are generated based on different business identifiers, thereby enabling access to the correct business APK when a business layer includes multiple business APKs, so that collaborative business can proceed normally.

[0151] Through the above description of the embodiments, those skilled in the art will clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. The specific working process of the system, device, and unit described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0152] In the embodiments provided in this example, it should be understood that the disclosed systems and methods can be implemented in other ways. For example, the embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

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

[0154] Furthermore, in each embodiment of this invention, the functional units can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0155] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this embodiment, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments. The aforementioned storage medium includes various media capable of storing program code, such as flash memory, portable hard disk, read-only memory, random access memory, magnetic disk, or optical disk.

[0156] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for accessing services, characterized in that, The method is applied to a first electronic device, which has a collaborative service Android application package APK and a control center APK installed thereon. The control center APK is used to control the first electronic device to implement collaborative services through the collaborative service APK. The method includes: In response to a user performing a collaborative service operation on the first electronic device and the second electronic device to perform a first service through the control center APK, the control center APK obtains a first identifier and generates a first access instruction containing the first identifier; the first identifier is an identifier corresponding to the first service that is declared in advance in the system manifest file of the first control center software development kit (SDK). The control center APK accesses the first control center SDK corresponding to the service APK of the first service according to the first access instruction, and then accesses the service APK of the first service through the first control center SDK.

2. The method according to claim 1, characterized in that, The first control center SDK is integrated into the service APK of the first service.

3. The method according to claim 1, characterized in that, The first identifier includes the service APK package name of the first service and the name of the called component of the first control center SDK; The control center APK obtains a first identifier and generates a first access instruction containing the first identifier, including: Obtain the business ID of the first business; The business APK package name of the first service is determined based on the service ID of the first service and the preset mapping relationship between the service ID and the service APK package name. Obtain the first identifier based on the business APK package name; The first access instruction is generated based on the first identifier and the preset mapping relationship between identifiers and access instructions.

4. The method according to claim 1, characterized in that, When a user performs a collaborative service operation on the first electronic device and the second electronic device using the control center APK, the method further includes: The control center APK obtains the second identifier and generates a second access instruction containing the second identifier. The second identifier is an identifier that is declared in advance in the system manifest file of the second control center SDK and corresponds to the second service. The control center APK accesses the second control center SDK corresponding to the service APK of the second service according to the second access instruction, and then accesses the service APK of the second service through the second control center SDK to realize the collaborative service mode switching.

5. The method according to claim 4, characterized in that, The second identifier includes the service APK package name of the first service and the name of the called component of the second control center SDK; The control center APK obtains the second identifier and generates a second access instruction containing the second identifier, including: Obtain the business ID of the second service; Based on the service ID of the second service and the preset mapping relationship between the service ID and the service APK package name, obtain the second identifier; The second access instruction is generated based on the second identifier and the preset mapping relationship between identifiers and access instructions.

6. The method according to claim 1, characterized in that, The method further includes: The first service's APK obtains a third identifier and generates a third access instruction containing the third identifier; the third identifier is an identifier corresponding to the control center APK as declared in advance in the system manifest file of the control center APK. The first control center SDK accesses the control center APK according to the third access instruction, so as to enable the service APK of the first service to access the control center APK to execute the callback operation of the first service.

7. A system for accessing services, characterized in that, The system includes: The collaborative business Android application package APK, the control center APK, and the first control center software development kit SDK; When a user performs a collaborative service operation on a first electronic device and a second electronic device using the control center APK, the control center APK obtains a first identifier and generates a first access instruction containing the first identifier. The first identifier is an identifier corresponding to the first service, which is declared in advance in the system manifest file of the first control center software development kit (SDK). The control center APK accesses the first control center SDK corresponding to the service APK of the first service according to the first access instruction, and then accesses the service APK of the first service through the first control center SDK.

8. The system according to claim 7, characterized in that, The first control center SDK is integrated into the service APK of the first service.

9. The system according to claim 7, characterized in that, The first identifier includes the service APK package name of the first service and the name of the called component of the first control center SDK; The control center APK is specifically used for: obtaining the service ID of the first service; determining the service APK package name of the first service based on the service ID of the first service and a preset mapping relationship between the service ID and the service APK package name; and obtaining the first identifier based on the service APK package name. The first access instruction is generated based on the first identifier and the preset mapping relationship between identifiers and access instructions.

10. An electronic device, characterized in that, The electronic device includes: A memory and a processor, wherein the memory is coupled to the processor; The memory stores program instructions that, when executed by the processor, cause the electronic device to perform the method according to any one of claims 1-6.

11. A computer-readable storage medium, characterized in that, Includes computer-readable instructions that, when executed on a computing device, cause the computing device to perform the method of any one of claims 1-6.

Images