Call service processing method and device, computer equipment and readable storage medium

Abstract

The invention relates to the technical field of communication, in particular to a call service processing method and device, computer equipment and a readable storage medium. The method comprises the following steps: acquiring a call service request initiated by a user on a user interface (UI) through an outer layer; wherein the UI is generated by an outer layer according to interaction configuration information provided by a developer; processing the call service request through a target call function integrated in an internal processing layer to obtain a response result of the call service; and the response result is returned to the UI by the outer layer, so that the user executes the corresponding call operation according to the response result.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a call service processing method, device, computer equipment and readable storage medium. Background Art

[0002] In the current technological environment, the fifth generation mobile communication technology (5th generation wireless systems, 5G) new call technology has huge development potential and can bring users a better communication experience.

[0003] At present, the UI style design under the 5G new call code framework is fixed.

[0004] However, different terminal manufacturers have their own unique products. The existing 5G new call UI style design is fixed and cannot meet the UI customization requirements of each terminal manufacturer. Summary of the invention

[0005] Based on this, it is necessary to provide a call service processing method, device, computer equipment and readable storage medium that can be customized by UI to address the above technical problems.

[0006] In a first aspect, the present application provides a call service processing method, the method comprising:

[0007] Obtaining the call service request initiated by the user on the user interface UI through the external layer; wherein the UI is generated by the external layer according to the interactive configuration information provided by the developer;

[0008] The call service request is processed through the target call function integrated in the internal processing layer to obtain the response result of the call service;

[0009] By returning the response result to the UI, the user can perform corresponding call operations based on the response result.

[0010] In one embodiment, the call service request is processed by the target call function integrated in the internal processing layer to obtain a response result of the call service, including:

[0011] Determine the target call function and the calling logic of the target call function required by the call service request through the use case layer in the internal processing layer;

[0012] Through the management layer in the internal processing layer, the target call function is executed according to the calling logic of the target call function;

[0013] In the process of executing the target call function, the external interface layer corresponding to the call service request in the internal processing layer communicates with the outside to obtain a response result of the call service request.

[0014] In one embodiment, the target call function and the calling logic of the target call function required for the call service request are determined through the use case layer in the internal processing layer, including:

[0015] Parse the call service request to obtain the service scenario and call requirements;

[0016] Through the use case layer in the internal processing layer, the target call function and the calling logic of the target call function corresponding to the business scenario and call requirements are determined from the candidate call functions in the function mapping table.

[0017] In one embodiment, the external layer includes a view layer and a view model layer; the UI is generated by the view layer according to the interaction configuration information provided by the developer; the interaction configuration information includes interface configuration parameters and device display parameters;

[0018] The call service request initiated by the user on the user interface UI is obtained from the external layer, including:

[0019] Obtain the call service request initiated by the user on the user interface UI through the view layer;

[0020] Through the view model layer, the business logic interface is called to transmit the call business request to the use case layer in the internal processing layer.

[0021] In one of the embodiments, the business logic interface is obtained by the use case layer according to the target call function and the logical encapsulation of the target call function.

[0022] In one embodiment, the response result is returned to the UI by the external layer, including:

[0023] The response result is formatted through the view model layer and returned to the UI.

[0024] In a second aspect, the present application further provides a call service processing device, including:

[0025] The UI interaction module is used to obtain the call service request initiated by the user on the user interface UI through the external layer; wherein the UI is generated by the external layer according to the interaction configuration information provided by the developer;

[0026] The call processing module is used to process the call service request through the target call function integrated in the internal processing layer to obtain the response result of the call service;

[0027] The feedback module is used to return the response result to the UI through the external layer, so that the user can perform corresponding call operations according to the response result.

[0028] In a third aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0029] Obtaining the call service request initiated by the user on the user interface UI through the external layer; wherein the UI is generated by the external layer according to the interactive configuration information provided by the developer;

[0030] The call service request is processed through the target call function integrated in the internal processing layer to obtain the response result of the call service;

[0031] By returning the response result to the UI, the user can perform corresponding call operations based on the response result.

[0032] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the following steps are implemented:

[0033] Obtaining the call service request initiated by the user on the user interface UI through the external layer; wherein the UI is generated by the external layer according to the interactive configuration information provided by the developer;

[0034] The call service request is processed through the target call function integrated in the internal processing layer to obtain the response result of the call service;

[0035] By returning the response result to the UI, the user can perform corresponding call operations based on the response result.

[0036] In a fifth aspect, the present application further provides a computer program product, including a computer program, which implements the following steps when executed by a processor:

[0037] Obtaining the call service request initiated by the user on the user interface UI through the external layer; wherein the UI is generated by the external layer according to the interactive configuration information provided by the developer;

[0038] The call service request is processed through the target call function integrated in the internal processing layer to obtain the response result of the call service;

[0039] By returning the response result to the UI, the user can perform corresponding call operations based on the response result.

[0040] The above-mentioned call service processing method, device, computer equipment and readable storage medium, in this application, the UI is generated by the external layer based on the interactive configuration information provided by the developer, so that the developer can customize the diverse UI layouts and behaviors according to the needs and preferences of different user groups. The layered architecture of the external layer and the internal processing layer separates the business logic from the interface display, and the responsibilities of each layer are clear. The external layer, as the visual part of the user interface, is only responsible for displaying data and interacting with users, and does not involve complex business logic. This allows terminal manufacturers to customize the external layer according to their own needs, change the layout, color, interaction method, etc. of the interface, without affecting the business logic implementation of other layers. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0042] Figure 1 A flowchart of a call service processing method in one embodiment;

[0043] Figure 2 A flowchart of steps for processing a call service request by a target call function integrated in an internal processing layer in one embodiment;

[0044] Figure 3 A flowchart of determining a target call function required for a call service request and a logic step of calling the target call function in one embodiment;

[0045] Figure 4 It is a flowchart of the steps of obtaining a call service request initiated by a user on a user interface UI through an external layer in one embodiment;

[0046] Figure 5 It is a schematic diagram of a 5G new call UI open source framework based on the clean framework in another embodiment;

[0047] Figure 6 is a structural block diagram of a call service processing device in an embodiment;

[0048] Figure 7 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0049] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0050] Clean framework: This is a software design architecture whose core idea is that the dependency direction of program code is unidirectional. Specifically, the outer layer depends on the inner layer, the outer layer code can access the inner layer, but the inner layer code cannot access the outer layer, and the data format and code structure of the outer layer will not affect the inner layer. This architecture helps to achieve clear layering and decoupling of code, and improve the maintainability and scalability of the software.

[0051] 5G New Calling: It is a general term for a series of services based on the operator's IMS network enhancement and business innovation, aiming to improve the experience of individual and enterprise industry users.

[0052] UI: User Interface. As the medium for interaction between people and information, it is the carrier of information product functions. It has distinct characteristics and directly affects the interaction experience between users and products.

[0053] Open source: means that the software code can be publicly accessed. Within the prescribed scope, community members can modify and share it, making it possible for multi-party collaborative development and customization.

[0054] In an exemplary embodiment, Figure 1 As shown, a call service processing method is provided, and the method is applied to a terminal device as an example for explanation. The terminal device can process the external layer and the internal layer, including:

[0055] S101, obtaining a call service request initiated by a user on a user interface UI through an external layer.

[0056] Among them, the external layer plays a key role in the entire architecture in direct interaction with users. It is not only responsible for generating the UI interface that users see and interact with, but also bears the responsibility of receiving call service requests initiated by users. From the perspective of user experience, the external layer is like a bridge between users and the system. Users use it to express their needs (such as initiating a call) and the system perceives the user's operations.

[0057] Optionally, refer to the layered design concept of the Clean architecture. Here, the external layer can be compared to the framework and driver layers. In the Clean architecture, different layers have clear division of responsibilities and one-way dependencies. The external layer corresponds to the framework and driver layer, which means that it is at the boundary of interaction with the external environment (mainly users here), responsible for introducing external input (user requests) into the internal layer, and feeding back the internal processing results to the external layer (displayed through the UI).

[0058] Furthermore, the UI is generated by the external layer based on the interactive configuration information provided by the developer. This approach makes the design and generation of the UI highly flexible and customizable. The developer provides the configuration in a specific format (such as JSON or YAML files), and these configuration files define the layout and behavior of the UI in detail. For example, in a JSON file, the layer relationship, position, size, style and other layout information of the interface elements can be described through nested objects and array structures, and behavioral information such as the response action after a button click and the page switching logic can also be defined.

[0059] This way of defining the UI through configuration files is fully in line with the open source concept. Open source means that the software code and related design resources (such as the UI configuration files here) are publicly accessible, and community members can modify and share them within the prescribed scope. This not only promotes collaboration among developers in the community, but also allows different developers to optimize, expand or customize the existing UI configuration to meet different application scenarios and user needs.

[0060] It is understandable that the call service requests initiated by users may not be limited to traditional voice or video calls, but may also include requirements for 5G enhanced functions such as high-definition video, screen sharing, and AR (augmented reality). With the development of 5G technology, these functions have gradually become advanced features that users expect to use during calls. The high-definition video function can provide a clearer and smoother video call experience; the screen sharing function allows users to share the content on their mobile phone or computer screen during a call, which is suitable for scenarios such as remote collaboration and teaching; the AR function can add virtual augmented reality elements to users during a call, such as virtual props and scenes, to increase the fun and interactivity of the call.

[0061] S102, processing the call service request through the target call function integrated in the internal processing layer to obtain a response result of the call service.

[0062] Among them, the internal processing layer is a key layer in the entire architecture responsible for processing various business logics. In this layer, a variety of modules related to core functions are integrated, just like a "central brain" that specializes in processing various input requests and outputting corresponding results. It brings together different functional modules to achieve orderly processing of various business requests.

[0063] Among them, the target call function is a set of functions in the internal processing layer that is specifically designed for call services. It includes a series of logical operations required to implement call services, such as establishing call connections, verifying user permissions, allocating communication resources, and other specific functions. These functions work together to ensure that call services can proceed smoothly.

[0064] Optionally, during the communication process, a call service request may be received from the outside (may be initiated by the user through the terminal device, or may be transmitted from other modules). This request contains various information required to initiate a call, such as the calling number, called number, call type (voice call, video call, etc.) and other related parameters.

[0065] Once the internal processing layer receives a call service request, the integrated target call function begins to work. The target call function analyzes, verifies, and processes the information in the request according to the preset business logic and algorithm. For example, first verify whether the calling user has the authority to initiate the call, check whether there are sufficient resources to support the call, etc. If the verification is successful, the target call function will call the corresponding sub-function module to establish a call connection and conduct communication negotiation with the called party.

[0066] After a series of processing of the call service request by the target call function, a response result for the request will be generated. This response result will vary depending on the processing situation. If the call service request is successfully processed, the response result may contain information about the successful establishment of the call, such as the call connection identifier, communication quality parameters, etc., which can be used for subsequent call process control and display. If a problem occurs during the processing, such as the called number does not exist, insufficient resources, etc., the response result will contain corresponding error information, such as error code, error description, etc. This information can help or users understand the reason for the failure of the call service request so that corresponding measures can be taken, such as prompting the user to re-operate or perform maintenance, etc.

[0067] S103, returning the response result to the UI through the external layer, so that the user can perform corresponding call operations according to the response result.

[0068] Optionally, the external layer acts as a direct interface for interacting with the user and is responsible for delivering the response results from the internal processing layer to the UI.

[0069] For example, after the UI receives the response result from the external layer, it will be displayed to the user in a visual way. This display process is not a simple information presentation, but is carefully designed to guide users to perform corresponding call operations based on the response results. For example, if the response result is a successful call request, the UI may display a prompt message "Call connected" and provide relevant call operation buttons such as start video and mute; if the response result is a call failure, the UI may display the specific reason for the failure (such as "the other party is busy" or "network connection failed"), and may provide operation options such as "retry" or "return". Through this intuitive display method, users can clearly understand the processing status of the call service and perform the next step according to the prompts.

[0070] In the above-mentioned call service processing method, the UI in this application is generated by the external layer based on the interactive configuration information provided by the developer, so that the developer can customize diverse UI layouts and behaviors according to the needs and preferences of different user groups. The layered architecture of the external layer and the internal processing layer separates the business logic from the interface display, and the responsibilities of each layer are clear. The external layer, as the visual part of the user interface, is only responsible for displaying data and interacting with users, and does not involve complex business logic. This allows terminal manufacturers to customize the external layer according to their own needs, change the interface layout, color, interaction method, etc., without affecting the business logic implementation of other layers.

[0071] In an exemplary embodiment, Figure 2 As shown, the call service request is processed by the target call function integrated in the internal processing layer to obtain the response result of the call service, including:

[0072] S201, determining the target call function and the calling logic of the target call function required by the call service request through the use case layer in the internal processing layer.

[0073] It is understandable that the UseCase layer is responsible for integrating and encapsulating the logical functions of the new 5G call service. The UseCase layer includes multiple use cases, such as screen sharing case, IMS call case, markup board case, and permission management case. The specific implementation method is to re-integrate the functional interfaces encapsulated by the Manager layer.

[0074] For example, in a business scenario involving screen sharing and IMS calls, the UseCase layer will reasonably combine the screen sharing interface and IMS call interface provided by the Manager layer to form a logical interface for the business scenario. This business scenario logical interface is directly called by the external layer, allowing the external layer to easily trigger and manage complex business logic, realizing the modularization and reuse of business logic, and improving development efficiency and maintainability.

[0075] Optionally, after receiving a call service request initiated by the user on the UI, the UseCase layer will perform a detailed analysis of the request. For example, if the user initiates a video call request that includes a screen sharing function, the UseCase layer will identify the key business elements involved in the request, namely, the video call (based on the IMS call function) and screen sharing. Based on the analysis results of the call service request, the UseCase layer determines the target call function required to complete the request. In the above example, the target call function is the IMS call function and the screen sharing function. These functions have been encapsulated into independent interfaces in the Manager layer of the internal processing layer, and the UseCase layer only needs to identify them.

[0076] In addition to determining the target call function, the UseCase layer also needs to clarify the order and method of calling these functions, that is, the calling logic. In the video call scenario of screen sharing, it is usually necessary to establish an IMS call connection first to ensure that both parties can conduct basic voice and video communications, and then enable the screen sharing function. Therefore, the calling logic may be to first call the IMS call interface of the Manager layer to establish a connection, and then call the screen sharing interface to start screen sharing after the connection is successful.

[0077] S202, executing the target call function according to the calling logic of the target call function through the management layer in the internal processing layer.

[0078] It is understandable that the Manager layer is responsible for encapsulating the single functions of the new 5G call. This includes the encapsulation of the screen sharing function, which ensures that the screen sharing operation has a unified calling method and management logic throughout; the encapsulation of the IMS call function, which handles specific operations related to IMS network calls; the encapsulation of the mark drawing board function, which facilitates the implementation of functions such as marking and annotation during the call; and the encapsulation of the permission management function, which ensures that the use of the function complies with the permission settings.

[0079] The Manager layer includes multiple Manager classes. Each Manager class is actually a re-encapsulation of the internal layer - external interface layer. It integrates and abstracts the basic functions provided by the external interface layer and provides these functions to the UseCase layer in the form of interfaces. The advantage of this is that the UseCase layer does not need to care about the specific implementation details of the external interface layer. It only needs to call the interface provided by the Manager layer to implement specific logic execution, which further improves the modularity and maintainability of the code.

[0080] Optionally, the Manager layer finds the corresponding Manager class based on the received target call function information. For example, if the target call function is screen sharing, the Manager layer will locate the Manager class responsible for encapsulating the screen sharing function. According to the calling logic, the interfaces provided by the corresponding Manager class are called in sequence. Taking the establishment of an IMS call connection as an example, the Manager layer will call the "establish connection" interface in the Manager class encapsulating the IMS call function, send a call request to the IMS network, and complete the establishment of the call connection.

[0081] The called Manager class will call the basic functions provided by the external interface layer according to its own encapsulated logic to complete specific operations. For example, the screen sharing Manager class will call the interfaces related to screen capture and data transmission in the external interface layer to capture and share the screen content. In the process of executing the target call function, the Manager layer will feedback the execution results to the UseCase layer. If a function is executed successfully, a success message will be returned; if an error occurs, the corresponding error code and error description will be returned for subsequent processing by the UseCase layer.

[0082] S203, in the process of executing the target call function, communicating with the outside through the external interface layer corresponding to the call service request in the internal processing layer to obtain a response result of the call service request.

[0083] It can be understood that the main responsibility of the external interface layer is to encapsulate the external interface layers that the project depends on. These external interface layers cover multiple aspects.

[0084] For example, the screen sharing related interface is responsible for handling the interaction between the screen sharing function and external devices in the 5G new call;

[0085] IMS related interfaces are used to implement communication functions based on the operator's IMS network;

[0086] AIDL interface related to the extended interface. AIDL (AndroidInterfaceDefinitionLanguage) is an inter-process communication (IPC) mechanism in Android. This interface enables interaction between different application components.

[0087] As well as the JSAPI interface related to mini-programs, it is convenient to integrate mini-program related functions into 5G new calls.

[0088] By encapsulating these external interface layers, a unified entry point for interacting with the external environment is provided, allowing the inner code to call external functions in a standardized way, while also reducing the impact of changes in the external interface layer on the internal core code.

[0089] Optionally, when executing the target call function, the external interface to be used must first be determined based on the specific content of the call service request. For example, if the target call function is screen sharing, then the screen sharing related interface will be determined; if it is to establish an IMS call connection, then the IMS related interface will be selected.

[0090] After determining the external interface, the internal processing layer will initiate a communication request to the outside through the interface. Taking IMS calls as an example, a call request will be sent to the operator's IMS network through the IMS-related interface, including necessary information such as the calling number and the called number. For the screen sharing function, a sharing request will be sent to the external device through the screen sharing-related interface, and the shared screen data will be provided.

[0091] After initiating a communication request, the external interface layer will interact with the outside world according to established protocols and rules. In this process, multiple data transmissions and exchanges may be required. For example, when establishing an IMS call connection, signaling interaction is required to negotiate call parameters (such as voice coding format, video resolution, etc.); when sharing the screen, it is necessary to continuously transmit screen data to the external device and receive feedback information from the external device.

[0092] After interacting with the outside, the response result of the call service request will be obtained. This result may be a successful feedback, such as the call has been successfully established, screen sharing has been enabled; or it may be a failure prompt, such as the called number does not exist, the network connection fails, etc. The external interface layer will pass these response results to the internal processing layer for subsequent processing and feedback to the user.

[0093] In an exemplary embodiment, Figure 3 As shown, the target call function and the calling logic of the target call function required for the call service request are determined through the use case layer in the internal processing layer, including:

[0094] S301, parsing the call service request to obtain the service scenario and call requirements.

[0095] Among them, service type refers to the category to which the call service belongs, such as ordinary voice call, HD video call, video conference call with screen sharing function, emergency call, etc. Different service types correspond to different service processes and function combinations.

[0096] Call requirements: In addition to the business type, users may have other specific requirements, such as whether to open the markup board for annotation, whether to record the call, whether to set specific permissions, etc. These requirements further refine the specific requirements of the business.

[0097] Optionally, the parsing process can use different methods according to the specific format of the request. If the request is a JSON format data, the use case layer can extract the relevant fields through the JSON parsing library; if it is a custom message format, it needs to be parsed according to the pre-defined protocol.

[0098] S302, determining the target call function and the calling logic of the target call function corresponding to the business scenario and the call demand from the candidate call functions in the function mapping table through the use case layer in the internal processing layer.

[0099] Among them, the function mapping table is a pre-set data structure that records the correspondence between different business scenarios and call requirements and candidate call functions. This table is like a dictionary. The use case layer can find the required target call functions from it according to the parsed business scenarios and call requirements. Candidate call functions are a series of pre-defined basic call functions, such as voice call function, video call function, screen sharing function, markup drawing board function, permission management function, etc. These functions are the basic modules that constitute various complex call services.

[0100] Optionally, the use case layer performs a match search in the function mapping table based on the business scenario and call requirements. For example, if the business type is "video conference call with screen sharing function" and the call requirement includes "open the markup drawing board", the use case layer will find the corresponding target call function from the function mapping table, such as the video call function, screen sharing function and markup drawing board function.

[0101] In addition to determining the target call functions, the use case layer also needs to clarify the order and method of calling these functions, that is, the calling logic. Different business scenarios and call requirements may require different calling logic. For example, in a video conference call with screen sharing function, it is usually necessary to establish a video call connection first, then turn on the screen sharing function, and finally turn on the markup drawing board function according to user needs. The determination of the calling logic can be based on factors such as the dependency between functions, the rationality of business processes, and user experience.

[0102] In this embodiment, the use case layer can accurately understand the user's call service request, filter out suitable target call functions from the candidate call functions, and determine the calling logic of these functions.

[0103] In an exemplary embodiment, the external layer includes a view layer and a view model layer.

[0104] The View layer is the part that users come into direct contact with and is the entire "facade". It is like a display window that presents internal data to users in an intuitive and easy-to-understand interface. For example, in the 5G new call scenario, the call interface and shared screen images that users see are all displayed by the View layer.

[0105] On the one hand, it receives data from the ViewModel layer and converts it into visual interface elements. On the other hand, it collects user operations on the interface, such as clicking buttons, sliding the screen, etc., and feeds these operation information back to the ViewModel layer, thus realizing two-way communication between users and the application.

[0106] For terminal manufacturers, the View layer provides a lot of customization space. They can personalize the layout, color, and interaction methods of the interface according to the preferences and needs of different user groups. For example, they can design a simple and elegant interface for business users, and a colorful and interactive interface for young users.

[0107] Among them, the ViewModel layer is mainly responsible for interacting with the business logic. It directly calls the business logic interface provided by the UseCase layer to trigger the execution of corresponding business functions. For example, when a new 5G call needs to be initiated, the ViewModel layer will call the relevant business logic interface to complete the call establishment process.

[0108] After calling the business logic interface, the ViewModel layer will obtain the processing result data. Then, it processes and converts this data and updates it to the View layer so that the View layer can display the latest information. For example, during a call, the caller's information, screen sharing content and other data are passed to the View layer for display.

[0109] When the user operates in the View layer, the View layer will pass the operation information to the ViewModel layer. After receiving the information, the ViewModel layer will call the business logic interface of the UseCase layer again according to the user's intention and perform the corresponding operation, thus forming a complete interactive closed loop between the user and the business logic. This design pattern separates the business logic from the interface display, reduces the coupling of the code, and facilitates developers to develop, modify and maintain the interface and business logic separately.

[0110] Furthermore, the UI is generated by the view layer according to the interaction configuration information provided by the developer.

[0111] The interaction configuration information includes two parts:

