CN117914674A - Service scheduling method, device, vehicle and computer storage medium - Google Patents
Service scheduling method, device, vehicle and computer storage medium Download PDFInfo
- Publication number
- CN117914674A CN117914674A CN202311681364.6A CN202311681364A CN117914674A CN 117914674 A CN117914674 A CN 117914674A CN 202311681364 A CN202311681364 A CN 202311681364A CN 117914674 A CN117914674 A CN 117914674A
- Authority
- CN
- China
- Prior art keywords
- service
- target service
- information
- target
- identification database
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 55
- 238000004590 computer program Methods 0.000 claims description 13
- 238000010586 diagram Methods 0.000 description 12
- 238000012545 processing Methods 0.000 description 8
- 238000004891 communication Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 7
- 230000008569 process Effects 0.000 description 5
- 230000005540 biological transmission Effects 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- 238000006243 chemical reaction Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
Abstract
The application discloses a service scheduling method, a device, a vehicle and a computer storage medium, wherein the method is characterized in that a service calling request of a user for target service is obtained; the service calling request comprises a target service identifier corresponding to the service to be called; determining whether an available target service exists in the identification database according to the target service identifier; and calling the service content of the target service from the service providing end under the condition that the target service available in the identification database. Thus, whether the target service corresponding to the available target service identifier exists in the identification database is determined according to the target service identifier. When the available target service exists in the identification database, the service content of the target service is directly called, and the flexibility of calling the service between the vehicle end and the service providing end in different local area networks is improved. In addition, the calling efficiency of calling the target service between the service providing end and the vehicle end is improved.
Description
Technical Field
The application relates to the technical field of the internet of things, in particular to a service scheduling method, a service scheduling device, a vehicle and a computer storage medium.
Background
Along with the intelligent development of vehicles, the combination of vehicles and the Internet of things becomes a hot trend of future vehicle development. The vehicle based on the internet of things can combine with the service providing end to provide a plurality of different services for the vehicle end, so that a service-oriented architecture (service-Oriented Architecture, SOA) is generated, and the SOA can meet various different business requirements of the vehicle end by calling the service contents provided by different service providing ends in different virtual local area networks.
In the related art, when a service provider provides service contents for a vehicle or the vehicle invokes the service contents provided by the service provider, service invocation is often implemented based on identification information statically configured between the vehicle and the service provider. However, since the identification information between the vehicle side and the service providing side is registered in the virtual local area network (Virtual Local Area Network, VLAN), service calls between the vehicle side and the service providing side in different virtual local area networks are ignored. Therefore, the vehicle end and the service providing end contained in different local area networks in the service-oriented architecture are difficult to call in a cross-domain manner, and the flexibility of service scheduling is poor.
Disclosure of Invention
The embodiment of the application provides a service scheduling method, a service scheduling device, a vehicle and a computer storage medium, which can improve the flexibility of service scheduling.
In a first aspect, an embodiment of the present application discloses a service scheduling method, where the method is applied to a vehicle end, and the method includes:
Acquiring a service call request of a user for a target service; the service calling request comprises a target service identifier corresponding to the service to be called;
Determining whether available target services exist in an identification database according to the target service identifier;
And calling the service content of the target service from a service providing end under the condition that the target service available in the identification database.
In a second aspect, an embodiment of the present application discloses a service scheduling apparatus, where the apparatus is applied to a vehicle end, and the service scheduling apparatus includes:
The acquisition unit is used for acquiring a service call request of a user to a target service; the service calling request comprises a target service identifier corresponding to the service to be called;
A determining unit, configured to determine whether there is an available target service in the identification database according to the target service identifier;
And the calling unit is used for calling the service content of the target service from the service providing end under the condition that the available target service exists in the identification database.
In a third aspect, an embodiment of the present application discloses a vehicle, where the vehicle includes a processor and a memory, the memory stores a computer program, and the processor invokes the computer program to implement the service scheduling method described above.
In a fourth aspect, an embodiment of the present application discloses a computer readable storage medium storing program code that is invoked by a processor to implement the service scheduling method described above.
In a fifth aspect, the application discloses a computer program product comprising computer program code which, when run by a processor, causes the above-mentioned service scheduling method to be performed.
In the embodiment of the application, the service call request of the user to the target service is obtained; the service calling request comprises a target service identifier corresponding to the service to be called; determining whether an available target service exists in the identification database according to the target service identifier; in the case where there is a target service available in the identification database, the service content of the target service is called from the service provider. Thus, whether the target service corresponding to the available target service identifier exists in the identification database is determined according to the target service identifier. When the available target service exists in the identification database, the service content of the target service is directly called, and the flexibility of calling the service between the vehicle end and the service providing end in different local area networks is improved. In addition, the calling efficiency of calling the target service between the service providing end and the vehicle end is improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of a system architecture of a scheduling system of a service scheduling method according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a system architecture of another scheduling system of a service scheduling method according to an embodiment of the present application;
FIG. 3 is a schematic flow chart of a service scheduling method according to an embodiment of the present application;
FIG. 4 is a schematic flow chart of a service scheduling method according to an embodiment of the present application;
FIG. 5 is a schematic flow chart of another method for scheduling services according to an embodiment of the present application;
FIG. 6 is a schematic diagram of another specific flow of a service scheduling method disclosed in an embodiment of the present application;
FIG. 7 is a schematic diagram of a specific scenario of a service scheduling method disclosed in an embodiment of the present application;
FIG. 8 is a schematic diagram of another specific scenario of a service scheduling method disclosed in an embodiment of the present application;
FIG. 9 is a schematic diagram of another specific flow of a service scheduling method disclosed in an embodiment of the present application;
fig. 10 is a schematic structural diagram of a service scheduling apparatus according to an embodiment of the present application;
Fig. 11 is a schematic view of a vehicle according to an embodiment of the present application.
Detailed Description
Embodiments of the present application are described in detail below, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to like or similar elements or elements having like or similar functions throughout. The embodiments described below by referring to the drawings are exemplary only for explaining the present application and are not to be construed as limiting the present application.
In order to enable those skilled in the art to better understand the solution of the present application, the following description will make clear and complete descriptions of the technical solution of the present application in the embodiments of the present application with reference to the accompanying drawings. It will be apparent that the described embodiments are only some, but not all, embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
For a better understanding of the embodiments of the present application, a system architecture diagram is described below.
Referring to fig. 1, fig. 1 is a schematic diagram illustrating a scheduling system 100 according to an embodiment of the application. As shown in fig. 1, the dispatch system 100 may include a dispatch gateway 110, a vehicle side 120, and a service provider 130.
Wherein the dispatch gateway 110 may be a service dynamic dispatch gateway. The dispatch gateway 110 may be installed in the vehicle end 120 or may be independent of the vehicle end 120. For a better understanding of the present application, the dispatch gateway 110 is mounted to the vehicle side 120 as an example.
The dispatch system 100 may include a plurality of vehicle ends 120. Wherein each vehicle end 120 of the plurality of vehicle ends 120 is in communication with the dispatch gateway 110.
The dispatch system 100 may include a plurality of service providers 130. Wherein each service provider 130 of the plurality of service providers 130 is in communication with the dispatch gateway 110 in the vehicle side 120.
Specifically, referring to fig. 2, fig. 2 is a schematic diagram illustrating a refinement of another scheduling system 200 according to an embodiment of the present application. As shown in fig. 2, the dispatch system 200 may include an SOA-based dispatch gateway 210, a demand side 220, and a service side 230.
The dispatch gateway 210 may include a service dynamic dispatch gateway, a vehicle cloud protocol conversion module, a protocol data transmission module, and an ethernet switch. The service dynamic dispatching gateway can comprise a service dynamic discovery management module, a service dynamic discovery module, a service authority management module and a whole vehicle service registration center. The vehicle cloud protocol conversion module and the protocol data transmission module can realize data transmission between the dispatching gateway and the Ethernet switch.
The demand side 220 may include a plurality of demand sides 220 of a vehicle wireless terminal of an ethernet switch with the SOA dispatch gateway 210 or a cloud consumer side connected with the vehicle wireless terminal within the virtual local area network VLAN 1. Wherein, each of the plurality of demand terminals 220 may include an interaction device that interacts with the user, based on which the demand terminal 220 may respond to a service invocation request of the target service by the user.
The server 230 may include a plurality of service providers connected to the ethernet switch of the SOA dispatch gateway 210 within the virtual local area network VLAN 2.
It should be noted that the system architecture shown in fig. 1 and fig. 2 is only an example, and the technical solution disclosed in the embodiments of the present application is not limited. With the evolution of the interactive system architecture and the appearance of new application scenes, the technical scheme disclosed by the embodiment of the application is applicable to similar technical problems.
Referring to fig. 3, fig. 3 is a flowchart of a service scheduling method according to an embodiment of the application. The service scheduling method can be applied to a vehicle end. The service scheduling method may include the following steps.
301. And acquiring a service call request of the user for the target service.
Wherein the service call request includes a target service identifier corresponding to the service to be called.
The vehicle side may include a dispatch gateway through which the vehicle side may communicate with the service provider side. The dispatch system may include at least one vehicle side, each of which may obtain a user's service invocation request for a target service. Specifically, the user may determine the corresponding service invocation request in response to an invocation operation of the target service by the user through an interaction device (e.g., an in-vehicle control panel, a vehicle center control panel, etc.) installed on the vehicle side. The user can also respond to the call operation of the user to the target service by the call operation of the terminal equipment (such as mobile phone equipment, computer equipment and the like) which is in communication with the vehicle end to determine the corresponding service call request.
The service call request may be a request of a service consumer at the vehicle end for a target service meeting the user application requirement, and the service call request may include a target service identifier corresponding to the target service meeting the user application requirement.
It should be noted that the service invocation request may be request information existing in a service discovery (ServiceDiscovery, SD) message of a standard IP-based extensible service-oriented middleware (Oriented MiddlewarE over IP, SOM/IP) protocol. Illustratively, flag may be used to identify the service. For example, whether to restart Flag, whether to support unicast Flag, etc.; the Offer ENTRY ARRAY may be used to represent the name of the service. For example, an instance of a service, a version of a service, a lifecycle of a service; the Option Array may be used to represent deployment information of a service, such as a transport protocol, a service providing port number, and the like.
302. A determination is made as to whether there is a target service available in the identification database based on the target service identifier.
After the vehicle receives the service call request of the user for the target service, whether the target service required to be called by the user exists in the identification database or not can be determined according to the target service identifier of the target service. That is, whether or not a target service corresponding to the target service identifier exists in the identification database is queried based on the target service identifier of the target service.
After determining that the target service needed by the user exists in the identification database, service information of the target service can be queried in the identification database. The service information of the target service may include source information of a service source providing the target service, range information of a right range of the target service, deployment information of the target service, state information of the target service, version information of the target service, interface information of the target service, and the like.
In another embodiment, the service provider that can query the target service in the identification database according to the target service identifier of the target service to determine the target service can query whether the target service is an unknown service to the vehicle side according to the information of the target service. And under the condition that the target service is not an unknown service, inquiring service information corresponding to the target service in the identification database. And detecting whether the current vehicle end has the authority to use the target service according to the service information of the target service. In the case that the vehicle side has the authority to use the target service, whether the target service is available or not is detected according to the service information. In the event that a target service is available, it is determined that there is a target service available in the identification database.
In another embodiment, after querying the target service in the identification database according to the target service identifier of the target service, the target service may also be determined to be an unknown service. In the event that the target service is an unknown service, it may be determined that the target service is not present in the identification database. And under the condition that the target service does not exist in the identification database, the service information of the target service of each network segment node where the service providing end corresponding to the target service is located can be inquired. That is, the service information of the target service may be queried by querying each node in a different domain connected to the dispatch gateway of the vehicle side. Under the condition that the service information of the target service is queried, the service information of the target service is stored in an identification database, and the target service corresponding to the service calling request is registered in the identification database.
Referring to fig. 4, fig. 4 is a schematic flow chart of a specific scenario of another embodiment. Specifically, after the vehicle side obtains the service call request of the user for the target service through the dispatching gateway, whether the target service corresponding to the target service identifier in the service call request is registered in the identification database can be determined. And detecting whether the vehicle end has the use authority for the target service or not under the condition that the target service is registered. And judging whether the current state of the target service is an available state or not under the condition that the vehicle side has authority to the target service. And storing the information of the target service into an identification database of the vehicle end under the condition that the current state of the target service is an available state, and dispatching the target service from the service providing end to the vehicle end.
303. In the case where there is a target service available in the identification database, the service content of the target service is called from the service provider.
And under the condition that the vehicle end determines that the available target service exists in the identification database, the current vehicle end and the service providing end corresponding to the target service can be bound through a dispatching gateway in the vehicle end. After determining the binding relation between the vehicle end and the service providing end of the target service, the service content of the target service provided by the service providing end can be called to the vehicle end for use based on the binding relation.
It should be noted that, the binding relationship between the service providing end and the vehicle end may be a binding relationship between the vehicle end and the service providing end determined by the corresponding relationship between the vehicle end and the target service subscribed by the vehicle end. That is, in the case that the vehicle side needs to subscribe to the target service, if a service providing side capable of providing the target service is queried through a dispatch gateway of the vehicle, a binding relationship between the vehicle side and the service providing side is determined.
Specifically, the vehicle side can acquire the target service scheduled from the service providing side based on the binding relationship between the service providing side and the vehicle side. After determining the binding relationship between the service providing end and the vehicle end, the vehicle end and the service providing end can be connected according to the binding relationship, so that the vehicle end can register for the target service at the service providing end based on the dispatching gateway. The registered vehicle end can be used for the target service at any time. Therefore, the calling gateway can dynamically update the information of the target service from the service providing end to the vehicle end according to the service calling request sent by the vehicle end in the identification database, so that the service providing end can dynamically provide the target service for the vehicle end, plug and play of the new target service on the service gateway is realized, and the efficiency of calling the target service is improved.
In another embodiment, when the dispatch gateway at the vehicle side dispatches the target service from the service providing side to the vehicle side, and after the dispatch gateway at the vehicle side dispatches the target service to the vehicle side for use, call information of the target service and use information of service content of the target service may be recorded. Further, the scheduling gateway at the vehicle end can store the calling information and the using information into the identification database to record the calling information and the using information of the target service, so that the information in the identification database is continuously updated in the calling and updating processes of the target service. Further, the dispatching gateway at the vehicle end can also track the service of the target service according to the calling information and the using information of the target service stored in the identification database. The tracking information is used for evaluating the quality of the target service. Illustratively, the vehicle side may evaluate the timeliness of the invocation of the vehicle side by the target service based on the response time of the target service in the identification database. The vehicle end can evaluate the use frequency of the vehicle end for using the target service according to the last call information of the target service.
In the method embodiment depicted in FIG. 2, a service invocation request for a target service by a user is obtained; the service calling request comprises a target service identifier corresponding to the service to be called; determining whether an available target service exists in the identification database according to the target service identifier; in the case where there is a target service available in the identification database, the service content of the target service is called from the service provider. Thus, whether the target service corresponding to the available target service identifier exists in the identification database is determined according to the target service identifier. When the available target service exists in the identification database, the service content of the target service is directly called, and the flexibility of calling the service between the vehicle end and the service providing end in different local area networks is improved. In addition, the calling efficiency of calling the target service between the service providing end and the vehicle end is improved.
Referring to fig. 5, fig. 5 is a flowchart illustrating another service scheduling method according to an embodiment of the present application. The service scheduling method can be applied to the service dynamic vehicle end, and the service scheduling method can comprise the following steps.
501. And receiving the release content from the service provider.
Wherein the distribution content includes a plurality of services and a plurality of identifiers, the plurality of services being in one-to-one correspondence with the plurality of identifiers.
The vehicle side can acquire service information from the service provider side through the dispatch gateway. Accordingly, the service providing terminal can issue a plurality of services to the vehicle terminal. The service information received from the service providing end may be first service information of the service already stored in the identification database; the service information received from the service providing terminal may also be second service information of a service not stored in the identification database. In the case that the vehicle side receives the first service information from the service providing side through the scheduling gateway, the update may be performed on the identification database stored in accordance with the received first service information. When the vehicle side receives the second service information from the service providing side through the dispatching gateway, the second service information can be loaded into the identification database, and the service corresponding to the second service information is registered.
Referring to fig. 6, fig. 6 is a schematic flow chart of acquiring service information from a service provider. Specifically, after creating an identification database for storing description identifiers of service information, service information from a service provider may be dynamically collected, and service information of a service may be registered or updated according to the acquired service information.
It should be noted that, acquiring the service information from the service providing end may be actively acquiring, according to the service call request, the service information of the target service corresponding to the service call request from the service providing end; or the service information from the service provider may be obtained by passively receiving the service information from the service provider. The vehicle end can collect the service issued by the service providing end which is in data connection with the dispatching gateway of the vehicle through the whole vehicle service data registration center in the dispatching gateway. The service providing end can send the service information of the service to be issued or the service information of the service to be updated to the dispatching gateway of the vehicle end under the condition that the service providing end needs to issue new service or update service information. Therefore, the vehicle side can passively receive the service information of the service to be issued or the service information of the service to be updated from the service providing side through the dispatching gateway. In addition, the vehicle side can actively inquire service information corresponding to the service call request to the service providing side through the dispatching gateway according to the service call request sent to the dispatching gateway by the vehicle side.
Referring to fig. 7, fig. 7 is a schematic flow chart of acquiring service information. Specifically, the dispatching gateway of the vehicle side can realize data connection with a plurality of service providing sides for providing services. For example, a service provider S1, a service provider S2, a service provider S3, and a service provider Sn. The service information can be sent to the vehicle end by the plurality of service providing ends which are in data connection with the dispatching gateway of the vehicle end. For example, service information s1.Info, service information s2.Info, service information s3.Info, and service information sn.
Referring to fig. 8, fig. 8 is another flow chart for acquiring service information. Specifically, the vehicle end can realize data connection with a plurality of service providing ends for providing services through the dispatching gateway; the system can also be connected with a plurality of vehicle ends needing service. The vehicle end can search corresponding service information in each service providing end in data communication with the vehicle end according to the service call request after receiving the service call request of any one of the vehicle ends, and return the searched service information S1.Info, S2.Info, S3.Info and Sn.info to the vehicle end.
502. A plurality of services are registered in the identification database, respectively, based on the plurality of identifiers, to update the identification database.
After the vehicle side obtains the service information from the service providing side through the dispatching gateway, the service information can be stored in the identification database. When a service corresponding to the service information is already present in the identification database, the service information of the service already present in the identification database is updated. And storing the service information of the service to the service corresponding to the service information registered in the identification database by the identification database under the condition that the service corresponding to the service information does not exist in the identification database.
Referring to fig. 9, fig. 9 is a specific flowchart of another embodiment of updating service information. Specifically, the service list existing at the current vehicle end can be loaded from the whole vehicle service registry. And detecting a service call request sent by the vehicle end and/or release information sent by the service providing end by monitoring each VLAN connected with the dispatching gateway of the vehicle end. It should be noted that, the service call request sent by the vehicle end may include a target service that needs to be queried by the vehicle end; the release information sent by the service providing end can include newly added or updated target services released by the service providing end. Therefore, the vehicle side can query the target service in the identification database according to the service call request or the release information through the dispatching gateway, and judge whether the target service in the service call request or the release information is the existing service. In the case that the target service in the service call request or the release information is not an existing service, that is, the target service is the target service existing in the identification database, the current deployment information, the current state information, the current authority information and the like of the target service can be recorded. And after the current service state of the target service is recorded, finishing information registration of the target service to be newly added to a whole vehicle service registration center of a dispatching gateway of the vehicle side. In addition, when the target service in the service call request or the release information is the existing service, after the current deployment information of the target service is recorded, whether the service state of the target service is changed or not can be judged, and if the service state is changed, the state information in the service call request or the release information is updated to the current state information; if the service state is unchanged, judging whether the authority information of the target service is changed or not. If the authority information of the target service changes, the authority information in the service calling request or the release information is updated to the current authority information. After the updating is completed, the information updating of the target service is completed through the whole vehicle service registration center.
In another embodiment, the inventive approach may also create an identification database before registering the plurality of services in the identification database. After the identification database is created, service information corresponding to a plurality of services from a plurality of service providers can also be acquired. The service information includes a plurality of identifiers corresponding to a plurality of services provided by the service provider. After obtaining service information corresponding to the plurality of service providers and a plurality of identifiers corresponding to the plurality of services, the plurality of services and the corresponding plurality of identifiers may be stored in the identification database.
The identification database may be used to store a plurality of service information corresponding to a plurality of services. The service information of each of the plurality of services may be description information describing each of the service information of the service. The service information may include usage information of the service used by the vehicle side and call information of the scheduling service of the vehicle side service provider. For example, the usage information of the service may include status information of the service, time information of a request response of the service, user information of a user to which the service corresponds, information of a last successful call of the service, and the like. The description information of each of the plurality of services may further include call information for scheduling the service from the service provider. Illustratively, the call information of the service may include source information of an electronic control unit (Electronic Control Unit, ECU) providing the service, scope information of the service usage right, deployment information of the service, status information of the service, version information of the service, interface information available to the service, and the like.
Illustratively, the identification database may store different types of information corresponding to a plurality of services and description information corresponding to each different type of information may be as shown in table 1:
Table 1, representation information of identification database
The service corresponding to the service information stored in the identification database may be a service for which registration is completed in the identification database. Under the condition that the vehicle end determines that the service call request is carried out on the service which has completed registration, the vehicle end can inquire the service in the identification database according to the service call request, and the corresponding target service is obtained.
503. And acquiring a service call request of the user for the target service.
Wherein the service call request includes a target service identifier corresponding to the service to be called.
Step 503 may refer to the specific description of step 301, and will not be described herein.
504. And under the condition that the target service corresponding to the target service identifier exists in the identification database, determining the description information corresponding to the target service according to the target service identifier.
After obtaining a service call request of a user for a target service, whether the target service exists in the identification database or not can be queried according to a target service identifier in the service call request. After determining that the target service exists, the description information corresponding to the target service can be queried according to the target service identifier of the target service. Wherein the description information may be used to represent information describing the target service.
505. And determining whether the target service available in the identification database exists according to the description information.
Wherein the description information may include availability information and authority information of the target service. After determining the description information of the target service, it may be determined whether there is a target service available in the identification database according to the description information of the target service. Specifically, after determining that the target service exists in the identification database and acquiring the description information corresponding to the target service, whether the target service is available or not may be determined according to the availability information of the target service. When the availability information corresponding to the target service determines that the target service is available, whether the vehicle side has the authority to use the service provider corresponding to the target service may be determined according to the authority information of the target service. In the case that the vehicle side has the authority to use the service provider corresponding to the target service, it is determined that the target service is available in the identification database.
After the target service is available in the identification database, the target service can be called to the vehicle end for use.
506. And under the condition that no available target service exists in the identification database, inquiring service information of the service providing end corresponding to the target service at each network segment node.
After determining the description information of the target service, it may be determined whether there is a target service available in the identification database according to the description information of the target service. Specifically, after determining that the description information corresponding to the target service exists in the identification database, if the availability information or the authority information of the target service indicates that the available target service does not exist in the identification database, the service information of the target service of each network segment node where the service providing end corresponding to the target service is located may be queried. That is, the service information of the target service may be queried by querying each node in a different domain where data communication is implemented with the vehicle side.
507. And storing the service information of the target service to an identification database under the condition that the service information of the target service is queried.
Under the condition that the service information of the target service is queried, the service information of the target service is stored in an identification database, and the target service corresponding to the service calling request is registered in the identification database.
In the method embodiment depicted in FIG. 5, a user's service invocation request for a target service is obtained; the service calling request comprises a target service identifier corresponding to the service to be called; determining whether an available target service exists in the identification database according to the target service identifier; in the case where there is a target service available in the identification database, the service content of the target service is called from the service provider. Thus, whether the target service corresponding to the available target service identifier exists in the identification database is determined according to the target service identifier. When the available target service exists in the identification database, the service content of the target service is directly called, and the flexibility of calling the service between the vehicle end and the service providing end in different local area networks is improved. In addition, the calling efficiency of calling the target service between the service providing end and the vehicle end is improved.
It is to be understood that the same or corresponding information as in the different embodiments described above may be referred to each other.
Referring to fig. 10, fig. 10 is a schematic diagram illustrating a service scheduling apparatus 1000 according to an embodiment of the application. As shown in fig. 10, the service scheduling apparatus 1000 may include:
an obtaining unit 1001, configured to obtain a service call request of a user to a target service; the service calling request comprises a target service identifier corresponding to the service to be called;
A determining unit 1002, configured to determine whether there is an available target service in the identification database according to the target service identifier;
and a calling unit 1003, configured to call, from a service provider, service content of the target service if the target service is available in the identification database.
In some embodiments, the service scheduling apparatus 1000 may further include:
A registration unit 1004, configured to receive release content from the service provider; the release content comprises a plurality of services and a plurality of identifiers, wherein the plurality of services are in one-to-one correspondence with the plurality of identifiers;
The registering unit 1004 is further configured to register the plurality of services in the identification database according to the plurality of identifiers, so as to update the identification database.
In some embodiments, the determining unit 1002 may be specifically configured to:
Under the condition that the target service corresponding to the target service identifier exists in the identification database, determining description information corresponding to the target service according to the target service identifier;
And determining whether available target services exist in the identification database according to the description information.
In some embodiments, the determining unit 1002 may be specifically configured to:
determining whether the target service is available according to the availability information;
Determining whether the vehicle end has the authority to use the service providing end corresponding to the target service according to the authority information under the condition that the target service is available;
And under the condition of having the authority of using the service provider corresponding to the target service, determining that the target service is available in the identification database.
In some embodiments, the service scheduling apparatus 1000 may further include:
a query unit 1005, configured to query service information of a service provider corresponding to the target service at each network segment node, where the target service is not available in the identification database;
The query unit 1005 is further configured to store, in case service information of the target service is queried, service information of the target service to the identification database.
In some embodiments, the service scheduling apparatus 1000 may further include:
A tracking unit 1006, configured to record call information of the target service and usage information of service content of the target service;
The tracking unit 1006 is further configured to track the target service according to the call information and the usage information, so as to obtain tracking information of the target service; the tracking information is used for evaluating the quality of the target service.
In some embodiments, the service scheduling apparatus 1000 may further include:
A creation unit 1007 for creating an identification database;
a creating unit 1007, configured to obtain service information corresponding to a plurality of services from the service providing end; wherein the service information comprises a plurality of identifiers corresponding to a plurality of services;
the creating unit 1007 is further configured to store service information corresponding to the plurality of services to the identification database.
In some embodiments, the determining unit 1002 may be specifically configured to:
and inquiring whether identifiers consistent with the target service identifier exist in a plurality of identifiers corresponding to a plurality of services in the identification database so as to determine the target service.
It will be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working process of the apparatus and modules described above may refer to the corresponding process in the foregoing method embodiment, which is not repeated herein.
In the several embodiments disclosed herein, the modules may be electrically, mechanically, or otherwise coupled to each other.
In addition, each functional module in each embodiment of the present application may be integrated into one processing module, or each module may exist alone physically, or two or more modules may be integrated into one module. The integrated modules may be implemented in hardware or in software functional modules.
As shown in fig. 11, the embodiment of the present application further discloses a schematic structural diagram of a vehicle 1100, where the vehicle 1100 includes a processor 1110 and a memory 1120, and the memory 1120 stores computer program instructions, and when the computer program instructions are called by the processor 1110, the various method steps disclosed in the foregoing embodiments can be executed. Those skilled in the art will appreciate that the configuration of the vehicle 1100 shown in the figures does not constitute a limitation of the vehicle, and may include more or fewer components than shown, or may combine certain components, or a different arrangement of components. Wherein:
Processor 1110 may include one or more processing cores. The processor 1110 utilizes various interfaces and lines to connect various portions of the overall battery management system, invoking data stored in the memory 1120 by executing or executing instructions, programs, code sets, or instruction sets stored in the memory 1120, performing various functions of the battery management system and processing data, and performing various functions of the vehicle and processing data, thereby providing overall control of the vehicle. Alternatively, the processor 1110 may be implemented in at least one hardware form of digital signal processing (DIGITAL SIGNAL processing, DSP), field-programmable gate array (field-programmable GATE ARRAY, FPGA), programmable logic array (Programmable Logic Array, PLA). The processor 1110 may integrate one or a combination of several of a central processor 1110 (Central Processing Unit, CPU), an image processor 1110 (Graphics Processing Unit, GPU), and a modem, etc. The CPU mainly processes an operating system, a user interface, an application program and the like; the GPU is used for being responsible for rendering and drawing of display content; the modem is used to handle wireless communications. It will be appreciated that the modem may not be integrated into the processor 1110 and may be implemented solely by a single communication chip.
The memory 1120 may include a random access memory 1120 (Random Access Memory, RAM) or a read-only memory 1120. Memory 1120 may be used to store instructions, programs, code, sets of codes, or sets of instructions. The memory 1120 may include a stored program area and a stored data area, wherein the stored program area may store instructions for implementing an operating system, instructions for implementing at least one function (e.g., a touch function, a sound playing function, an image playing function, etc.), instructions for implementing various method embodiments described below, and the like. The storage data area may also store data created by the vehicle in use (e.g., phonebook, audio-video data, chat-record data), etc. Accordingly, the memory 1120 may also include a memory controller to disclose access to the memory 1120 by the processor 1110.
Although not shown, the vehicle may further include a display unit or the like, which is not described herein. In particular, in this embodiment, the processor 1110 in the vehicle loads executable files corresponding to the processes of one or more application programs into the memory 1120 according to the following instructions, and the processor 1110 executes the application programs stored in the memory 1120, so as to implement the various method steps disclosed in the foregoing embodiments.
According to one aspect of the application, a computer-readable storage medium is disclosed, which may include computer instructions, which may be an electronic memory such as a flash memory, an EEPROM (electrically erasable programmable read Only memory), an EPROM, a hard disk, or a ROM. Optionally, the computer readable storage medium comprises a Non-volatile computer readable storage medium (Non-Transitory Computer-Readable Storage Medium). The computer readable storage medium has storage space for program code to perform any of the method steps described above.
According to one aspect of the present application, a computer program product or computer program is disclosed, the computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the vehicle reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions so that the vehicle performs the methods disclosed in the various alternative implementations disclosed in the above embodiments.
Although the present application has been described in terms of the preferred embodiments, it should be understood that the present application is not limited to the specific embodiments, but is capable of numerous modifications and equivalents, and alternative embodiments and modifications of the embodiments described above, without departing from the spirit and scope of the present application.
Claims (10)
1. A service scheduling method, wherein the method is applied to a vehicle end, and the method comprises:
Acquiring a service call request of a user for a target service; the service calling request comprises a target service identifier corresponding to the service to be called;
Determining whether available target services exist in an identification database according to the target service identifier;
And calling the service content of the target service from a service providing end under the condition that the target service available in the identification database.
2. The method of claim 1, wherein the method further comprises:
receiving release content from the service providing end; the release content comprises a plurality of services and a plurality of identifiers, wherein the plurality of services are in one-to-one correspondence with the plurality of identifiers;
And respectively registering the plurality of services in the identification database according to the plurality of identifiers so as to update the identification database.
3. The method of claim 1, wherein said determining whether there is a target service available in an identification database based on the target service identifier comprises:
Under the condition that the target service corresponding to the target service identifier exists in the identification database, determining description information corresponding to the target service according to the target service identifier;
And determining whether available target services exist in the identification database according to the description information.
4. The method of claim 3, wherein the description information includes availability information and rights information, and wherein determining whether a target service is available in the identification database based on the description information includes:
determining whether the target service is available according to the availability information;
Determining whether the vehicle end has the authority to use the service providing end corresponding to the target service according to the authority information under the condition that the target service is available;
And under the condition of having the authority of using the service provider corresponding to the target service, determining that the target service is available in the identification database.
5. The method of claim 1, wherein the method further comprises:
Under the condition that the available target service does not exist in the identification database, inquiring service information of a service providing end corresponding to the target service at each network segment node;
And storing the service information of the target service to the identification database under the condition that the service information of the target service is queried.
6. The method of any one of claims 1-5, wherein the method further comprises:
recording the calling information of the target service and the using information of the service content of the target service;
Tracking the target service according to the calling information and the using information to obtain tracking information of the target service; the tracking information is used for evaluating the quality of the target service.
7. The method of claim 1, wherein the method further comprises:
Creating an identification database;
acquiring service information corresponding to a plurality of services from the service providing end; wherein the service information comprises a plurality of identifiers corresponding to a plurality of services;
storing service information corresponding to the plurality of services to the identification database;
the determining whether the target service is available in the identification database according to the target service identifier comprises:
and inquiring whether identifiers consistent with the target service identifier exist in a plurality of identifiers corresponding to a plurality of services in the identification database so as to determine the target service.
8. A service dispatch device for application to a vehicle end, the device comprising:
The acquisition unit is used for acquiring a service call request of a user to a target service; the service calling request comprises a target service identifier corresponding to the service to be called;
A determining unit, configured to determine whether there is an available target service in the identification database according to the target service identifier;
And the calling unit is used for calling the service content of the target service from the service providing end under the condition that the available target service exists in the identification database.
9. A vehicle comprising a memory storing a computer program and a processor invoking the computer program to implement the method of any of claims 1-7.
10. A computer readable storage medium, characterized in that the computer readable storage medium has stored therein a computer program or computer instructions, which, when executed by a processor, implement the method of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311681364.6A CN117914674A (en) | 2023-12-07 | 2023-12-07 | Service scheduling method, device, vehicle and computer storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311681364.6A CN117914674A (en) | 2023-12-07 | 2023-12-07 | Service scheduling method, device, vehicle and computer storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117914674A true CN117914674A (en) | 2024-04-19 |
Family
ID=90684703
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311681364.6A Pending CN117914674A (en) | 2023-12-07 | 2023-12-07 | Service scheduling method, device, vehicle and computer storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117914674A (en) |
-
2023
- 2023-12-07 CN CN202311681364.6A patent/CN117914674A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110166409B (en) | Device access method, related platform and computer storage medium | |
| CN109428749B (en) | Network management method and related equipment | |
| CN107592367B (en) | Resource sharing method and device for household appliances and computer readable storage medium | |
| CN111345008B (en) | Mobile edge host service notification method and device | |
| US9323587B2 (en) | Method and system for automatic detecting and resolving APIs | |
| CN109618176B (en) | Processing method, equipment and storage medium for live broadcast service | |
| CN110413418B (en) | Cache synchronization device and method, cache synchronization system and electronic equipment | |
| US10681184B2 (en) | Method and device for transmitting a message in a vehicle | |
| CN114756306A (en) | Service calling method, device, equipment and storage medium | |
| CN114301990A (en) | Node scheduling method, device and storage medium based on content distribution network | |
| CN115562757A (en) | Data processing method, configuration center system, electronic device, and storage medium | |
| CN114826866B (en) | Cross-platform microservice architecture, computing device and storage medium | |
| CN117914674A (en) | Service scheduling method, device, vehicle and computer storage medium | |
| CN110784510A (en) | Method for accessing target service node to bus and information interaction method of service node | |
| CN113596795B (en) | Device binding method, device and computer readable storage medium | |
| CN114726905B (en) | Method, device, equipment and storage medium for accessing Tbox network into Android system | |
| CN114189893B (en) | O-RAN capability opening method, communication system, device and storage medium | |
| CN110943975B (en) | Service registration method, device, computer equipment and storage medium | |
| CN114356456A (en) | Service processing method, device, storage medium and electronic equipment | |
| CN113489848B (en) | Terminal equipment testing method and device, electronic equipment and storage medium | |
| CN114629791B (en) | Data processing method, device, electronic equipment and computer readable storage medium | |
| CN115001889B (en) | Device control method, electronic device and storage medium | |
| CN115767478A (en) | Vehicle cloud communication method based on service-oriented architecture and storage medium | |
| CN114371944A (en) | Distributed service remote calling method, system, device and storage medium | |
| CN117261788A (en) | Vehicle-mounted function operation method and device, vehicle and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination |