5G new call adaptation method, system and device compatible with multi-chip platform and medium

Abstract

The invention relates to the technical field of communication services, in particular to a 5G new call adaptation method, system and device compatible with a multi-chip platform and a medium. The method comprises the following steps: acquiring an IMS data channel request initiated by a user application layer through an AIDL interface; identifying the chip platform according to predefined IMS data channel information through a JNI reflection mechanism to obtain the type of the chip platform; loading a configuration file of the chip platform according to the type of the chip platform, and obtaining IMS data channel configuration parameters whether the IMS data channel configuration parameters support native creation or not; obtaining an adaptation strategy according to the IMS data channel configuration parameters and the IMS data channel request; creating an IMS data channel according to the adaptation strategy; and feeding back the data of the IMS data channel to the user application layer through the AIDL interface. According to the method, terminals of different manufacturers, models and chips can be flexibly connected.

Description

Technical Field

[0001] The present application relates to the field of communication service technology, and in particular to a 5G new call adaptation method, system, device and medium compatible with a multi-chip platform. Background Art

[0002] 5G New Calling refers to a series of services that enhance the user experience for individuals and businesses through system enhancements and service innovations based on carriers' IMS networks. 5G New Calling upgrades the user experience in interactive messaging and interaction during calls. The 5G New Calling network architecture builds on the IMS network architecture defined in 3GPP TS26.114 Release 18 by adding new network elements. Existing IMS network elements must also be upgraded to support new features such as data channels and third-party ID access. Implementing these new services requires support from both terminal and chipset manufacturers. Chipsets provide IMSDC channel capabilities, and terminal manufacturers must adapt these chipsets to implement IMSDC channel management and data transmission. However, 5G New Calling is still in its developmental stages, and the IMSDC interfaces and capabilities implemented by various chip vendors vary, requiring terminal manufacturers to tailor their chipset implementations.

[0003] In summary, the technical problems existing in the relevant technologies need to be improved. Summary of the Invention

[0004] The main purpose of the embodiments of this application is to propose a 5G new call adaptation method, system, device and medium that are compatible with multiple chip platforms, which can flexibly connect to terminals of different manufacturers, models and chips.

[0005] To achieve the above objectives, an embodiment of the present application provides a 5G new call adaptation method compatible with a multi-chip platform, the method comprising:

[0006] Get the IMS data channel request initiated by the user application layer through the AIDL interface;

[0007] Identify the chip platform according to the predefined IMS data channel information through the JNI reflection mechanism to obtain the chip platform type;

[0008] Load the configuration file of the chip platform according to the chip platform type to obtain whether the natively created IMS data channel configuration parameters are supported;

[0009] Obtaining an adaptation strategy according to the IMS data channel configuration parameters and the IMS data channel request;

[0010] Creating an IMS data channel according to the adaptation policy;

[0011] The data of the IMS data channel is fed back to the user application layer through the AIDL interface.

[0012] In some embodiments, the IMS data channel information includes an IMS data channel service name and an IMS data channel interface name;

[0013] The data of the IMS data channel includes the creation result of the IMS data channel, the status information of the IMS data channel, the data received by the IMS data channel and the status of the data sent by the IMS data channel.

[0014] In some embodiments, identifying the chip platform according to predefined IMS data channel information through the JNI reflection mechanism to obtain the chip platform type includes the following steps:

[0015] Traversing the interface implementation class through the JNI reflection mechanism;

[0016] Matching the interface implementation method in the interface implementation class based on the IMS data channel information;

[0017] The chip platform type is obtained by judging according to the calling result or exception type of the interface implementation method.

[0018] In some embodiments, the configuration file includes hardware capability parameters and interface call specifications;

[0019] The interface call specification includes the underlying protocol type and support identification;

[0020] Among them, the underlying protocol type is a combined protocol stack of SCTPoverDTLSoverUDP. In SCTPoverDTLS, DTLS is TLS encryption of UDP; the support identifier includes a support identifier of the DTLS encryption mode or a support identifier of the multi-stream transmission function.

[0021] In some embodiments, creating the IMS data channel according to the adaptation policy includes:

[0022] When native creation is supported, the IMS data channel is created through the chip adaptation strategy;

[0023] When native creation is not supported, the IMS data channel is created through a software simulation strategy.

[0024] In some embodiments, when native creation is supported, creating the IMS data channel through a chip adaptation strategy includes the following steps:

[0025] Creating a virtual IMS data channel as an interface proxy layer for the chip platform;

[0026] Calling the native interface provided by the chip platform through the JNI reflection mechanism;

[0027] The private interface of the chip platform is converted into a unified standardized interface through the virtual IMS data channel.

[0028] In some embodiments, when native creation is not supported, creating the IMS data channel through a software simulation strategy includes the following steps:

[0029] Dynamically load the protocol stack library in user space;

[0030] A logical channel is constructed based on the request type of the IMS data channel request to obtain an IMS data channel.

[0031] To achieve the above objectives, another aspect of the present application provides a 5G new call adaptation system compatible with a multi-chip platform, the system comprising:

[0032] A first module, which is used to obtain an IMS data channel request initiated by a user application layer through an AIDL interface;

[0033] A second module, configured to identify the chip platform according to predefined IMS data channel information through a JNI reflection mechanism to obtain a chip platform type;

[0034] A third module is used to load the configuration file of the chip platform according to the chip platform type, and obtain whether the natively created IMS data channel configuration parameters are supported;

[0035] A fourth module, configured to obtain an adaptation strategy according to the IMS data channel configuration parameters and the IMS data channel request;

[0036] A fifth module, configured to create an IMS data channel according to the adaptation policy;

[0037] The sixth module is configured to feed back the data of the IMS data channel to the user application layer through the AIDL interface.

[0038] To achieve the above objectives, one aspect of an embodiment of the present application provides a computer device, including:

[0039] at least one processor;

[0040] at least one memory for storing at least one program;

[0041] When the at least one program is executed by the at least one processor, the at least one processor implements the aforementioned method.

[0042] To achieve the above objectives, one aspect of an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method described above is implemented.

[0043] The embodiments of the present application include at least the following beneficial effects: The present application provides a 5G new call adaptation method, system, device and medium that are compatible with multiple chip platforms. The solution implements standardized cross-process communication between the user application layer and the background service through the AIDL interface to ensure efficient and stable data transmission. The chip platform type is dynamically identified with the help of the JNI reflection mechanism, and the corresponding parameters are loaded in combination with the configuration file to achieve automatic adaptation to different chip platforms. Based on the judgment of whether the chip platform supports native creation, the software simulation strategy or the chip platform adaptation strategy is flexibly adopted. When the chip platform does not support it, the channel function is simulated through the user space protocol stack. When the chip platform supports it, the native interface is called through the virtual channel agent, shielding the chip platform interface difference. The entire process realizes the full-link automated processing from request initiation, chip platform identification, policy decision-making to channel creation, which improves the compatibility and adaptation efficiency of the 5G new call system for multiple chip platforms and reduces development and maintenance costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 This is a flow chart of a 5G new call adaptation method compatible with a multi-chip platform provided in an embodiment of the present application;

[0045] Figure 2 yes Figure 1 Flowchart of step S200 in FIG.

[0046] Figure 3 yes Figure 1 Flowchart of step S500 in FIG.

[0047] Figure 4 This is a schematic diagram of a 5G new call adaptation system compatible with a multi-chip platform provided in an embodiment of the present application. DETAILED DESCRIPTION

[0048] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application is further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the embodiments of the present application. They are merely examples of devices and methods consistent with some aspects of the embodiments of the present application.

[0049] It will be understood that the terms "first", "second", etc. used in this application may be used herein to describe various concepts, but unless otherwise specified, these concepts are not limited by these terms. These terms are only used to distinguish one concept from another. For example, without departing from the scope of the embodiments of the present application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the words "if" and "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0050] The terms "at least one", "plurality", "each", "any", etc. used in this application include "at least one", "two" or more, "plurality" or "each", "any" or "any one", "each" or "any one" as used herein.

[0051] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this application pertains. The terms used herein are for the purpose of describing the embodiments of this application only and are not intended to limit this application.

[0052] Before explaining the embodiments of the present application in detail, some of the nouns and terms involved in the embodiments of the present application are first explained. The nouns and terms involved in the embodiments of the present application are subject to the following explanations.

[0053] SCTP: Stream Control Transmission Protocol, provides connection-oriented, multi-stream reliable transmission, suitable for real-time communication, supports multi-hosting and message framing;

[0054] DTLS: Datagram Transport Layer Security, which provides encryption and authentication for connectionless protocols such as UDP to ensure data transmission security;

[0055] UDP: User Datagram Protocol, connectionless, lightweight, high transmission efficiency but unreliable;

[0056] IMS network: A multimedia subsystem provided by operators that supports the integration of multimedia services such as voice and video;

[0057] JNI reflection mechanism: reflection technology of local interface, allowing code to dynamically call local code and resources at runtime;

[0058] IMS data channel: a logical channel for transmitting multimedia data in the IMS network;

[0059] AIDL interface: Android interface definition language, used to implement cross-process communication, allowing safe and efficient interaction between different application components;

[0060] TLS encryption: Transport Layer Security Protocol encryption is used to encrypt data during network transmission, ensuring the confidentiality, integrity and identity authentication of data between the communicating parties, and preventing data from being stolen or tampered with;

[0061] Application type: Based on WebRTC data channel technology, it uses SCTP stream ID starting from 1000 and is used for data transmission for 5G new call applications;

[0062] Bootstrap type: It is based on WebRTC data channel technology and uses reserved channels with SCTP stream IDs less than 1000. In 5G new calls, channels with IDs 0 and 100 are used to initialize 5G new call applications.

[0063] Figure 1 This is an optional flowchart of a 5G new call adaptation method compatible with a multi-chip platform provided in an embodiment of the present application. Figure 1 The method may include but is not limited to steps S100 to S600.

[0064] Step S100: obtaining an IMS data channel request initiated by the user application layer through the AIDL interface;

[0065] Step S200: Identify the chip platform based on the predefined IMS data channel information through the JNI reflection mechanism to obtain the chip platform type;

[0066] Step S300: Load the chip platform configuration file according to the chip platform type to obtain whether the natively created IMS data channel configuration parameters are supported;

[0067] Step S400: Obtaining an adaptation strategy based on IMS data channel configuration parameters and an IMS data channel request;

[0068] Step S500: Create an IMS data channel according to the adaptation policy;

[0069] Step S600: Feedback the data of the IMS data channel to the user application layer through the AIDL interface.

[0070] Specifically, the user application layer initiates an IMS data channel request to the background service through the AIDL interface. The background service dynamically identifies the chip platform type of the current device based on the predefined service name and interface name through the JNI reflection mechanism. Based on the type, the corresponding configuration file is loaded to obtain the configuration parameters of whether the chip platform supports native creation of IMS data channels. Combining the configuration parameters with the user request, the data channel management unit determines the adaptation strategy: if native creation is supported, a virtual channel proxy layer is created, and the chip platform native interface is called to implement the function; if not, the protocol stack library is dynamically loaded in the user space, and the channel function is implemented through software simulation. Finally, the created channel feeds back status information and data to the user application layer through the AIDL interface, forming a complete closed loop, realizing cross-chip platform 5G new call adaptation, and effectively shielding hardware differences.

[0071] In some embodiments, in step S100, the user application layer sends a request to create an IMS data channel to the background service through the AIDL interface, and the request includes the channel type, channel name, and channel transmission subprotocol. As a cross-process communication bridge, the AIDL interface passes the request from the user application layer to the IMS data channel management module to ensure the standardization and efficient transmission of the request. Among them, the user application layer includes applications such as call subtitles, intelligent translation, multi-screen interaction, or intelligent customer service voice calls; channel types include application type and bootstrap type. The channel transmission subprotocol refers to the data encapsulation protocol used for data transmission within the channel, such as http, or it can be a custom data encapsulation protocol.

[0072] In some embodiments, in step S200, Figure 2 As shown, Figure 2 yes Figure 1 The flowchart of step S200 in step S200 includes but is not limited to steps S210 to S230:

[0073] Step S210: traverse the interface implementation class through the JNI reflection mechanism;

[0074] Step S220: Matching the interface implementation method in the interface implementation class based on the IMS data channel information;

[0075] Step S230: Determine the chip platform type based on the call result or exception type of the interface implementation method.

[0076] Specifically, in steps S210 to S230, when the chip platform type identification process is initiated using the JNI reflection mechanism, JNI technology is first used to break through the call boundary between the Java and Native layers, dynamically traversing all loaded interface implementation classes in the process at runtime. These classes are typically provided by the chip platform vendor and encapsulate the implementation logic for specific hardware functions. During this traversal, based on predefined IMS data channel information, the interface implementation methods related to the IMS data channel are precisely matched within the interface implementation class. Subsequently, reflection is attempted to call these methods, and the execution results or exception types are captured. Interface implementations vary across chip platforms. Successful calls to specific methods may return vendor-specific values, while failed calls may throw exceptions that indirectly reflect the chip platform type. Using a predefined set of matching rules, these call results or exception types are mapped to specific chip platform types, completing dynamic identification of the chip platform and providing a foundation for subsequent loading of the adaptation configuration. The predefined IMS data channel information includes the IMS data channel service name and the IMS data channel interface name. The interface implementation method refers to the specific functional implementation code written in the interface implementation class by the chip platform vendor or developer for the IMS data channel function. These methods are based on the characteristics of the chip platform and encapsulate the underlying hardware operation logic, such as core functions such as channel creation or data transmission and reception.

[0077] In some embodiments, in step S300, after determining the chip platform type, the configuration file of the corresponding manufacturer is loaded from a preset configuration directory. These configuration files are predefined by the chip platform manufacturer or device manufacturer and contain hardware capability parameters and interface call specifications. The hardware capability parameters include the encryption suite supported by DTLS, the maximum number of media supported by the DC protocol stack, the maximum number of channels, the SCTP port range, and the SCTP transmission buffer size; the interface call specification includes the underlying protocol type and the support identifier. The underlying protocol type is a combined protocol stack of SCTPoverDTLSoverUDP. In SCTPoverDTLS, DTLS is TLS encryption for UDP. The support identifier includes the support identifier of the DTLS encryption mode or the support identifier of the multi-stream transmission function.

[0078] Specifically, after determining the chip platform type, the corresponding vendor configuration file is loaded from a preset configuration directory. This file is predefined by the chip vendor or device manufacturer. The hardware capability parameters in this file align with the actual requirements of 5G new calls: DTLS supports cipher suites including null encryption and standard encryption modes. Null encryption is equivalent to no encryption, allowing users to choose whether to encrypt transmission. The SCTP port range limits the port range for channel communication to avoid port conflicts. The SCTP transmit buffer size affects the buffer capacity for data transmission and reception, affecting transmission efficiency and stability. These parameters, combined with the characteristics of the SCTP over DTLS over UDP combined protocol stack, provide a key basis for adaptation strategies, ensuring that chip capabilities match protocol requirements and achieving efficient compatibility across multiple chip platforms. In the SCTP over DTLS over UDP combined protocol stack, UDP serves as the underlying transport protocol, providing lightweight datagram services. DTLS performs TLS encryption on UDP data to ensure data transmission security. DTLS can also enable unencrypted transmission in scenarios with lower security requirements or special circumstances, improving transmission efficiency or facilitating commissioning. SCTP, built on DTLS, is responsible for implementing multi-stream transmission and reliable connections. The support flag in the configuration file is used to clarify the chip's support for multi-stream transmission functions and DTLS encryption mode. This allows the system to select appropriate protocol configuration parameters based on the chip platform type and user requests through chip adaptation strategies or software simulation strategies, ensuring efficient and secure 5G new call services on different chips, ultimately achieving the goal of multi-chip compatibility. It is understandable that in 5G new calls, the IMS data channel uses the SCTPoverDTLSoverUDP combined protocol stack to achieve reliable data transmission and secure encryption, and is the direct carrier of the transmission protocol. At the same time, the configuration file identifies chip capabilities, dynamically switches adaptation strategies, and standardizes chip private interfaces, thereby achieving compatibility with different chip platforms and becoming an adaptation bridge that shields hardware differences.

[0079] In some embodiments, in step S400, after obtaining the configuration parameters of whether the chip platform supports native creation of IMS data channels, a multi-dimensional policy decision is made in combination with the content of the IMS data channel request initiated by the user, such as channel type, service quality requirements or security level. If the configuration parameters indicate that the chip platform supports native creation and the requested functional characteristics are within the capabilities of the chip platform, the "chip adaptation strategy" will be selected to achieve efficient channel creation by calling the native interface of the chip platform; on the contrary, if the chip platform does not support native creation or the requested function exceeds the capabilities of the chip platform, such as requiring a DTLS version that is not supported by the hardware, the "software simulation strategy" will be started to dynamically load the protocol stack library in the user space and simulate the channel function in a pure software manner. Performance optimization factors will also be considered in the decision-making process. For example, when there are known compatibility issues with the native interface of the chip platform, even if native creation is supported, it may be downgraded to use the software simulation strategy to ensure stability. The final generated adaptation strategy clarifies the technical path for channel creation and provides an execution basis for subsequent steps.

[0080] In some embodiments, as Figure 3 As shown, Figure 3 yes Figure 1 Flowchart of step S500, Figure 1 Step S500 includes but is not limited to steps S510 to S520:

[0081] Step S510: When native creation is supported, an IMS data channel is created using the chip adaptation policy;

[0082] Step S520: When native creation is not supported, an IMS data channel is created through a software simulation strategy.

[0083] Specifically, in steps S510 to S520, after determining the adaptation strategy, differentiated channel creation logic is executed based on whether the chip platform supports native IMS data channel creation. If the chip platform supports native creation, the chip adaptation strategy is adopted. If the chip platform does not support native creation, the software emulation strategy is enabled.

[0084] When using the chip adaptation strategy to create an IMS data channel, a virtual IMS data channel is first created in user space as a proxy layer for the chip platform interface. This proxy layer plays the role of an intermediate conversion. Through the JNI reflection mechanism, the native interface library provided by the chip platform manufacturer is dynamically loaded, the standardized channel creation request is converted into a chip platform-specific instruction format, and the chip platform native interface is called to complete the initialization of the physical channel. During the data flow process, the virtual channel continuously monitors the chip platform interface status, parses the private status code returned by the chip platform into a unified standardized status, and maps the general operation instructions of the upper-level application into low-level calls that can be recognized by the chip platform, thereby realizing standardized encapsulation of the private interfaces of different chip platforms. This allows upper-level applications to complete channel management and data transmission through a unified interface without having to perceive the specific chip platform model, effectively shielding the heterogeneous differences between chip platforms.

[0085] When using a software simulation strategy to create an IMS data channel, the pre-compiled protocol stack library is first dynamically loaded into the user space. These libraries are independent of the native interface of the chip platform and implement the protocol logic in a pure software manner. After loading, based on the type of IMS data channel request initiated by the user, the protocol components with corresponding functions, such as the SCTP flow controller and the DTLS encryption module, are instantiated from the protocol stack library, and the component behavior is configured according to the parameters in the request. Subsequently, a logical channel is constructed in memory using these components. This channel simulates the functions of a real hardware channel, including mechanisms such as data segmentation, reliable transmission, and error recovery. For example, for file transfer requests with high reliability requirements, the multi-stream feature and retransmission mechanism of SCTP are enabled. Ultimately, these protocol components work together to form a complete IMS data channel, which is implemented entirely in user space without relying on the native capabilities of the chip platform, ensuring that consistent 5G new call services can still be provided on chip platforms that do not support native creation.

[0086] In some embodiments, in step S600, after the IMS data channel is created and initialized, the channel data is fed back to the user application layer via the AIDL interface. During this process, the IMS data channel data fed back includes: the IMS data channel creation result, presented as a Boolean value combined with a status code, such as "SUCCESS" or "ERROR_CHIP_INCOMPATIBLE," clearly indicating whether the channel was successfully established; IMS data channel status information, including real-time connection status, such as "CONNECTED" or "DISCONNECTED," transmission performance metrics, such as current bandwidth and packet loss rate, and quality of service parameters, such as latency or jitter. In addition, the IMS data channel data also includes the status of data received and data sent by the IMS data channel. The AIDL interface encapsulates this data into a Parcelable object that can be transferred across processes and passed to the user application layer via the Binder mechanism. Upon receiving this feedback, the user application layer updates the UI display based on the feedback, such as displaying a "Channel Disconnected" or "Poor Network Quality" prompt, and triggers corresponding service logic, such as automatically reestablishing the channel or reducing the service data transmission rate. The entire feedback process is implemented through AIDL's asynchronous callback mechanism, ensuring that status changes can be notified to users in real time, forming a complete closed loop from request to response, and improving the interactive experience and reliability of 5G new calls.

[0087] In some embodiments, a 5G new call adaptation method compatible with a multi-chip platform includes a UI layer, an AIDL layer, a configuration unit, and a data channel management unit. Among them, the UI layer is a call application, which is modified based on the traditional call application and supports 5G new calls based on IMSDC. The AIDL layer provides an AIDL interface to the UI layer for the 5G new call protocol stack. The UI module calls the AIDL interface of the 5G new call background service, calls to create an IMS data channel, monitors the status of the IMS data channel, and sends and receives data through the IMS data channel. The configuration unit is used to obtain chip platform-related configuration parameters, mainly including whether the chip platform supports the creation of an IMS data channel.

[0088] The data channel management unit, when the chip platform does not support IMS data channel creation, implements the IMS data channel protocol, enabling IMS data channel creation, management, sending user data, and receiving data from the server. Specifically, when the chip platform does not support IMS data channels, this solution implements the IMS data channel protocol, tailored from the Google WebRTC library, to generate relevant data channel parameters, including port and TLS ID, and then connects to the chip platform. The chip platform implements SIP signaling negotiation, including port, IP address, data channel type, name, and QoS, obtaining the other party's data channel parameters and sending its own data channel parameters. This solution uses the chip platform's interface to obtain or set these parameters and then creates and manages the data channel. When the chip platform supports IMS data channel creation, a virtual IMS data channel is created to connect to the chip platform. The chip platform's interface is used to implement IMS data channel creation, management, and data transmission and reception, thus masking the differences between chip platforms.

[0089] In some embodiments, a 5G new call adaptation method compatible with multiple chip platforms includes: since the IMS data channel service names and interfaces of each chip platform are different, different chip platforms are judged through the JNI reflection mechanism according to the service name and interface name of the IMS data channel; the corresponding configuration file is loaded according to the chip platform, the type of the IMS data channel is obtained, where the type indicates whether it is created by the chip platform, and an IMS data channel management layer instance is created for the corresponding chip platform; when the chip platform does not support IMS data channel creation, it is used to implement the IMS data channel protocol, implement IMS data channel creation, management, sending user data and receiving data sent by the server and other functions; when the chip platform supports IMS data channel creation, create a virtual IMS data channel to connect to the chip platform, and implement IMS data channel creation, management and data transmission and reception and other functions by calling the chip platform interface, thereby shielding the differences between chip platforms.

[0090] In some embodiments, as Figure 4 As shown, Figure 4 This is a schematic diagram of a 5G new call adaptation system compatible with a multi-chip platform. The system includes:

[0091] The first module is used to obtain the IMS data channel request initiated by the user application layer through the AIDL interface;

[0092] The second module is used to identify the chip platform according to the predefined IMS data channel information through the JNI reflection mechanism to obtain the chip platform type;

[0093] The third module is used to load the chip platform configuration file according to the chip platform type and obtain whether the natively created IMS data channel configuration parameters are supported;

[0094] The fourth module is used to obtain an adaptation strategy according to the IMS data channel configuration parameters and the IMS data channel request;

[0095] The fifth module is used to create an IMS data channel according to the adaptation policy;

[0096] The sixth module is used to feed back the data of the IMS data channel to the user application layer through the AIDL interface.

[0097] It can be understood that the contents of the above method embodiments are all applicable to the present system embodiments, the functions specifically implemented by the present system embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0098] The present application also provides a computer processing device comprising a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the aforementioned 5G new call adaptation method compatible with a multi-chip platform. The electronic device can be any smart terminal, including a tablet computer and an in-vehicle computer.

[0099] It can be understood that the contents of the above method embodiments are all applicable to the present device embodiments, the functions specifically implemented by the present device embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0100] An embodiment of the present application also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the above-mentioned 5G new call adaptation method compatible with a multi-chip platform.

[0101] It can be understood that the contents of the above method embodiments are all applicable to the present storage medium embodiment, the functions specifically implemented by the present storage medium embodiment are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0102] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may optionally include a memory remotely arranged relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0103] The embodiments described in the embodiments of this application are intended to more clearly illustrate the technical solutions of the embodiments of this application and do not constitute a limitation on the technical solutions provided by the embodiments of this application. Those skilled in the art will appreciate that with the evolution of technology and the emergence of new application scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0104] Those skilled in the art will understand that the technical solutions shown in the figures do not constitute a limitation on the embodiments of the present application, and may include more or fewer steps than shown in the figures, or a combination of certain steps, or different steps.

[0105] The terms "first", "second", "third", "fourth", etc. (if any) in the specification of the present application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0106] It should be understood that in this application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0107] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the above-mentioned units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0108] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0109] The integrated unit can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, 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, which is stored in a storage medium and includes multiple instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of various embodiments of the present application. The aforementioned storage medium includes: various media that can store programs, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0110] The preferred embodiments of the present invention are described above with reference to the accompanying drawings, but are not intended to limit the scope of the present invention. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and essence of the present invention should be within the scope of the present invention.

Claims

1. A 5G new call adaptation method compatible with a multi-chip platform, characterized in that: The method comprises: Get the IMS data channel request initiated by the user application layer through the AIDL interface; Identify the chip platform according to the predefined IMS data channel information through the JNI reflection mechanism to obtain the chip platform type; Load the configuration file of the chip platform according to the chip platform type to obtain whether the natively created IMS data channel configuration parameters are supported; Obtaining an adaptation strategy according to the IMS data channel configuration parameters and the IMS data channel request; Creating an IMS data channel according to the adaptation policy; The data of the IMS data channel is fed back to the user application layer through the AIDL interface.

2. The method according to claim 1, characterized in that The IMS data channel information includes an IMS data channel service name and an IMS data channel interface name; The data of the IMS data channel includes the creation result of the IMS data channel, the status information of the IMS data channel, the data received by the IMS data channel and the status of the data sent by the IMS data channel.

3. The method according to claim 1, characterized in that The method of identifying the chip platform according to the predefined IMS data channel information through the JNI reflection mechanism to obtain the chip platform type includes the following steps: Traversing the interface implementation class through the JNI reflection mechanism; Matching the interface implementation method in the interface implementation class based on the IMS data channel information; The chip platform type is obtained by judging according to the calling result or exception type of the interface implementation method.

4. The method according to claim 1, wherein The configuration file includes hardware capability parameters and interface call specifications; The interface call specification includes the underlying protocol type and support identification; Among them, the underlying protocol type is a combined protocol stack of SCTPoverDTLSoverUDP. In SCTPoverDTLS, DTLS is TLS encryption of UDP; the support identifier includes a support identifier of the DTLS encryption mode or a support identifier of the multi-stream transmission function.

5. The method according to claim 1, wherein The creating of the IMS data channel according to the adaptation policy includes: When native creation is supported, the IMS data channel is created through the chip adaptation strategy; When native creation is not supported, the IMS data channel is created through a software simulation strategy.

6. The method according to claim 5, characterized in that When native creation is supported, creating the IMS data channel through a chip adaptation strategy includes the following steps: Creating a virtual IMS data channel as an interface proxy layer for the chip platform; Calling the native interface provided by the chip platform through the JNI reflection mechanism; The private interface of the chip platform is converted into a unified standardized interface through the virtual IMS data channel.

7. The method according to claim 5, characterized in that When native creation is not supported, creating the IMS data channel through a software simulation strategy includes the following steps: Dynamically load the protocol stack library in user space; A logical channel is constructed based on the request type of the IMS data channel request to obtain an IMS data channel.

8. A 5G new call adaptation system compatible with a multi-chip platform, characterized in that: The system comprises: A first module, which is used to obtain an IMS data channel request initiated by a user application layer through an AIDL interface; A second module, configured to identify the chip platform according to predefined IMS data channel information through a JNI reflection mechanism to obtain a chip platform type; A third module is used to load the configuration file of the chip platform according to the chip platform type, and obtain whether the natively created IMS data channel configuration parameters are supported; A fourth module, configured to obtain an adaptation strategy according to the IMS data channel configuration parameters and the IMS data channel request; A fifth module, configured to create an IMS data channel according to the adaptation policy; The sixth module is configured to feed back the data of the IMS data channel to the user application layer through the AIDL interface.

9. A computer device, characterized in that: include: at least one processor; at least one memory for storing at least one program; When the at least one program is executed by the at least one processor, the at least one processor implements the method according to any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images