[0112] (1) Interface configuration parameters: These parameters are used to define the specific layout and element style of the interface. For example, the size, color, and position of a button, the font and size of a text box, etc. By adjusting these parameters, different styles of interface design can be achieved.

[0113] (2) Device display parameters: Considering the different display characteristics of different devices, such as screen size and resolution, device display parameters are used to ensure that the UI can be displayed and adapted normally on various devices. For example, a looser layout may be used on large-screen devices, while appropriate compression and adjustment will be performed on small-screen devices.

[0114] Further, such as Figure 4 As shown, the call service request initiated by the user on the user interface UI is obtained from the external layer, including:

[0115] S401, obtaining a call service request initiated by a user on a user interface UI through a view layer.

[0116] For example, when a user initiates a call service request on the user interface UI, the View layer will directly perceive these operations. For example, when a user clicks the "Initiate Call" button, the View layer will capture this operation information and collect it as a call service request.

[0117] S402, calling the business logic interface through the view model layer to transmit the call service request to the use case layer in the internal processing layer.

[0118] Optionally, the business logic interface is obtained by the use case layer based on the target call function and the logic encapsulation of the target call function. This interface will be used as a whole for other layers (such as the external layer) to call directly.

[0119] For example, the packaging process is as follows:

[0120] 1. Define interface parameters: Interface parameters are the carrier of information when calling the business logic interface. They specify the necessary information to be provided when calling the interface to ensure that the interface can accurately process the request. The use case layer will determine the input parameters required by the interface based on the target call function and call logic.

[0121] Optionally, the interface parameters include: (1) Identification of the two parties of the call: used to uniquely identify the caller and the called party, such as mobile phone number, user ID, etc. The call connection is established based on these identifiers to ensure that the call can be accurately conducted between the two parties.

[0122] (2) Function enable flag: used to indicate whether a specific target call function is enabled. For example, for the screen sharing function, a Boolean flag can be set. When the flag is "true", it means that screen sharing is enabled, and when it is "false", it means that it is not enabled.

[0123] (3) Other related parameters: Depending on specific business needs, other parameters may be required. For example, in a video call, you may need to specify parameters such as video resolution and frame rate; in the permission management function, you may need to pass the user's permission level information.

[0124] 2. Encapsulate function calls: The use case layer integrates the call and call logic of the target call function into the implementation of the interface, so that the caller only needs to call the interface to execute the corresponding function according to the predetermined logic. The specific implementation method is as follows:

[0125] (1) Function call code embedding: The code for implementing the target call function is embedded into the implementation method of the interface. For example, for the video call function, the initialization method and connection establishment method of the relevant video call module may be called; for the screen sharing function, the screen capture, data transmission and other related methods may be called.

[0126] (2) Call logic control: In the interface implementation, according to the determined call logic, control statements such as conditional judgment and loop are used to control the execution order of each target call function.

[0127] Furthermore, after the View layer obtains the call service request, it will pass it to the ViewModel layer. After receiving the request, the ViewModel layer will call the business logic interface to pass the request to the use case layer of the internal processing layer. After receiving the request, the use case layer analyzes and determines the target call function and call logic, and then encapsulates these contents into a business scenario logic interface to facilitate calls by other layers, thereby realizing modularization and reuse of functions.

[0128] Furthermore, returning the response result to the UI through the external layer includes: converting the format of the response result through the view model layer, and returning the format-converted response result to the UI.

[0129] It is understandable that the UI layer has its own data display rules and format requirements. The response results returned by the internal processing layer are usually organized and stored from the perspective of business logic, and their data format may not match the format required for direct UI display. For example, the internal processing layer may return a complex data structure containing detailed technical information, while the UI may only need to display some key information, or need to display the data in a specific text format, image format, etc.

[0130] For example, the ViewModel layer will first extract the data required by the UI from the response results returned by the internal processing layer. For example, in a call service request, the response results returned by the internal processing layer may contain multiple information such as call establishment time, call duration, call quality indicators, etc., but the UI may only need to display the call duration and call status (success or failure). At this time, the ViewModel layer will extract these two key information from the response results.

[0131] After extracting the required data, the ViewModel layer will convert the data according to the requirements of the UI. This may include the following common conversion methods: 1) Data type conversion: Convert the data type returned by the internal processing layer to a type that the UI can handle. For example, convert the integer type call duration to a string type and add a time unit (such as "minutes") to facilitate display on the UI. 2) Text formatting: Format the text data to make it conform to the display specifications of the UI. For example, convert the error code in the response result to the corresponding error description information, or truncate and omit long text. 3) Data mapping: Map some internal identifiers or codes to user-visible labels or icons. For example, map the internal call status code (such as 0 for success and 1 for failure) to a text label of "Call success" or "Call failure", or a corresponding icon. 4) Data integration: After completing the data conversion, the ViewModel layer will integrate the converted data into a format suitable for UI display. This may be a simple data object or a complex data structure with multiple fields. For example, the converted call duration and call status information are integrated into a new data object, which is convenient for the UI layer to obtain and display at one time.

[0132] After the ViewModel layer completes the format conversion, it will pass the converted response result to the UI layer. In actual implementation, this process is usually implemented through data binding or event notification. For example, the data binding framework is used to bind the data properties in the ViewModel layer to the view elements in the UI layer. When the data in the ViewModel layer changes, the view elements in the UI layer will automatically update and display.

[0133] After receiving the response result after format conversion, the UI layer will update the interface display according to this data. For example, if the response result shows that the call is successful, the UI layer will display the prompt message "Call connected" on the interface and update related interface elements (such as a timer showing the call duration); if the response result shows that the call failed, the UI layer will display the corresponding failure reason and provide possible operation options (such as retry, return, etc.).

[0134] In this embodiment, the process of converting the format of the response result by the view model layer and returning it to the UI is to ensure that the response result of the internal processing layer can be displayed to the user in a suitable format and manner, thereby improving the user experience and achieving effective interaction with the user.

[0135] In an exemplary embodiment, Figure 5 As shown, a 5G new call UI open source framework based on the clean framework based on the above call service processing method is provided, and the framework includes:

[0136] External interface layer: This layer is mainly responsible for encapsulating the external interfaces that the project relies on. These external interfaces are the bridges for the system to interact with the external environment, covering multiple functional interfaces.

[0137] Manager layer: responsible for encapsulating the single functions of 5G new calls. It organizes and encapsulates the complex single function logic so that each function has a unified calling method and management logic.

[0138] UseCase layer: responsible for integrating and encapsulating the business logic functions of 5G new calls. It combines multiple single functions into specific business scenarios to meet different call requirements.

[0139] ViewModel layer: mainly responsible for directly calling the business logic function of 5G new calls and updating the acquired data to the View layer. It is the bridge between business logic and interface display.

[0140] View layer: As the visual part of the user interface, it is directly facing the user. It is responsible for displaying data and interacting with users related to 5G new calls.

[0141] This layered architecture separates business logic from interface display, and the responsibilities of each layer are clear. As the visual part of the user interface, the View layer is only responsible for displaying data and interacting with users, and does not involve complex business logic. This allows terminal manufacturers to customize the View layer according to their own needs, change the layout, color, interaction method, etc. of the interface, without affecting the business logic implementation of other layers.

[0142] By using the ViewModel layer as the middle layer, the business logic and the View layer are isolated, reducing the coupling of the code. When customizing the View layer, only the data transmission and interaction between the View layer and the ViewModel layer need to be adjusted, without modifying the UseCase layer, the Manager layer, and the external interface layer, thus facilitating the customized development of the interface and the modification of the business logic, solving the problem that the UI design of 5G new calls cannot be customized in terminal integration under the existing technology.

[0143] It should be understood that, although the steps in the flowcharts involved in the above embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0144] Based on the same inventive concept, the embodiment of the present application also provides a call service processing device for implementing the call service processing method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more call service processing device embodiments provided below can refer to the limitations of the call service processing method above, and will not be repeated here.

[0145] In an exemplary embodiment, Figure 6 As shown, a call service processing device is provided, including: a UI interaction module 11, a call processing module 12 and a feedback module 13, wherein:

[0146] The UI interaction module 11 is used to obtain the call service request initiated by the user on the user interface UI through the external layer; wherein the UI is generated by the external layer according to the interaction configuration information provided by the developer;

[0147] The call processing module 12 is used to process the call service request through the target call function integrated in the internal processing layer to obtain a response result of the call service;

[0148] The feedback module 13 is used to return the response result to the UI through the external layer, so that the user can perform corresponding call operations according to the response result.

[0149] In one embodiment, the call processing module 12 is further used to: determine the target call function and the calling logic of the target call function required by the call service request through the use case layer in the internal processing layer;

[0150] Through the management layer in the internal processing layer, the target call function is executed according to the calling logic of the target call function;

[0151] In the process of executing the target call function, the external interface layer corresponding to the call service request in the internal processing layer communicates with the outside to obtain a response result of the call service request.

[0152] In one embodiment, the call processing module 12 is further used to: parse the call service request to obtain the service scenario and call requirements;

[0153] Through the use case layer in the internal processing layer, the target call function and the calling logic of the target call function corresponding to the business scenario and call requirements are determined from the candidate call functions in the function mapping table.

[0154] In one embodiment, the external layer includes a view layer and a view model layer; the UI is generated by the view layer according to the interaction configuration information provided by the developer; the interaction configuration information includes interface configuration parameters and device display parameters;

[0155] The UI interaction module 11 is further used to: obtain a call service request initiated by a user on the user interface UI through the view layer;

[0156] The view model layer calls the business logic interface and transmits the call business request to the use case layer in the internal processing layer.

[0157] In one of the embodiments, the business logic interface is obtained by the use case layer according to the target call function and the logical encapsulation of the target call function.

[0158] In one embodiment, the feedback module 13 is further used to: convert the format of the response result through the view model layer, and return the format-converted response result to the UI.

[0159] Each module in the above-mentioned call service processing device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the operations corresponding to each module above.

[0160] In an exemplary embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as shown in FIG. Figure 7As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected via a bus, and the communication interface, the display unit and the input device are connected to the bus via the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores operations and computer programs. The internal memory provides an environment for the operation of the operations and computer programs in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a mobile cellular network, near field communication (NFC) or other technologies. When the computer program is executed by the processor, a method for processing call services is implemented. The display unit of the computer device is used to form a visually visible picture, which can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device shell, or an external keyboard, touchpad or mouse.

[0161] Those skilled in the art will understand that Figure 7 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0162] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0163] Obtaining the call service request initiated by the user on the user interface UI through the external layer; wherein the UI is generated by the external layer according to the interactive configuration information provided by the developer;

[0164] The call service request is processed through the target call function integrated in the internal processing layer to obtain the response result of the call service;

[0165] By returning the response result to the UI, the user can perform corresponding call operations based on the response result.

[0166] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0167] Obtaining the call service request initiated by the user on the user interface UI through the external layer; wherein the UI is generated by the external layer according to the interactive configuration information provided by the developer;

[0168] The call service request is processed through the target call function integrated in the internal processing layer to obtain the response result of the call service;

[0169] By returning the response result to the UI, the user can perform corresponding call operations based on the response result.

[0170] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:

[0171] Obtaining the call service request initiated by the user on the user interface UI through the external layer; wherein the UI is generated by the external layer according to the interactive configuration information provided by the developer;

[0172] The call service request is processed through the target call function integrated in the internal processing layer to obtain the response result of the call service;

[0173] By returning the response result to the UI, the user can perform corresponding call operations based on the response result.

[0174] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0175] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0176] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0177] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A method for processing call services, characterized in that: Applied to a terminal device, the method comprises: Obtaining a call service request initiated by a user on a user interface UI through the external layer; wherein the UI is generated by the external layer according to the interaction configuration information provided by the developer; Processing the call service request through the target call function integrated in the internal processing layer to obtain a response result of the call service; The response result is returned to the UI through the external layer, so that the user can perform corresponding call operations according to the response result.

2. The method according to claim 1, characterized in that The process of processing the call service request by the target call function integrated in the internal processing layer to obtain a response result of the call service includes: Determining the target call function required by the call service request and the calling logic of the target call function through the use case layer in the internal processing layer; Executing the target call function according to the calling logic of the target call function through the management layer in the internal processing layer; In the process of executing the target call function, the external interface layer corresponding to the call service request in the internal processing layer communicates with the outside to obtain a response result of the call service request.

3. The method according to claim 2, characterized in that The determining, through the use case layer in the internal processing layer, the target call function required by the call service request and the calling logic of the target call function includes: Parsing the call service request to obtain the service scenario and call requirements; Through the use case layer in the internal processing layer, the target call function corresponding to the business scenario and the call requirement and the calling logic of the target call function are determined from the candidate call functions in the function mapping table.

4. The method according to claim 2, characterized in that: The external layer includes a view layer and a view model layer; the UI is generated by the view layer according to the interactive configuration information provided by the developer; the interactive configuration information includes interface configuration parameters and device display parameters; The step of obtaining the call service request initiated by the user on the user interface UI through the external layer includes: Acquire a call service request initiated by the user on the user interface UI through the view layer; The view model layer calls the business logic interface to transmit the call service request to the use case layer in the internal processing layer.

5. The method according to claim 4, characterized in that The business logic interface is obtained by the use case layer according to the target call function and the logical encapsulation of the target call function.

6. The method according to claim 4, characterized in that The returning the response result to the UI through the external layer includes: The response result is format-converted through the view model layer, and the response result after format conversion is returned to the UI.

7. A call service processing device, characterized in that: The device comprises: A UI interaction module is used to obtain a call service request initiated by a user on a user interface UI through an external layer; wherein the UI is generated by the external layer according to the interaction configuration information provided by the developer; A call processing module, used to process the call service request through the target call function integrated in the internal processing layer to obtain a response result of the call service; A feedback module is used to return the response result to the UI through the external layer, so that the user can perform corresponding call operations according to the response result.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images