CN113014859A

CN113014859A - System, method and device for obtaining video data and electronic equipment

Info

Publication number: CN113014859A
Application number: CN201911322462.4A
Authority: CN
Inventors: 邓永龙
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2019-12-20
Filing date: 2019-12-20
Publication date: 2021-06-22
Anticipated expiration: 2039-12-20
Also published as: CN113014859B

Abstract

The embodiment of the application discloses a system, a method and a device for obtaining video data and electronic equipment. The method comprises the following steps: loading a component for acquiring video data according to different video data acquisition modes by a third client; when the access interface provided for a second client associated with the entity shop is called, acquiring target video data acquisition mode information and identification information of a target camera issued by the second client, wherein the target video data acquisition mode information and the identification information of the target camera are determined by the first client and issued to the second client through the first server; and determining a target component corresponding to the target video data acquisition mode information, acquiring video data acquired by the target camera according to the target video data acquisition mode through the target component, and submitting the video data to the second client so that the second client can push the video data to the second server for the first client to acquire. Thus, personalized plug flow processing for the user can be realized.

Description

System, method and device for obtaining video data and electronic equipment

Technical Field

The present application relates to the field of information processing technologies, and in particular, to a system, a method, an apparatus, and an electronic device for obtaining video data, and a method, an apparatus, and an electronic device for loading a component.

Background

Generally, cameras are distributed in an online entity store for collecting video data in the store, and the video data can be uploaded to a cloud server for data analysis and data tracing.

Taking a physical store in a new retail business mode as an example, with continuous upgrading of technologies and continuous innovation of business modes, hundreds of cameras may be arranged in the store, and if all video data acquired by the cameras are uploaded to a cloud server, a large amount of network transmission resources and cloud server storage resources are consumed, and the data storage cost is high. In response to this, video data storage is currently mainly performed by the following two schemes.

According to the first scheme, part of video data is uploaded to a cloud server. Specifically, a designated area where the store needs to pay attention to in a focused manner can be determined, and the video data acquired by the camera in the designated area is uploaded to the cloud, for example, a cash register area and a processing area can be determined as the designated area, and the video data can be acquired and uploaded. Or, the cloud end can be uploaded with the partial video data that the camera was gathered, for example, someone is through in the camera coverage, can trigger the camera and carry out video data's collection and upload.

In the second scheme, the Video data collected by the camera is stored locally, for example, the Video data can be stored in a locally-distributed NVR (Network Video Recorder). Under the scheme, how to carry out stream pushing processing on the local video data according to the user requirements becomes a technical problem to be solved by technical personnel.

Disclosure of Invention

The application provides a system, a method and a device for obtaining video data and electronic equipment, and a method and a device for loading components and electronic equipment. At least one component can be configured in the third client side associated with the camera, and different components can obtain video data acquired by the camera according to different video data acquisition modes, so that the video data meeting different requirements of the user can be pushed.

The application provides the following scheme:

a system for obtaining video data, comprising:

a first client, a second client, a third client, a first server and a second server,

the first service end is used for forwarding a stream pushing request submitted by the first client end to the second client end, wherein the stream pushing request comprises target video data acquisition mode information and identification information of a target camera;

and the second client is used for determining a third client associated with the target camera, acquiring video data acquired by the target camera according to the target video data acquisition mode through a component configured in the third client, and pushing the video data to a second server for the first client to acquire.

A method for obtaining video data, comprising:

the first client provides optional video data acquisition mode information and optional camera information;

when a target video data acquisition mode and a target camera are selected, generating a stream pushing request, submitting the stream pushing request to a first service end so that the first service end can send the stream pushing request to a second client end associated with a target entity shop to which the target camera belongs, and the second client end obtains video data acquired by the target camera according to the target video data acquisition mode through a component configured in a third client end associated with the target camera and pushes the video data to the second service end;

and obtaining the video data from the second server.

A method for obtaining video data, comprising:

a second client associated with the entity store acquires a stream pushing request issued by a first server, wherein the stream pushing request is submitted to the first server by the first client and comprises target video data acquisition mode information and identification information of a target camera;

determining a third client associated with the target camera, and acquiring video data acquired by the target camera according to the target video data acquisition mode through a component configured in the third client;

and pushing the video data to a second server for the first client to obtain.

A method for obtaining video data, comprising:

loading a component for acquiring video data according to different video data acquisition modes by a third client;

when the access interface provided for a second client associated with the entity shop is called, acquiring target video data acquisition mode information and identification information of a target camera issued by the second client, wherein the target video data acquisition mode information and the identification information of the target camera are determined by the first client and issued to the second client through a first server;

and determining a target component corresponding to the target video data acquisition mode information, acquiring video data acquired by the target camera according to the target video data acquisition mode through the target component, and submitting the video data to the second client, so that the second client can push the video data to a second server for the first client to acquire.

A method for obtaining video data, comprising:

the method comprises the steps that a first server side obtains identification information of cameras associated with all entity shops;

acquiring a stream pushing request submitted by a first client, wherein the stream pushing request comprises target video data acquisition mode information and identification information of a target camera;

and determining a target entity shop associated with the target camera, and issuing the plug-flow request to a second client associated with the target entity shop, so that the second client can obtain video data acquired by the target camera according to the target video data acquisition mode through a component configured in a third client associated with the target camera and push the video data to a second server for the first client to acquire.

A method for loading a component, comprising:

a third server side obtains a component information base, wherein a component related to video data obtaining mode information related to the operation of the entity shop is stored in the component information base, and the component is used for obtaining video data in the entity shop according to the related video data obtaining mode;

obtaining a configuration request submitted by a third client, wherein the configuration request comprises optional video data acquisition mode information corresponding to a user associated with a first client, and the first client can request the third client to perform stream pushing processing;

and determining a target component associated with the optional video data acquisition mode information, and loading the target component to the third client, so that the third client can provide a push streaming service for the first client through the target component.

A method for obtaining video data, comprising:

the third client acquires video data acquisition mode information associated with different users and loads components for acquiring video data according to different video data acquisition modes;

when the access interface provided for a second client associated with an entity shop is called, acquiring identification information of a target user associated with a first client and identification information of a target camera issued by the second client, wherein the identification information of the target user and the identification information of the target camera are determined by the first client and issued to the second client through a first server;

determining target video data acquisition mode information associated with the target user and a target component corresponding to the target video data acquisition mode information;

and video data acquired by the target camera according to the target video data acquisition mode is acquired through the target assembly and submitted to the second client, so that the second client can push the video data to a second server for the first client to acquire.

A method for obtaining video data, comprising:

a second client associated with an entity shop obtains a plug flow request issued by a first server, wherein the plug flow request is submitted to the first server by the first client and comprises identification information of a target user associated with the first client and identification information of a target camera;

determining a third client associated with the target camera, calling an access interface of the third client by taking the identification information of the target user and the identification information of the target camera as parameters, and acquiring video data acquired by the target camera according to a target video data acquisition mode associated with the target user through a component configured in the third client;

and pushing the video data to a second server for the first client to obtain.

A method for obtaining video data, comprising:

obtaining a flow pushing request submitted by a first client, wherein the flow pushing request comprises identification information of a target user and identification information of a target camera, which are associated with the first client;

and determining a target entity shop associated with the target camera, and issuing the plug-flow request to a second client associated with the target entity shop, so that the second client can obtain video data acquired by the target camera according to a target video data acquisition mode associated with the target user through a component configured in a third client associated with the target camera, and push the video data to a second server for the first client to acquire.

A method for obtaining video data, comprising:

the method comprises the steps that a first server side obtains identification information of cameras associated with all entity shops and video data obtaining mode information associated with different users;

determining target video data acquisition mode information associated with the target user and a target entity shop associated with the target camera;

and issuing the target video data acquisition mode information and the identification information of the target camera to a second client associated with the target entity shop, so that the second client can acquire video data acquired by the target camera according to the target video data acquisition mode through a component configured in a third client associated with the target camera and push the video data to a second server for the first client to acquire.

A method for obtaining video data, comprising:

a second client associated with the entity shop obtains video data acquisition mode information associated with different users;

obtaining a flow pushing request issued by a first server, wherein the flow pushing request is submitted to the first server by a first client, and the flow pushing request comprises identification information of a target user and identification information of a target camera, which are associated with the first client;

determining target video data acquisition mode information associated with the target user and a third client associated with the target camera;

and calling an access interface of the third client, acquiring video data acquired by the target camera according to the target video data acquisition mode through a component configured in the third client, and pushing the video data to a second server for the first client to acquire.

A method for obtaining video data, comprising:

when a target video data acquisition mode and a target camera are selected, generating a stream pushing request, submitting the stream pushing request to a first service end so that the first service end can send the stream pushing request to a second client end associated with a target organization to which the target camera belongs, and the second client end obtains video data acquired by the target camera according to the target video data acquisition mode through a component configured in a third client end associated with the target camera and pushes the video data to the second service end;

and obtaining the video data from the second server.

A method for obtaining video data, comprising:

when the access interface provided for a second client associated with a target organization is called, acquiring identification information of a target user associated with a first client and identification information of a target camera issued by the second client, wherein the identification information of the target user and the identification information of the target camera are determined by the first client and issued to the second client through a first server;

A method for obtaining video data, comprising:

the first server side obtains identification information of cameras related to each organization and video data obtaining mode information related to different users;

determining target video data acquisition mode information associated with the target user and target organization associated with the target camera;

and issuing the target video data acquisition mode information and the identification information of the target camera to a second client associated with the target organization, so that the second client can acquire video data acquired by the target camera according to the target video data acquisition mode through a component configured in a third client associated with the target camera and push the video data to a second server for the first client to acquire.

A method for obtaining video data, comprising:

a second client associated with a target organization acquires video data acquisition mode information associated with different users;

A method for loading a component, comprising:

a third server side obtains a component information base, wherein components related to video data acquisition mode information related to target organization operation are stored in the component information base, and the components are used for acquiring video data in a target organization according to the related video data acquisition mode;

An apparatus for obtaining video data, applied to a first client, comprises:

the information providing unit is used for providing optional video data acquisition mode information and optional camera information;

a plug flow request submitting unit, configured to generate a plug flow request when a target video data acquisition manner and a target camera are selected, and submit the plug flow request to a first service end, so that the first service end issues the plug flow request to a second client associated with a target entity store to which the target camera belongs, and the second client obtains video data acquired by the target camera according to the target video data acquisition manner through an assembly configured in a third client associated with the target camera and pushes the video data to the second service end;

and the video data obtaining unit is used for obtaining the video data from the second server.

An apparatus for obtaining video data, applied to a second client associated with a physical store, comprising:

the system comprises a push flow request obtaining unit, a push flow request obtaining unit and a push flow processing unit, wherein the push flow request obtaining unit is used for obtaining a push flow request issued by a first service end, the push flow request is submitted to the first service end by a first client end, and the push flow request comprises target video data obtaining mode information and identification information of a target camera;

the video data acquisition unit is used for determining a third client associated with the target camera and acquiring video data acquired by the target camera according to the target video data acquisition mode through a component configured in the third client;

and the video data pushing unit is used for pushing the video data to a second server for the first client to obtain.

An apparatus for obtaining video data, applied to a third client, includes:

the component loading unit is used for loading components for acquiring video data according to different video data acquisition modes;

the system comprises an interface calling unit, a first server and a second server, wherein the interface calling unit is used for obtaining target video data acquisition mode information and identification information of a target camera issued by a second client when an access interface provided for the second client associated with an entity shop is called, and the target video data acquisition mode information and the identification information of the target camera are determined by the first client and issued to the second client through the first server;

and the video data submitting unit is used for determining a target component corresponding to the target video data acquisition mode information, acquiring video data acquired by the target camera according to the target video data acquisition mode through the target component, and submitting the video data to the second client so that the second client can push the video data to a second server for the first client to acquire.

An apparatus for obtaining video data, applied to a first service end, comprising:

the system comprises an incidence relation obtaining unit, a correlation obtaining unit and a correlation obtaining unit, wherein the incidence relation obtaining unit is used for obtaining identification information of cameras associated with all entity shops;

the system comprises a push flow request obtaining unit, a push flow request obtaining unit and a push flow control unit, wherein the push flow request obtaining unit is used for obtaining a push flow request submitted by a first client, and the push flow request comprises target video data obtaining mode information and identification information of a target camera;

and the stream pushing request issuing unit is used for determining a target entity shop associated with the target camera and issuing the stream pushing request to a second client associated with the target entity shop, so that the second client can obtain video data acquired by the target camera according to the target video data acquisition mode through a component configured in a third client associated with the target camera and push the video data to a second server for the first client to acquire.

An apparatus for loading a component, applied to a third server, includes:

an information base obtaining unit, configured to obtain a component information base, in which a component associated with video data obtaining manner information related to an actual store job is stored, and the component is configured to obtain video data in the actual store according to the associated video data obtaining manner;

a configuration request obtaining unit, configured to obtain a configuration request submitted by a third client, where the configuration request includes information about an optional video data obtaining manner corresponding to a user associated with a first client, and the first client may request the third client to perform stream pushing processing;

and the component loading unit is used for determining a target component associated with the optional video data acquisition mode information and loading the target component to the third client so that the third client can provide the push streaming service for the first client through the target component.

An apparatus for obtaining video data, applied to a third client, includes:

the incidence relation obtaining unit is used for obtaining video data obtaining mode information associated with different users;

the system comprises an interface calling unit, a first server and a second server, wherein the interface calling unit is used for obtaining identification information of a target user and identification information of a target camera which are associated with a first client and issued by the second client when an access interface provided for the second client associated with an entity shop is called, and the identification information of the target user and the identification information of the target camera are determined by the first client and issued to the second client through the first server;

the target component determining unit is used for determining target video data acquisition mode information associated with the target user and a target component corresponding to the target video data acquisition mode information;

and the video data submitting unit is used for obtaining the video data acquired by the target camera according to the target video data acquisition mode through the target component and submitting the video data to the second client so that the second client can push the video data to a second server for the first client to acquire.

a push flow request obtaining unit, configured to obtain a push flow request issued by a first service end, where the push flow request is submitted to the first service end by a first client, and the push flow request includes identification information of a target user and identification information of a target camera associated with the first client;

a video data obtaining unit, configured to determine a third client associated with the target camera, call an access interface of the third client using the identification information of the target user and the identification information of the target camera as parameters, and obtain, through a component configured in the third client, video data acquired by the target camera in a target video data acquisition manner associated with the target user;

a push flow request obtaining unit, configured to obtain a push flow request submitted by a first client, where the push flow request includes identification information of a target user and identification information of a target camera associated with the first client;

and the stream pushing request issuing unit is used for determining a target entity shop associated with the target camera and issuing the stream pushing request to a second client associated with the target entity shop, so that the second client can obtain video data acquired by the target camera according to a target video data acquisition mode associated with the target user through a component configured in a third client associated with the target camera and push the video data to a second server for the first client to acquire.

the system comprises an incidence relation obtaining unit, a video data obtaining unit and a video data obtaining unit, wherein the incidence relation obtaining unit is used for obtaining identification information of cameras associated with all entity shops and video data obtaining mode information associated with different users;

the information determining unit is used for determining target video data acquisition mode information related to the target user and a target entity shop related to the target camera;

and the information issuing unit is used for issuing the target video data acquisition mode information and the identification information of the target camera to a second client associated with the target entity shop, so that the second client can obtain the video data acquired by the target camera according to the target video data acquisition mode through a component configured in a third client associated with the target camera and push the video data to a second server for the first client to acquire.

the information determining unit is used for determining target video data acquisition mode information associated with the target user and a third client associated with the target camera;

and the video data pushing unit is used for calling an access interface of the third client, acquiring video data acquired by the target camera according to the target video data acquisition mode through a component configured in the third client, and pushing the video data to a second server for the first client to acquire.

An apparatus for obtaining video data, applied to a first client, comprises:

a stream pushing request submitting unit, configured to generate a stream pushing request when a target video data acquisition mode and a target camera are selected, and submit the stream pushing request to a first service end, so that the first service end issues the stream pushing request to a second client associated with a target organization to which the target camera belongs, and the second client obtains video data acquired by the target camera according to the target video data acquisition mode through a component configured in a third client associated with the target camera and pushes the video data to the second service end;

An apparatus for obtaining video data, applied to a third client, includes:

the system comprises an interface calling unit, a first server and a second server, wherein the interface calling unit is used for acquiring identification information of a target user and identification information of a target camera which are associated with a first client and issued by a second client when an access interface provided for the second client associated with a target organization is called, and the identification information of the target user and the identification information of the target camera are determined by the first client and issued to the second client through the first server;

the system comprises an incidence relation obtaining unit, a video data obtaining unit and a video data obtaining unit, wherein the incidence relation obtaining unit is used for obtaining identification information of cameras relevant to various organizations and video data obtaining mode information relevant to different users;

the information determining unit is used for determining target video data acquisition mode information related to the target user and target organization related to the target camera;

and the information issuing unit is used for issuing the target video data acquisition mode information and the identification information of the target camera to a second client associated with the target organization, so that the second client can obtain the video data acquired by the target camera according to the target video data acquisition mode through a component configured in a third client associated with the target camera and push the video data to a second server for the first client to acquire.

An apparatus for obtaining video data, applied to a second client associated with a target organization, comprising:

An apparatus for loading a component, applied to a third server, includes:

an information base obtaining unit, configured to obtain a component information base, where a component associated with video data obtaining mode information related to a target organization job is stored in the component information base, and the component is configured to obtain video data in the target organization according to the associated video data obtaining mode;

a configuration request unit, configured to obtain a configuration request submitted by a third client, where the configuration request includes information about an optional video data acquisition mode corresponding to a user associated with a first client, and the first client may request the third client to perform stream pushing processing;

An electronic device, comprising:

one or more processors; and

a memory associated with the one or more processors for storing program instructions that, when read and executed by the one or more processors, perform operations comprising:

providing optional video data acquisition mode information and optional camera information;

and obtaining the video data from the second server.

An electronic device, comprising:

one or more processors; and

obtaining a stream pushing request issued by a first server, wherein the stream pushing request is submitted to the first server by a first client, and the stream pushing request comprises target video data acquisition mode information and identification information of a target camera;

and pushing the video data to a second server for the first client to obtain.

An electronic device, comprising:

one or more processors; and

loading a component for obtaining video data according to different video data acquisition modes;

An electronic device, comprising:

one or more processors; and

obtaining identification information of cameras associated with each entity shop;

An electronic device, comprising:

one or more processors; and

the method comprises the steps of obtaining a component information base, wherein components related to video data obtaining mode information related to physical shop operation are stored in the component information base, and the components are used for obtaining video data in the physical shop according to the related video data obtaining mode;

An electronic device, comprising:

one or more processors; and

acquiring video data acquisition mode information associated with different users, and loading components for acquiring video data according to different video data acquisition modes;

An electronic device, comprising:

one or more processors; and

and pushing the video data to a second server for the first client to obtain.

An electronic device, comprising:

one or more processors; and

An electronic device, comprising:

one or more processors; and

acquiring identification information of cameras associated with each entity shop and video data acquisition mode information associated with different users;

An electronic device, comprising:

one or more processors; and

acquiring video data acquisition mode information related to the operation of the entity shop and associated with different users;

An electronic device, comprising:

one or more processors; and

and obtaining the video data from the second server.

An electronic device, comprising:

one or more processors; and

An electronic device, comprising:

one or more processors; and

acquiring identification information of cameras associated with various organizations and video data acquisition mode information associated with different users;

An electronic device, comprising:

one or more processors; and

acquiring video data acquisition mode information related to target organization jobs and associated with different users;

An electronic device, comprising:

one or more processors; and

acquiring a component information base, wherein components related to video data acquisition mode information related to target organization operation are stored in the component information base, and the components are used for acquiring video data in the target organization according to the related video data acquisition mode;

According to the specific embodiments provided herein, the present application discloses the following technical effects:

in the embodiment of the application, at least one piece of video data acquisition mode information can be determined according to user requirements, a corresponding component can be provided for each video data acquisition mode, and the video data acquired by the camera can be acquired according to the corresponding video data acquisition mode when the component runs.

Specifically, the component corresponding to the user requirement can be loaded to the third client associated with the target camera, so that the third client can determine the target component from the loaded component according to the use requirement of the user associated with the first client, namely the target video data acquisition mode information, obtain the video data acquired by the target camera according to the target video data acquisition mode through the target component, push the video data to the second server, and pull the video data by the first client. Therefore, the video data meeting the requirements of different users can be pushed, and personalized stream pushing processing aiming at the users is realized.

Of course, it is not necessary for any product to achieve all of the above-described advantages at the same time for the practice of the present application.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.

FIG. 1 is a schematic diagram of a system provided by an embodiment of the present application;

FIGS. 2-22 are flow charts of methods provided by embodiments of the present application;

FIGS. 23-32 are schematic views of apparatus provided by embodiments of the present application;

FIG. 33 is a schematic diagram of an architecture of a computer system provided by an embodiment of the present application;

fig. 34 is a schematic diagram of an architecture of an electronic device provided in an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments that can be derived from the embodiments given herein by a person of ordinary skill in the art are intended to be within the scope of the present disclosure.

In order to facilitate understanding of a specific implementation scheme provided in the embodiment of the present application, a specific scenario of the scheme is briefly introduced below.

The embodiment of the application provides a tool for obtaining video data in a physical shop, referring to a schematic diagram shown in fig. 1, which may include: the system comprises a first client, a second client, a third client, a first server and a second server. The first client can be deployed on terminal equipment associated with a user, a flow pushing request is submitted to a first service end deployed on a cloud server, and the first service end forwards the flow pushing request to a second client for flow pushing processing. Specifically, a first client may be deployed on a terminal device outside a physical store as shown in fig. 1, and request to obtain video data collected in the store; or the mobile terminal may be deployed on a terminal device in a physical store, which may not be specifically limited in the embodiment of the present application.

The second client can be deployed on terminal equipment arranged in a shop, for example, on an industrial personal computer arranged in the shop, and can interact with a third client associated with the camera, and video data collected by the camera is obtained through a component loaded by the third client. The association relationship between the camera and the third client may be one-to-one, for example, the third client is deployed on the camera, acquires video data in the shop, which is acquired by the camera in real time, and pushes the video data to the second server, so that the first client pulls the video data from the second server. Or, the association relationship between the cameras and the third client may be many-to-one, for example, the third client is deployed on a Network Video Recorder (NVR), one NVR can access multiple cameras, and the third client may associate with the multiple cameras, acquire historical Video data stored in the NVR by the cameras, and push the historical Video data to the second server, so that the first client pulls the Video data from the second server.

When video plug-flow processing is carried out, different users may have different requirements correspondingly and need to obtain different video data, so that at least one piece of video data obtaining mode information can be preset according to different user requirements, meanwhile, a corresponding component can be provided for each video data obtaining mode, video data matched with the video data obtaining mode information are obtained through the component, and the video data are pushed to the users.

The following explains an implementation process of loading a component at a third client according to an embodiment of the present application with reference to the flowchart shown in fig. 2.

Example 1

S101: and the third server side obtains a component information base, wherein components related to video data acquisition mode information related to the operation of the physical shop are stored in the component information base, and the components are used for obtaining the video data in the physical shop according to the related video data acquisition mode.

The video data acquisition mode information can be defined by combining with actual use requirements. For example, for the store leader of the physical store, to view the daily morning meeting situation, it may be defined that the video data acquisition mode information 1 requests to acquire video data related to the morning meeting; for the inspection personnel of the entity shop, the inspection personnel want to check whether the placement of the commodity object in the shop meets the requirements, so that the video data acquisition mode information 2 can be defined to request to acquire the video data when the commodity object is abnormally placed; for the troubleshooting personnel to be able to do so,

correspondingly, the third server can provide the components corresponding to the video data acquisition mode information, and determine the target component from the stored components to load to the third client according to the use requirement. In the embodiment of the application, the component can be developed and released to the third server for storage by a developer of a new retail service provider, or the third server can provide a calling interface for other third-party service providers to obtain the component developed and released by the developer of the third-party service provider.

For the above example, the information stored in the component information repository may be as shown in table 1 below.

TABLE 1

Identification information of video data acquisition mode	Identification information of a component
		Video data acquisition mode information 1	Component 1
Video data acquisition mode information 2	Component 2

S102: the method comprises the steps of obtaining a configuration request submitted by a third client, wherein the configuration request comprises optional video data acquisition mode information corresponding to a user associated with a first client, and the first client can request the third client to carry out stream pushing processing.

S103: and determining a target component associated with the optional video data acquisition mode information, and loading the target component to the third client, so that the third client can provide a push streaming service for the first client through the target component.

When component configuration is carried out on the third client, video data acquisition mode information representing the user plug flow requirement can be obtained, and then the target component is determined to be loaded to the third client.

In one mode, a first client requesting a third client to perform stream pushing processing may submit a configuration request to a third server, and submit optional video data acquisition mode information corresponding to a user associated with the first client to the third server. Taking the physical store 1 as an example, the camera 11 may collect video data of an early meeting area, the store manager 1 may submit a configuration request to the third server through the associated first client 1, and the configuration request may include identification information of the first client 1, identification information of the third client 1 associated with the camera 11, and video data acquisition mode information 1. Correspondingly, the third server may determine the component 1 as a target component, and load the target component into the third client 1, so that when the first client 1 requests to perform the stream pushing process, the running component 1 obtains video data related to the morning meeting and pushes the video data to the store manager 1 for viewing.

Or, in another mode, when the store information is initialized, the developer submits a configuration request to the third server through its associated client, and triggers the third server to load the target component corresponding to the user requirement for the third client deployed in the physical store.

S104: and the third client acquires corresponding video data through the loaded target component according to the request of the second client and submits the video data to the second client.

After loading the target component corresponding to the user requirement according to the configuration of the third server, the third client may call the target component to obtain the video data matched with the user requirement if obtaining the information related to the stream pushing request issued by the second client, and push the video data to the second server through the second client for the first client to pull the video data.

As an example, video data acquisition mode information representing user requirements may be configured at a first client, a user determines target video data acquisition mode information according to current requirements, and the target video data acquisition mode information is issued to a third client through a first server and a second client, so that a target component associated with the target video data acquisition mode information configured in the third client acquires corresponding video data.

The following explains an implementation process of obtaining video data according to an embodiment of the present application with reference to a flowchart shown in fig. 3.

Example 2

S201: the first client provides optional video data acquisition mode information and optional camera information, and when a target video data acquisition mode and a target camera are selected, a stream pushing request is generated and submitted to the first server.

In the embodiment of the application, the first client can display all the video data acquisition mode information, so that a user can determine at least one optional video data acquisition mode information. Taking the store leader 1 of the entity store 1 as an example, 5 pieces of optional video data acquisition mode information are determined according to actual application requirements, and when the store leader requests for stream pushing processing, the first client 1 can display the 5 pieces of optional video data acquisition mode information and optional camera information deployed in the store 1 to the store leader for viewing, so that the store leader determines a target video data acquisition mode and a target camera from the information, generates a stream pushing request, and submits the stream pushing request to the first server. For example, when the store manager 1 requests to view video data related to a meeting morning, the push stream request may include video data acquisition mode information 1 and identification information of the camera 11.

S202: and the first server determines a target entity shop associated with the target camera according to the association relationship between the entity shop and the camera, and issues the plug-flow request to a second client associated with the target entity shop.

In the embodiment of the application, the first server can obtain the identification information of the cameras associated with the entity stores, so that after the plug-flow request submitted by the first client is obtained, the target entity store deployed by the target camera can be determined according to the plug-flow request, the plug-flow request is issued to the second client associated with the target entity store, and the second client is triggered to perform plug-flow processing.

For the physical store 1, if a single store is in a local area network, a second client may be set in the store, and the second client performs stream pushing processing on video data collected by a camera in the local area network. Correspondingly, the association relationship saved by the first server may be as shown in table 2 below.

TABLE 2

For the physical store 2, if a plurality of regions (for example, a fruit region, a seafood region, a food processing region, a packaging region, and the like) divided by the store belong to different local area networks, one second client corresponding to the plug-flow processing may be respectively provided in the different local area networks, that is, one store may be associated with a plurality of second clients. Correspondingly, the association relationship stored by the first server may be as shown in table 3 below.

TABLE 3

Correspondingly, the first server can determine a second client located in the local area network where the target camera is located, and the second client performs stream pushing processing on the video data acquired by the target camera.

S203: and the main process in the second client acquires the stream pushing request issued by the first server, and forwards the target video data acquisition mode information and the identification information of the target camera, which are analyzed from the stream pushing request, to the first sub-process.

S204: and the first sub-process determines a third client associated with the target camera, obtains video data acquired by the target camera according to a target video data acquisition mode through a component configured in the third client, and pushes the video data to the second server.

The second client in the embodiment of the present application may have various implementations. For example, in one approach, to improve the stability of the plug flow process, the second client may include a main process and a first sub-process. The main process can interact with the first server to obtain a stream pushing request issued by the first server, and perform task analysis to obtain target video data acquisition mode information and identification information of a target camera and forward the target video data acquisition mode information and the identification information to the first sub-process; the first sub-process can interact with the third client, interface calling is carried out after the third client associated with the target camera is determined, video data collected by the target camera according to a target video data obtaining mode are obtained, and the video data are pushed to the second server.

In an actual application process, for a camera and NVR, a problem may occur due to an unstable communication link, an operating system, and hardware devices, which may cause a first sub-process to crash when making an interface call, and in order to ensure normal execution of a subsequent stream pushing request, a main process may create (for example, may create at the time of starting the main process) two sub-processes for performing stream pushing processing: and the first sub-process and the second sub-process can both integrate access interface information of a third client associated with the camera in the entity shop.

The first sub-process can be used as a working process and carries out flow pushing processing according to the information forwarded by the main process; the second sub-process may be enabled as a standby process for the plug flow process when the first sub-process is not available. Specifically, the main process may obtain the working state information of the first sub-process through inter-process communication (IPC), and if the working state information indicates that the first sub-process is unavailable, the second sub-process may be enabled, and a new plug flow request issued by the first service end is forwarded to the second sub-process, at this time, the second sub-process may be used as a new working process to perform plug flow processing.

Preferably, when the second sub-process is enabled, the main process may further create a corresponding standby sub-process for the second sub-process: and the third sub-process can also integrate the access interface information of a third client related to the camera in the physical shop. Meanwhile, the main process can obtain the working state information of the second sub-process through interprocess communication, and accordingly determine whether to start the third sub-process. That is, except for the working process that is performing the push flow processing, the second client may always have at least one standby process that can be started at any time, so that when the working process is unavailable, the second client switches to the standby process without sensing, and it is ensured that the push flow request issued by the first server can be performed normally.

That is to say, the second client in the embodiment of the present application may separate the control function from the push flow function, and for the control function with stronger stability, the main process may be responsible for executing the control function, and for the push flow function that needs to interact with the third client, the stability is relatively poorer, and the sub process may be responsible for executing the push flow function. Therefore, when the working process is crashed and unavailable, the main process can start the standby process and create a new standby process for the started standby process, and therefore local video data can be stably and reliably uploaded to the cloud end for a user to pull the video data from the cloud end.

Preferably, the host process may report the working state of the second client to the first service end. For example, information that the first sub-process is unavailable may be reported to the first service end; or, the information for starting the second sub-process may be reported to the first service end; or, the information for creating the third sub-process may be reported to the first service end; or, the relevant information of the push flow request being executed when the first sub-process is unavailable may be reported to the first service end, so that the first service end may issue the push flow request to the second client again for push flow processing.

It can be understood that each time the main process starts the standby process, it is equivalent to performing a self-recovery, so that the main process can perform logging to generate the warning information to be submitted to the first service end when necessary. Specifically, the main process may obtain the number of times of creating the third sub-process within a specified time period, generate the warning information according to the number of times, and submit the warning information to the first service end. For example, if the main process creates 3 times of standby processes within 5 minutes, the warning information may be generated and submitted to the first service end, and the warning information is forwarded to the fourth client by the first service end, so as to notify the fourth client of the associated user to perform troubleshooting.

Or, in another mode, the control function may be further split, for example, the control function is split into two parts, i.e., interacting with the first service end and performing a push flow request analysis. That is, the second client may include a main process, a first sub-process, and a fourth sub-process, where the main process is mainly responsible for interacting with the first server, may obtain a stream pushing request issued by the first server, and forwards the stream pushing request to the fourth sub-process; the fourth sub-process is mainly responsible for analyzing the stream pushing request, and can submit the target video data acquisition mode information obtained by analysis and the identification information of the target camera to the main process, and forward the target video data acquisition mode information and the identification information of the target camera to the first sub-process for stream pushing processing through the main process.

As introduced above, the third client may be deployed in the camera to obtain video data acquired by the camera in real time. Correspondingly, the first sub-process can integrate access interface information of a third client deployed on a camera associated with the entity shop, and then after the information forwarded by the main process is obtained, an access interface of the third client deployed on the target camera is called, so that video data collected by the target camera in real time is obtained.

Or the third client may be deployed in the NVR, and acquire historical video data collected by the camera and stored in the NVR. Correspondingly, the first sub-process can integrate access interface information of a third client deployed on the NVR associated with the entity store, and after the target NVR associated with the target camera is determined, the access interface of the third client deployed on the target NVR is called to obtain historical video data collected by the target camera.

In the embodiment of the application, various implementation manners for determining the target NVR can be provided. For example, in one mode, the first server may obtain an association relationship between the camera and the NVR, and when it is determined that the stream pushing request submitted by the first client is used to obtain the historical video data collected by the target camera, the identification information of the target NVR associated with the target camera may be obtained according to the association relationship, and sent to the second client, and then forwarded to the first sub-process via the main process.

Still taking the entity store 2 as an example, the association relationship stored by the first server may be as shown in table 4 below.

TABLE 4

It is to be understood that table 4 is an example of the association relationship between NVRs and cameras, and does not limit that only one NVR is set in one area shown in table 3. Taking NVR accessing 16-way cameras as an example, if the number of the cameras arranged in a certain area exceeds 16, the cameras in the area can be correspondingly accessed into at least two NVRs.

Or, in another mode, the main process may obtain an association relationship between the camera and the NVR, and when it is determined that the stream pushing request issued by the first service end is used to obtain the historical video data collected by the target camera, may obtain the identification information of the target NVR associated with the target camera according to the association relationship, and forward the identification information to the first sub-process. Or, the first sub-process may obtain the association relationship, and determine a corresponding target NVR according to the identification information of the target camera forwarded by the main process; or, the fourth sub-process may obtain the association relationship, perform task analysis on the stream pushing request forwarded by the main process, obtain the identification information of the target NVR associated with the target camera, submit the identification information to the main process, and forward the identification information to the first sub-process through the main process.

In the actual application process, default setting can be performed on the plug flow processing process according to the use requirement. For example, for a stream pushing request submitted by the first client, the default setting may be set to be used for performing stream pushing processing on video data acquired by the target camera in real time. In the configuration mode, for the plug-flow request submitted by the store owner 1, the first sub-process may call the third client 1 deployed on the camera 11, obtain, through the component 1 configured in the third client 1, real-time video data acquired by the camera 11 according to the target video data acquisition mode, and push the real-time video data to the second server.

Or, for the stream pushing request submitted by the first client, the default setting may also be set to be used for performing stream pushing processing on the historical video data acquired by the target camera. In the configuration mode, for the plug-flow request submitted by the store owner 1, the first sub-process may call a third client deployed on the NVR associated with the camera 11, obtain, through the component 1 configured in the third client, historical video data acquired by the camera 11 according to the target video data acquisition mode, and push the historical video data to the second server.

In addition, the stream pushing request submitted by the first client may further include other condition information, and the first sub-process may perform stream pushing processing on the video data meeting the condition information. For example, in one approach, time period information may be included in the push flow request.

If the time period information is the instant time, for example, the shopkeeper 1 submits the push streaming request at 10:00 of 2019.12.05 including the video data acquisition mode information 1, the identification information of the camera 11 and the time period 10: 00-10: 30, it can be determined that the shopkeeper 1 wants to check the video data acquired by the camera 11 according to the video data acquisition mode information 1 within the next half hour, so that a third client 1 deployed on the camera 11 can be called, the real-time video data acquired by the camera 11 according to the video data acquisition mode information 1 within 10: 00-10: 30 is obtained through the component 1 configured in the third client 1, and the real-time video data is pushed to the second server.

If the time period information is historical time, for example, the shopkeeper 1 submits a push streaming request at 10:00 of 2019.12.05 including video data acquisition mode information 1, identification information of the camera 11, and 10: 00-10: 30 of the time period 2019.12.04, it can be determined that the shopkeeper 1 wants to view historical video data acquired by the camera 11, so a third client deployed on NVR associated with the camera 11 can be called, and historical video data acquired by the camera 11 within 10: 00-10: 30 of 2019.12.04 according to the video data acquisition mode information 1 is obtained through a component 1 configured in the third client and pushed to a second server.

In the embodiment of the application, the target assembly can obtain the video data collected by the target camera according to the target video data obtaining mode in various modes. For example, in one mode, the target camera may continuously collect video data, and the target component may determine video data meeting the user requirement from the video data collected by the target camera and submit the video data to the second client. Taking the example of pushing the video data related to the early meeting to the store leader 1, the camera 11 may be always in a video acquisition state, after the third client obtains the stream pushing request submitted by the store leader 1, the target assembly 1 is started, the target assembly 1 may analyze and identify the video data acquired by the camera 11 (for example, it may be determined that the early meeting scene is determined by analyzing and identifying a multi-person scene through an image recognition technology and a voice recognition technology), and when it is determined that the early meeting scene is matched, the video data related to the early meeting may be intercepted and submitted to the second client.

Or, in another mode, the target assembly can control the target camera to be started when needed, and video data meeting the user requirements are collected. Still taking the example of pushing the video data related to the morning meeting to the store leader 1, the camera 11 may not collect the video data when there is no streaming task, the third client starts the target component 1 after obtaining the streaming request submitted by the store leader 1, and when the target component 1 determines that there are many people in the collection range of the camera 11 (for example, human body perception may be performed through infrared technology), the camera 11 may be triggered to start collecting the video data. Preferably, in order to ensure the accuracy of the video data submitted to the second client, the target component 1 may further analyze and identify the video data collected by the camera 11, determine the video data related to the morning meeting, and then submit the video data to the second client. In addition, when the target assembly 1 determines that the morning meeting ends through analysis and recognition, the camera 11 can be controlled to stop collecting the video data.

S205: the first client obtains video data from the second server.

In the embodiment of the present application, the second server is mainly configured to receive a video stream pushed by the second client, provide a video playing capability for the first client, and may have a push stream address and a play stream address correspondingly. The second client can push the video data to the streaming address, and the first client can pull the video data from the streaming address.

As an example, the stream pushing address and the stream playing address may remain fixed for different stream pushing requests, and corresponding to this, the stream pushing address information may be configured in the first sub-process and the stream playing address information may be configured in the first client. In this way, after the first sub-process obtains the video data submitted by the third client, the video data can be pushed according to the configured stream pushing address information and submitted to the second server; correspondingly, the first client can pull the video data from the second server according to the configured broadcast stream address information. Or, the stream pushing address information and the stream broadcasting address information may be stored in the first service end, and when the stream pushing processing is required, the first service end issues the stream pushing address information to the second client and issues the stream broadcasting address information to the first client.

Or, in another example, different push stream requests may correspond to different push stream addresses and broadcast stream addresses. For example, after obtaining the push stream request submitted by the first client, the first server may submit an address allocation request to the second server, and request the second server to allocate a corresponding push stream address and a corresponding broadcast stream address for the push stream request.

In this example, after obtaining the streaming address information and the streaming address information sent by the second server, the first server may send the streaming address information to the second client, that is, the streaming request sent by the first server may include the streaming address information, and the main process may forward the streaming address information analyzed from the streaming request to the first sub-process, so that after obtaining the video data submitted by the third client, the first sub-process may push the video data to the streaming address determined by the second server. Correspondingly, the first service end can also issue the streaming address information to the first client, so that the first client can obtain the video data pushed by the first sub-process through the streaming address determined by the second service end.

In the embodiment of the present application, the video data obtaining mode information may be configured in the first client, the first server, the second client, or the third client, in addition to the above description, for pushing the video data meeting the requirements of the user, and the following explanations are separately provided.

Example 3

In this embodiment, the association relationship between the user and the video data acquisition mode information may be configured in the third client, and the video stream pushing process may refer to the flowchart shown in fig. 4.

S301: the first client submits a stream pushing request to the first server, wherein the stream pushing request may include identification information of a target user and identification information of a target camera associated with the first client.

S302: and the first server determines a target entity shop associated with the target camera according to the association relationship between the entity shop and the camera, and issues the plug-flow request to a second client associated with the target entity shop.

S303: and the main process in the second client acquires the stream pushing request issued by the first server, and forwards the identification information of the target user and the identification information of the target camera, which are analyzed from the stream pushing request, to the first sub-process.

S304: and the first sub-process determines a third client associated with the target camera, and calls an access interface of the third client by taking the identification information of the target user and the identification information of the target camera as parameters.

S305: and the third client associated with the target camera determines target video data acquisition mode information associated with the target user and a target assembly corresponding to the target video data acquisition mode information according to the association relationship between the user and the video data acquisition mode information.

S306: video data collected by the target camera according to the target video data acquisition mode is acquired through the target assembly, submitted to the first sub-process, and pushed to the second server side through the first sub-process for the first client side to acquire.

In this embodiment, when the first client generates the push flow request, the identification information of the target user associated with the first client may be acquired and submitted to the first server together with the identification information of the target camera, so that the push flow request issued by the first server to the second client may include the identification information of the target user and the identification information of the target camera. The first sub-process can determine a third client to be called according to the identification information of the target camera, and then issues the identification information of the target user and the identification information of the target camera to the third client in an interface calling mode.

Correspondingly, the third client can be configured with video data acquisition mode information associated with different users besides loading components for acquiring video data according to different video data acquisition modes, so that after information issued by the second client is acquired, target video data acquisition mode information associated with a target user can be determined, a corresponding target component is further determined, video data acquisition meeting user requirements is acquired through the target component, and the video data acquisition is submitted to the first sub-process.

Example 4

In this embodiment, an association relationship between the user and the video data acquisition mode information may be configured in the first service end, and a video stream pushing process may refer to a flowchart shown in fig. 5.

S401: the first client submits a stream pushing request to the first server, wherein the stream pushing request may include identification information of a target user and identification information of a target camera associated with the first client.

S402: the first service end determines target video data acquisition mode information associated with a target user according to the association relationship between the user and the video data acquisition mode information, determines a target entity shop associated with a target camera according to the association relationship between the entity shop and the camera, and issues the target video data acquisition mode information and the identification information of the target camera to a second client end associated with the target entity shop.

S403: and issuing the target video data acquisition mode information and the identification information of the target camera to a second client associated with the target entity shop, and analyzing the information by a main process in the second client and forwarding the information to the first sub-process.

S404: and the first sub-process determines a third client associated with the target camera, obtains video data acquired by the target camera according to a target video data acquisition mode through a component configured in the third client, and pushes the video data to the second server.

S405: the first client obtains video data from the second server.

In this embodiment, after obtaining the stream pushing request submitted by the first client, the first server may determine, through the preconfigured video data acquisition mode information associated with different users, target video data acquisition mode information associated with the target user, and send the target video data acquisition mode information and the identification information of the target camera to the second client, and forward the target video data acquisition mode information to the third client associated with the target camera through the second client, and the third client determines a target component corresponding to the target video data acquisition mode information, and obtains video data acquisition meeting the user requirement through the target component, and pushes the video data.

Example 5

In this embodiment, the association relationship between the user and the video data acquisition mode information may be configured in the second client, and the video stream pushing process may refer to the flowchart shown in fig. 6.

S501: the first client submits a stream pushing request to the first server, wherein the stream pushing request may include identification information of a target user and identification information of a target camera associated with the first client.

S502: and the first server determines a target entity shop associated with the target camera according to the association relationship between the entity shop and the camera, and issues the plug-flow request to a second client associated with the target entity shop.

S503: and the second client determines the target video data acquisition mode information associated with the target user and a third client associated with the target camera.

S504: and calling an access interface of the third client by taking the target video data acquisition mode information and the identification information of the target camera as parameters, acquiring video data acquired by the target camera according to the target video data acquisition mode through a component configured in the third client, and pushing the video data to the second server.

S505: the first client obtains video data from the second server.

In this embodiment, video data acquisition mode information associated with different users may be configured at the second client, for example, the video data acquisition mode information may be specifically configured in the first sub-process, so that after the first sub-process obtains the identification information of the target user and the identification information of the target camera forwarded by the main process, target video data acquisition mode information associated with the target user and a third client associated with the target camera may be determined, and then the target video data acquisition mode information and the identification information of the target camera are issued to the third client in an interface calling manner, and a target component corresponding to the target video data acquisition mode information is determined by the third client, and video data acquisition meeting the user requirements is obtained through the target component, so as to perform video data push.

It is understood that the above video data stream pushing processing scheme can also be applied to other scenes. For example, the method can be applied to a scene that a camera is deployed in an enterprise, a farm, a pet store and the like, and video data is required to be pushed according to the needs of a user.

Specifically, the third server may store a component associated with the video data acquisition mode information related to the organization job, perform component configuration for a third client associated with a camera deployed in the organization according to an actual use requirement, and load a component matching with a user requirement to the third client to provide a push flow service, where a specific implementation process is described in embodiment 1 and is not described in detail here.

The following explains the video plug flow process in other scenarios with reference to the flowchart shown in fig. 7.

Example 6

S601: the first client provides optional video data acquisition mode information and optional camera information, and when a target video data acquisition mode and a target camera are selected, a stream pushing request is generated and submitted to the first server.

S602: and the first service terminal determines a target organization associated with the target camera according to the association relationship between the organization and the camera, and issues the stream pushing request to a second client terminal associated with the target organization.

Taking a target organization as an enterprise as an example, different video acquisition requirements may also be available, and particularly for a production type enterprise, video data related to the working state of an operator, video data related to the operation of a machine device, and the like may be acquired, and specifically, personalized setting may be performed in combination with the use requirements related to enterprise operations.

Taking the target organization as a farm as an example, video data related to the health state of livestock and poultry, video data related to the operation of equipment such as an automatic feeder and the like can be obtained, and the like, and the video data can be specifically and individually set according to the use requirements related to farm operation.

Taking the target organization as a pet store as an example, video data related to the health state of the pet, video data related to the health state in the display cage and the like can be obtained, and personalized setting can be specifically performed according to the use requirements related to the operation of the pet store.

S603: and the main process in the second client acquires the stream pushing request issued by the first server, and forwards the target video data acquisition mode information and the identification information of the target camera, which are analyzed from the stream pushing request, to the first sub-process.

S604: and the first sub-process determines a third client associated with the target camera, obtains video data acquired by the target camera according to a target video data acquisition mode through a component configured in the third client, and pushes the video data to the second server.

S605: the first client obtains video data from the second server.

The implementation processes of S603 to S605 are described in the above S203 to S205, and are not described in detail here.

In this embodiment, the video data acquisition mode information is configured at the first client as an example, and the video stream pushing process in other scenes is explained. It should be noted that the video data obtaining method information may also be configured at the first service end, the second client end, or the third client end to perform the stream pushing process, and the specific implementation process may refer to the descriptions in the above embodiments 3 to 5, which are not illustrated here.

Example 7

Embodiment 7 is a method corresponding to embodiment 2, and from the perspective of the first client, there is provided a method for obtaining video data, which may specifically include, referring to fig. 8:

s701: the first client provides optional video data acquisition mode information and optional camera information;

s702: when a target video data acquisition mode and a target camera are selected, generating a stream pushing request, submitting the stream pushing request to a first service end so that the first service end can send the stream pushing request to a second client end associated with a target entity shop to which the target camera belongs, and the second client end obtains video data acquired by the target camera according to the target video data acquisition mode through a component configured in a third client end associated with the target camera and pushes the video data to the second service end;

s703: and obtaining the video data from the second server.

Example 8

Embodiment 8 is a method for obtaining video data from the perspective of a second client associated with a physical store, corresponding to embodiment 2, and may specifically include, with reference to fig. 9:

s801: a second client associated with the entity store acquires a stream pushing request issued by a first server, wherein the stream pushing request is submitted to the first server by the first client and comprises target video data acquisition mode information and identification information of a target camera;

s802: determining a third client associated with the target camera, and acquiring video data acquired by the target camera according to the target video data acquisition mode through a component configured in the third client;

s803: and pushing the video data to a second server for the first client to obtain.

Example 9

Embodiment 9 is a method corresponding to embodiment 2, and from the perspective of a third client, there is provided a method for obtaining video data, which may specifically include, referring to fig. 10:

s901: loading a component for acquiring video data according to different video data acquisition modes by a third client;

s902: when the access interface provided for a second client associated with the entity store is called, target video data acquisition mode information and identification information of a target camera issued by the second client are acquired, wherein the target video data acquisition mode information and the identification information of the target camera are determined by the first client and issued to the second client through a first server.

S903: and determining a target component corresponding to the target video data acquisition mode information, acquiring video data acquired by the target camera according to the target video data acquisition mode through the target component, and submitting the video data to the second client, so that the second client can push the video data to a second server for the first client to acquire.

Example 10

Embodiment 10 is a method corresponding to embodiment 2, and from the perspective of the first service end, a method for obtaining video data is provided, and referring to fig. 11, the method may specifically include:

s1001: the method comprises the steps that a first server side obtains identification information of cameras associated with all entity shops;

s1002: acquiring a stream pushing request submitted by a first client, wherein the stream pushing request comprises target video data acquisition mode information and identification information of a target camera;

s1003: and determining a target entity shop associated with the target camera, and issuing the plug-flow request to a second client associated with the target entity shop, so that the second client can obtain video data acquired by the target camera according to the target video data acquisition mode through a component configured in a third client associated with the target camera and push the video data to a second server for the first client to acquire.

Example 11

Embodiment 11 is a method corresponding to embodiment 1, and from the perspective of the third server, there is provided a method for loading a component, and referring to fig. 12, the method may specifically include:

s1101: a third server side obtains a component information base, wherein a component related to video data obtaining mode information related to the operation of the entity shop is stored in the component information base, and the component is used for obtaining video data in the entity shop according to the related video data obtaining mode;

s1102: obtaining a configuration request submitted by a third client, wherein the configuration request comprises optional video data acquisition mode information corresponding to a user associated with a first client, and the first client can request the third client to perform stream pushing processing;

s1103: and determining a target component associated with the optional video data acquisition mode information, and loading the target component to the third client, so that the third client can provide a push streaming service for the first client through the target component.

Example 12

Embodiment 12 is a method corresponding to embodiment 3, and from the perspective of a third client, there is provided a method for obtaining video data, which may specifically include, referring to fig. 13:

s1201: the third client acquires video data acquisition mode information associated with different users and loads components for acquiring video data according to different video data acquisition modes;

s1202: when the access interface provided for a second client associated with an entity shop is called, acquiring identification information of a target user associated with a first client and identification information of a target camera issued by the second client, wherein the identification information of the target user and the identification information of the target camera are determined by the first client and issued to the second client through a first server;

s1203: determining target video data acquisition mode information associated with the target user and a target component corresponding to the target video data acquisition mode information;

s1204: and video data acquired by the target camera according to the target video data acquisition mode is acquired through the target assembly and submitted to the second client, so that the second client can push the video data to a second server for the first client to acquire.

Example 13

Embodiment 13 is a method for obtaining video data from the perspective of a second client associated with a physical store, corresponding to embodiment 3, and with reference to fig. 14, the method may specifically include:

s1301: a second client associated with an entity shop obtains a plug flow request issued by a first server, wherein the plug flow request is submitted to the first server by the first client and comprises identification information of a target user associated with the first client and identification information of a target camera;

s1302: determining a third client associated with the target camera, calling an access interface of the third client by taking the identification information of the target user and the identification information of the target camera as parameters, and acquiring video data acquired by the target camera according to a target video data acquisition mode associated with the target user through a component configured in the third client;

s1303: and pushing the video data to a second server for the first client to obtain.

Example 14

Embodiment 14 is a method corresponding to embodiment 3, and from the perspective of the first service end, there is provided a method for obtaining video data, see fig. 15, where the method may specifically include:

s1401: the method comprises the steps that a first server side obtains identification information of cameras associated with all entity shops;

s1402: obtaining a flow pushing request submitted by a first client, wherein the flow pushing request comprises identification information of a target user and identification information of a target camera, which are associated with the first client;

s1403: and determining a target entity shop associated with the target camera, and issuing the plug-flow request to a second client associated with the target entity shop, so that the second client can obtain video data acquired by the target camera according to a target video data acquisition mode associated with the target user through a component configured in a third client associated with the target camera, and push the video data to a second server for the first client to acquire.

Example 15

Embodiment 15 is a method corresponding to embodiment 4, and from the perspective of the first service end, there is provided a method for obtaining video data, see fig. 16, where the method may specifically include:

s1501: the method comprises the steps that a first server side obtains identification information of cameras associated with all entity shops and video data obtaining mode information associated with different users;

s1502: obtaining a flow pushing request submitted by a first client, wherein the flow pushing request comprises identification information of a target user and identification information of a target camera, which are associated with the first client;

s1503: determining target video data acquisition mode information associated with the target user and a target entity shop associated with the target camera;

s1504: and issuing the target video data acquisition mode information and the identification information of the target camera to a second client associated with the target entity shop, so that the second client can acquire video data acquired by the target camera according to the target video data acquisition mode through a component configured in a third client associated with the target camera and push the video data to a second server for the first client to acquire.

Example 16

Embodiment 16 is a method corresponding to embodiment 5, provided from the perspective of a second client associated with a physical store, for obtaining video data, and with reference to fig. 17, the method may specifically include:

s1601: a second client associated with the entity shop obtains video data acquisition mode information associated with different users;

s1602: obtaining a flow pushing request issued by a first server, wherein the flow pushing request is submitted to the first server by a first client, and the flow pushing request comprises identification information of a target user and identification information of a target camera, which are associated with the first client;

s1603: determining target video data acquisition mode information associated with the target user and a third client associated with the target camera;

s1604: and calling an access interface of the third client, acquiring video data acquired by the target camera according to the target video data acquisition mode through a component configured in the third client, and pushing the video data to a second server for the first client to acquire.

Example 17

Embodiment 17 is a method corresponding to embodiment 6, and from the perspective of the first client, there is provided a method for obtaining video data, which may specifically include, referring to fig. 18:

s1701: the first client provides optional video data acquisition mode information and optional camera information;

s1702: when a target video data acquisition mode and a target camera are selected, generating a stream pushing request, submitting the stream pushing request to a first service end so that the first service end can send the stream pushing request to a second client end associated with a target organization to which the target camera belongs, and the second client end obtains video data acquired by the target camera according to the target video data acquisition mode through a component configured in a third client end associated with the target camera and pushes the video data to the second service end;

s1703: and obtaining the video data from the second server.

Example 18

The present embodiment provides a method for obtaining video data from the perspective of a third client, and referring to fig. 19, the method may specifically include:

s1801: the third client acquires video data acquisition mode information associated with different users and loads components for acquiring video data according to different video data acquisition modes;

s1802: when the access interface provided for a second client associated with a target organization is called, acquiring identification information of a target user associated with a first client and identification information of a target camera issued by the second client, wherein the identification information of the target user and the identification information of the target camera are determined by the first client and issued to the second client through a first server;

s1803: determining target video data acquisition mode information associated with the target user and a target component corresponding to the target video data acquisition mode information;

s1804: and video data acquired by the target camera according to the target video data acquisition mode is acquired through the target assembly and submitted to the second client, so that the second client can push the video data to a second server for the first client to acquire.

Example 19

In this embodiment, from the perspective of the first service end, a method for obtaining video data is provided, and referring to fig. 20, the method may specifically include:

s1901: the first server side obtains identification information of cameras related to each organization and video data obtaining mode information related to different users;

s1902: obtaining a flow pushing request submitted by a first client, wherein the flow pushing request comprises identification information of a target user and identification information of a target camera, which are associated with the first client;

s1903: determining target video data acquisition mode information associated with the target user and target organization associated with the target camera;

s1904: and issuing the target video data acquisition mode information and the identification information of the target camera to a second client associated with the target organization, so that the second client can acquire video data acquired by the target camera according to the target video data acquisition mode through a component configured in a third client associated with the target camera and push the video data to a second server for the first client to acquire.

Example 20

The present embodiment provides a method for obtaining video data from the perspective of a second client associated with a target organization, and referring to fig. 21, the method may specifically include:

s2001: a second client associated with a target organization acquires video data acquisition mode information associated with different users;

s2002: obtaining a flow pushing request issued by a first server, wherein the flow pushing request is submitted to the first server by a first client, and the flow pushing request comprises identification information of a target user and identification information of a target camera, which are associated with the first client;

s2003: determining target video data acquisition mode information associated with the target user and a third client associated with the target camera;

s2004: and calling an access interface of the third client, acquiring video data acquired by the target camera according to the target video data acquisition mode through a component configured in the third client, and pushing the video data to a second server for the first client to acquire.

Example 21

The present embodiment provides a method for loading a component from the perspective of the third server, and referring to fig. 22, the method may specifically include:

s2101: a third server side obtains a component information base, wherein components related to video data acquisition mode information related to target organization operation are stored in the component information base, and the components are used for acquiring video data in a target organization according to the related video data acquisition mode;

s2102: obtaining a configuration request submitted by a third client, wherein the configuration request comprises optional video data acquisition mode information corresponding to a user associated with a first client, and the first client can request the third client to perform stream pushing processing;

s2103: and determining a target component associated with the optional video data acquisition mode information, and loading the target component to the third client, so that the third client can provide a push streaming service for the first client through the target component.

For the parts not described in detail in embodiments 7 to 21, reference may be made to the descriptions in the embodiments, which are not repeated herein.

Corresponding to embodiment 2, an embodiment of the present application further provides an apparatus for obtaining video data, referring to fig. 23, where the apparatus is applied to a first client, and includes:

an information providing unit 2201, configured to provide optional video data acquisition mode information and optional camera information;

a plug flow request submitting unit 2202, configured to generate a plug flow request when a target video data acquisition manner and a target camera are selected, and submit the plug flow request to a first service end, so that the first service end issues the plug flow request to a second client associated with a target entity store to which the target camera belongs, and the second client obtains, through a component configured in a third client associated with the target camera, video data acquired by the target camera according to the target video data acquisition manner and pushes the video data to a second service end;

a video data obtaining unit 2203, configured to obtain the video data from the second server.

Corresponding to embodiment 2, the present application further provides an apparatus for obtaining video data, referring to fig. 24, the apparatus is applied to a second client associated with a physical store, and includes:

a push stream request obtaining unit 2301, configured to obtain a push stream request issued by a first server, where the push stream request is submitted to the first server by a first client, and the push stream request includes target video data obtaining mode information and identification information of a target camera;

a video data obtaining unit 2302, configured to determine a third client associated with the target camera, and obtain, through a component configured in the third client, video data acquired by the target camera according to the target video data obtaining manner;

a video data pushing unit 2303, configured to push the video data to a second server for the first client to obtain.

Wherein the apparatus further comprises:

the process providing unit is used for providing a main process used for interacting with the first server and a first sub-process used for carrying out plug-flow processing, wherein the first sub-process is created by the main process and is integrated with access interface information of a third client associated with a camera in the entity shop;

the push flow request obtaining unit is specifically configured to: obtaining the stream pushing request through the main process, and forwarding target video data acquisition mode information and identification information of a target camera, which are analyzed from the stream pushing request, to the first sub-process;

the video data obtaining unit is specifically configured to: and calling an access interface of the third client by using the target video data acquisition mode information and the identification information of the target camera as parameters through the first sub-process to acquire video data submitted by the third client.

Wherein, if the flow pushing request includes time period information,

the push flow request obtaining unit is specifically configured to: forwarding the time period information analyzed from the flow pushing request to the first sub-process through the main process;

the video data obtaining unit is specifically configured to: and calling an access interface of the third client by using the target video data acquisition mode information, the identification information of the target camera and the time period information as parameters through the first sub-process to acquire the video data acquired by the target camera in the time period according to the target video data acquisition mode.

And if the time period information is the instant time, the third client is deployed at the target camera to obtain the video data acquired by the target camera in real time.

And if the time period information is historical time, the third client deploys a Network Video Recorder (NVR) accessed by the target camera to obtain historical video data collected by the target camera and stored in the NVR.

The process providing unit is further configured to provide a second sub-process for performing plug-flow processing, where the second sub-process is created by the host process and is integrated with access interface information of a third client associated with a camera in the physical store;

the device further comprises:

a working state information obtaining unit, configured to obtain, by the host process, working state information of the first sub-process through inter-process communication; and if the working state information indicates that the first sub-process is unavailable, forwarding a new flow pushing request issued by the first server to the second sub-process.

The process providing unit is further configured to create a third sub-process for performing plug-flow processing through the host process, where the third sub-process is integrated with access interface information of a third client associated with a camera in the physical store;

the working state information obtaining unit is further configured to obtain the working state information of the second sub-process through inter-process communication by the main process, so that when the working state information indicates that the second sub-process is unavailable, a new push flow request issued by the first server is forwarded to the third sub-process.

Wherein the apparatus further comprises:

and the early warning information submitting unit is used for generating early warning information according to the times of creating the third sub-process in a specified time period by the main process and submitting the early warning information to the first service terminal.

Wherein the apparatus further comprises:

and the early warning information submitting unit is used for submitting the relevant information of the flow pushing request to the first service end through the main process so that the first service end can send the flow pushing request to the second client side again for flow pushing processing.

The process providing unit is further configured to provide a fourth sub-process for performing task analysis, where the fourth sub-process is created by the main process;

the push flow request obtaining unit is specifically configured to: and forwarding the stream pushing request to the fourth sub-process through the main process, and obtaining target video data acquisition mode information analyzed by the fourth sub-process and identification information of a target camera and forwarding the target video data acquisition mode information and the identification information to the first sub-process.

Corresponding to embodiment 2, the present application further provides an apparatus for obtaining video data, referring to fig. 25, where the apparatus is applied to a third client, and includes:

a component loading unit 2401, configured to load components used to obtain video data according to different video data obtaining manners;

an interface calling unit 2402, configured to obtain, when receiving a call through an access interface provided for a second client associated with an entity store, target video data acquisition mode information and identification information of a target camera issued by the second client, where the target video data acquisition mode information and the identification information of the target camera are determined by a first client and issued to the second client via a first server;

a video data submitting unit 2403, configured to determine a target component corresponding to the target video data obtaining mode information, obtain, through the target component, video data that is collected by the target camera according to the target video data obtaining mode, and submit the video data to the second client, so that the second client pushes the video data to a second server for the first client to obtain.

Wherein the apparatus further comprises:

and the component updating unit is used for updating the loaded component when the user requirement associated with the first client side is changed.

Wherein the user requirement changes into newly added optional video data acquisition mode information,

the component update unit is specifically configured to: and loading the component corresponding to the newly added optional video data acquisition mode information.

Wherein the user requirement changes into deleting the optional video data acquisition mode information,

the component update unit is specifically configured to: and unloading the components corresponding to the deleted optional video data acquisition mode information.

The interface calling unit is specifically configured to: and when the time period information issued by the second client is obtained through the access interface, video data collected by the target camera in the time period according to the target video data acquisition mode is obtained through the target component.

Corresponding to embodiment 2, an embodiment of the present application further provides an apparatus for obtaining video data, referring to fig. 26, where the apparatus is applied to a first service end, and includes:

an association relationship obtaining unit 2501, configured to obtain identification information of cameras associated with each entity store;

a push stream request obtaining unit 2502, configured to obtain a push stream request submitted by a first client, where the push stream request includes target video data obtaining mode information and identification information of a target camera;

a push stream request issuing unit 2503, configured to determine a target entity store associated with the target camera, and issue the push stream request to a second client associated with the target entity store, so that the second client obtains, through a component configured in a third client associated with the target camera, video data acquired by the target camera according to the target video data acquisition manner, and pushes the video data to a second server for the first client to acquire.

Wherein the apparatus further comprises:

an address information obtaining unit, configured to submit an address allocation request to the second server after obtaining the stream pushing request, and obtain stream pushing address information and stream playing address information sent by the second server;

a push stream address information issuing unit, configured to issue the push stream address information to the second client, so that the second client pushes the video data to the push stream address determined by the second server;

and the broadcast stream address information issuing unit is used for issuing the broadcast stream address information to the first client so that the first client can obtain the video data through the broadcast stream address determined by the second server.

Wherein the apparatus further comprises:

and the early warning information issuing unit is used for issuing the early warning information submitted by the second client to a fourth client.

Corresponding to embodiment 1, an embodiment of the present application further provides an apparatus for loading a component, referring to fig. 27, where the apparatus is applied to a third server, and includes:

an information base obtaining unit 2601, configured to obtain a component information base, in which components associated with video data obtaining manner information related to an actual store job are stored, and the components are configured to obtain video data in the actual store according to the associated video data obtaining manner;

a configuration request obtaining unit 2602, configured to obtain a configuration request submitted by a third client, where the configuration request includes information about an optional video data obtaining manner corresponding to a user associated with a first client, and the first client may request the third client to perform stream pushing processing;

a component loading unit 2603, configured to determine a target component associated with the optional video data acquisition mode information, and load the target component to the third client, so that the third client provides a push streaming service to the first client through the target component.

Corresponding to embodiment 3, an embodiment of the present application further provides an apparatus for obtaining video data, referring to fig. 28, where the apparatus is applied to a third client, and includes:

an association obtaining unit 2701, configured to obtain video data obtaining mode information associated with different users;

a component loading unit 2702, configured to load components used for obtaining video data according to different video data obtaining manners;

the system comprises an interface calling unit 2703, configured to obtain, when receiving a call through an access interface provided for a second client associated with an entity store, identification information of a target user and identification information of a target camera associated with a first client issued by the second client, where the identification information of the target user and the identification information of the target camera are determined by the first client and issued to the second client via a first server;

a target component determining unit 2704, configured to determine target video data acquisition manner information associated with the target user and a target component corresponding to the target video data acquisition manner information;

the video data submitting unit 2705 is configured to obtain, through the target component, video data acquired by the target camera according to the target video data acquisition manner, and submit the video data to the second client, so that the second client pushes the video data to a second server for the first client to acquire.

Corresponding to embodiment 3, the present application further provides an apparatus for obtaining video data, referring to fig. 29, where the apparatus is applied to a second client associated with a physical store, and includes:

a push flow request obtaining unit 2801, configured to obtain a push flow request issued by a first service end, where the push flow request is submitted to the first service end by a first client, and the push flow request includes identification information of a target user and identification information of a target camera, where the identification information is associated with the first client;

a video data obtaining unit 2802, configured to determine a third client associated with the target camera, call an access interface of the third client using the identification information of the target user and the identification information of the target camera as parameters, and obtain, through a component configured in the third client, video data acquired by the target camera in a target video data acquisition manner associated with the target user;

a video data pushing unit 2803, configured to push the video data to a second server for the first client to obtain.

Corresponding to embodiment 3, an embodiment of the present application further provides an apparatus for obtaining video data, referring to fig. 30, where the apparatus is applied to a first service end, and includes:

an association relation obtaining unit 2901 configured to obtain identification information of cameras associated with each entity store;

a push flow request obtaining unit 2902, configured to obtain a push flow request submitted by a first client, where the push flow request includes identification information of a target user and identification information of a target camera associated with the first client;

a push stream request issuing unit 2903, configured to determine a target entity store associated with the target camera, and issue the push stream request to a second client associated with the target entity store, so that the second client obtains, through a component configured in a third client associated with the target camera, video data acquired by the target camera according to a target video data acquisition manner associated with the target user, and pushes the video data to a second server for the first client to acquire.

Corresponding to embodiment 4, an embodiment of the present application further provides an apparatus for obtaining video data, referring to fig. 31, where the apparatus is applied to a first service end, and includes:

an association obtaining unit 3001, configured to obtain identification information of cameras associated with each entity store and video data obtaining manner information associated with different users;

a push flow request obtaining unit 3002, configured to obtain a push flow request submitted by a first client, where the push flow request includes identification information of a target user and identification information of a target camera associated with the first client;

an information determination unit 3003, configured to determine target video data acquisition mode information associated with the target user and a target entity store associated with the target camera;

an information issuing unit 3004, configured to issue the target video data acquisition mode information and the identification information of the target camera to a second client associated with the target entity store, so that the second client obtains, through a component configured in a third client associated with the target camera, video data acquired by the target camera according to the target video data acquisition mode and pushes the video data to a second server, where the video data is acquired by the first client.

Corresponding to embodiment 5, the present application further provides an apparatus for obtaining video data, referring to fig. 32, the apparatus is applied to a second client associated with a physical store, and includes:

an association obtaining unit 3101, configured to obtain video data obtaining mode information associated with different users;

a push flow request obtaining unit 3102, configured to obtain a push flow request issued by a first service end, where the push flow request is submitted to the first service end by a first client, and the push flow request includes identification information of a target user and identification information of a target camera associated with the first client;

an information determining unit 3103, configured to determine target video data acquisition mode information associated with the target user and a third client associated with the target camera;

a video data pushing unit 3104, configured to invoke an access interface of the third client, obtain, through a component configured in the third client, video data acquired by the target camera according to the target video data obtaining manner, and push the video data to a second server for the first client to obtain.

Corresponding to embodiment 6, an embodiment of the present application further provides an apparatus for obtaining video data, where the apparatus is applied to a first client, and the apparatus includes:

An embodiment of the present application further provides an apparatus for obtaining video data, where the apparatus is applied to a third client, and the apparatus includes:

An embodiment of the present application further provides an apparatus for obtaining video data, where the apparatus is applied to a first service end, and the apparatus includes:

An embodiment of the present application further provides an apparatus for obtaining video data, where the apparatus is applied to a second client associated with a target organization, and the apparatus includes:

The schematic diagrams of the above apparatus for obtaining video data can be seen in fig. 23, fig. 28, fig. 31, and fig. 32.

An embodiment of the present application further provides a device for loading a component, where the device is applied to a third server, and the device includes:

A schematic view of the above apparatus for loading a component can be seen in fig. 27.

In addition, an embodiment of the present application further provides an electronic device, including:

one or more processors; and

and obtaining the video data from the second server.

And an electronic device comprising:

one or more processors; and

and pushing the video data to a second server for the first client to obtain.

And an electronic device comprising:

one or more processors; and

And an electronic device comprising:

one or more processors; and

And an electronic device comprising:

one or more processors; and

And an electronic device comprising:

one or more processors; and

And an electronic device comprising:

one or more processors; and

and pushing the video data to a second server for the first client to obtain.

And an electronic device comprising:

one or more processors; and

And an electronic device comprising:

one or more processors; and

And an electronic device comprising:

one or more processors; and

And an electronic device comprising:

one or more processors; and

and obtaining the video data from the second server.

And an electronic device comprising:

one or more processors; and

And an electronic device comprising:

one or more processors; and

And an electronic device comprising:

one or more processors; and

And an electronic device comprising:

one or more processors; and

Fig. 33 illustrates an architecture of a computer system, which may specifically include a processor 3210, a video display adapter 3211, a disk drive 3212, an input/output interface 3213, a network interface 3214, and a memory 3220. The processor 3210, the video display adapter 3211, the disk drive 3212, the input/output interface 3213, the network interface 3214, and the memory 3220 may be communicatively connected to each other via a communication bus 3230.

The processor 3210 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits, and is configured to execute related programs to implement the technical solution provided by the present Application.

The Memory 3220 may be implemented in a ROM (Read Only Memory), a RAM (Random Access Memory), a static storage device, a dynamic storage device, or the like. Memory 3220 may store an operating system 3221 for controlling the operation of computer system 3200, a Basic Input Output System (BIOS) for controlling low-level operations of computer system 3200. In addition, a web browser 3223, a data storage management system 3224, a system for obtaining video data 3225, and the like may also be stored. The system 3225 for obtaining video data may be a first server that implements the operations of the foregoing steps in this embodiment of the application. In summary, when the technical solution provided in the present application is implemented by software or firmware, the relevant program codes are stored in the memory 3220 and called to be executed by the processor 3210.

The input/output interface 3213 is used to connect an input/output module to realize information input and output. The i/o module may be configured as a component in a device (not shown) or may be external to the device to provide a corresponding function. The input devices may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output devices may include a display, a speaker, a vibrator, an indicator light, etc.

The network interface 3214 is used to connect a communication module (not shown in the drawings) to enable the device to interact with other devices. The communication module can realize communication in a wired mode (such as USB, network cable and the like) and also can realize communication in a wireless mode (such as mobile network, WIFI, Bluetooth and the like).

The bus 3230 includes a path that transfers information between various components of the device, such as the processor 3210, the video display adapter 3211, the disk drive 3212, the input/output interface 3213, the network interface 3214, and the memory 3220.

It should be noted that, although the above-mentioned devices only show the processor 3210, the video display adapter 3211, the disk drive 3212, the input/output interface 3213, the network interface 3214, the memory 3220, the bus 3230 and so on, in a specific implementation process, the devices may also include other components necessary for normal operation. Furthermore, it will be understood by those skilled in the art that the apparatus described above may also include only the components necessary to implement the solution of the present application, and not necessarily all of the components shown in the figures.

Where fig. 34 illustratively shows the architecture of an electronic device, for example, device 3300 may be a mobile phone, computer, digital broadcast terminal, messaging device, game console, tablet device, medical device, fitness device, personal digital assistant, aircraft, or the like.

Referring to fig. 34, device 3300 may include one or more of the following components: processing component 3302, memory 3304, power component 3306, multimedia component 3308, audio component 3310, input/output (I/O) interface 3312, sensor component 3314, and communications component 3316.

The processing component 3302 generally controls the overall operation of the device 3300, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. Processing element 3302 may include one or more processors 3320 to execute instructions to perform all or a portion of the steps of the methods provided by the disclosed solution. Further, the processing component 3302 can include one or more modules that facilitate interaction between the processing component 3302 and other components. For example, the processing component 3302 can include a multimedia module to facilitate interaction between the multimedia component 3308 and the processing component 3302.

The memory 3304 is configured to store various types of data to support operations at the device 3300. Examples of such data include instructions for any application or method operating on device 3300, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 3304 may be implemented by any type or combination of volatile or non-volatile memory devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.

The power supply component 3306 provides power to the various components of the device 3300. The power components 3306 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 3300.

The multimedia component 3308 includes a screen that provides an output interface between the device 3300 and the user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 3308 includes a front facing camera and/or a rear facing camera. The front-facing camera and/or the back-facing camera may receive external multimedia data when the device 3300 is in an operating mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

The audio component 3310 is configured to output and/or input audio signals. For example, the audio component 3310 may include a Microphone (MIC) configured to receive external audio signals when the apparatus 3300 is in an operational mode, such as a call mode, recording mode, and voice recognition mode. The received audio signals may further be stored in memory 3304 or transmitted via the communications component 3316. In some embodiments, audio component 3310 also includes a speaker for outputting audio signals.

The I/O interface 3312 provides an interface between the processing component 3302 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.

The sensor component 3314 includes one or more sensors for providing various aspects of status assessment for the device 3300. For example, the sensor component 3314 may detect the open/closed state of the device 3300, the relative positioning of the components, such as the display and keypad of the device 3300, the sensor component 3314 may also detect a change in the position of the device 3300 or a component of the device 3300, the presence or absence of user contact with the device 3300, the orientation or acceleration/deceleration of the device 3300, and a change in the temperature of the device 3300. The sensor assembly 3314 may include a proximity sensor configured to detect the presence of a nearby object in the absence of any physical contact. The sensor component 3314 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 3314 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

Communications component 3316 is configured to facilitate communications between device 3300 and other devices in a wired or wireless manner. The device 3300 may access a wireless network based on a communication standard, such as WiFi, 2G, or 3G, or a combination thereof. In an exemplary embodiment, the communication component 3316 receives a broadcast signal or broadcast associated information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communications component 3316 also includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

In an exemplary embodiment, the device 3300 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components for performing the above-described methods.

In an exemplary embodiment, a non-transitory computer-readable storage medium comprising instructions, such as the memory 3304 comprising instructions, executable by the processor 3320 of the device 3300 to perform the methods provided by the present disclosure is also provided. For example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

From the above description of the embodiments, it is clear to those skilled in the art that the present application can be implemented by software plus necessary general hardware platform. Based on such understanding, the technical solutions of the present application may be essentially implemented or a part contributing to the prior art may be embodied in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method described in the embodiments or some parts of the embodiments of the present application.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, the system or system embodiments are substantially similar to the method embodiments and therefore are described in a relatively simple manner, and reference may be made to some of the descriptions of the method embodiments for related points. The above-described system and system embodiments are only illustrative, wherein the units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.

The system, the method, the apparatus, and the electronic device for obtaining video data provided by the present application, and the method, the apparatus, and the electronic device for loading components are introduced in detail above, and specific examples are applied herein to illustrate the principles and embodiments of the present application, and the description of the above embodiments is only used to help understand the method and the core ideas of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, the specific embodiments and the application range may be changed. In view of the above, the description should not be taken as limiting the application.

Claims

1. A system for obtaining video data, comprising:

2. A method for obtaining video data, comprising:

and obtaining the video data from the second server.

3. A method for obtaining video data, comprising:

and pushing the video data to a second server for the first client to obtain.

4. The method of claim 3,

the second client provides a main process used for interacting with the first server and a first sub-process used for carrying out plug-flow processing, wherein the first sub-process is created by the main process and is integrated with access interface information of a third client related to a camera under the entity shop;

the obtaining of the stream pushing request issued by the first server includes: obtaining the stream pushing request through the main process, and forwarding target video data acquisition mode information and identification information of a target camera, which are analyzed from the stream pushing request, to the first sub-process;

the obtaining, by the component configured in the third client, the video data acquired by the target camera according to the target video data obtaining manner includes: and the first sub-process calls an access interface of the third client by taking the target video data acquisition mode information and the identification information of the target camera as parameters to acquire video data submitted by the third client.

5. The method of claim 4, wherein if time period information is included in the push flow request, the method further comprises:

the main process forwards the time period information analyzed from the flow pushing request to the first sub-process;

the obtaining, by the component configured in the third client, the video data acquired by the target camera according to the target video data obtaining manner includes: and the first sub-process calls an access interface of the third client by taking the target video data acquisition mode information, the identification information of the target camera and the time period information as parameters to acquire the video data acquired by the target camera in the time period according to the target video data acquisition mode.

6. The method of claim 5,

7. The method of claim 5,

8. The method of claim 4, further comprising:

the second client provides a second sub-process for performing plug-flow processing, the second sub-process is created by the main process and is integrated with access interface information of a third client associated with the camera in the entity shop;

the main process obtains the working state information of the first sub-process through inter-process communication;

and if the working state information indicates that the first sub-process is unavailable, forwarding a new flow pushing request issued by the first server to the second sub-process.

9. The method of claim 8, further comprising:

the main process creates a third sub-process for pushing flow processing, and the third sub-process integrates access interface information of a third client associated with a camera under the entity shop;

and the main process obtains the working state information of the second sub-process through inter-process communication, so that when the working state information indicates that the second sub-process is unavailable, a new flow pushing request issued by the first server is forwarded to the third sub-process.

10. The method of claim 9, further comprising:

and the main process generates early warning information according to the times of creating the third sub-process in a specified time period and submits the early warning information to the first service terminal.

11. The method of claim 9, further comprising:

and the main process submits the relevant information of the flow pushing request to the first service end so that the first service end sends the flow pushing request to the second client side again for flow pushing processing.

12. The method of claim 4, further comprising:

the second client provides a fourth sub-process for task analysis, and the fourth sub-process is created by the main process;

the forwarding the target video data acquisition mode information and the identification information of the target camera, which are analyzed from the stream pushing request, to the first sub-process includes: and the main process forwards the stream pushing request to the fourth sub-process, obtains target video data acquisition mode information analyzed by the fourth sub-process and identification information of a target camera and forwards the target video data acquisition mode information and the identification information to the first sub-process.

13. A method for obtaining video data, comprising:

14. The method of claim 13, further comprising:

and when the user requirement associated with the first client side changes, updating the loaded component.

15. The method of claim 14,

the user demand changes to new optional video data acquisition mode information,

the updating process of the loaded component comprises the following steps: and loading the component corresponding to the newly added optional video data acquisition mode information.

16. The method of claim 14,

the user demand changes to delete the optional video data acquisition mode information,

the updating process of the loaded component comprises the following steps: and unloading the components corresponding to the deleted optional video data acquisition mode information.

17. The method of claim 13, further comprising:

and if the time period information issued by the second client is obtained through the access interface, video data collected by the target camera in the time period according to the target video data acquisition mode is obtained through the target component.

18. A method for obtaining video data, comprising:

19. The method of claim 18, further comprising:

after the stream pushing request is obtained, submitting an address allocation request to the second server, and obtaining stream pushing address information and stream broadcasting address information issued by the second server;

the stream pushing address information is sent to the second client side, so that the second client side can push the video data to the stream pushing address determined by the second server side;

and sending the streaming address information to the first client so that the first client can obtain the video data through the streaming address determined by the second server.

20. The method of claim 18, further comprising:

and issuing the early warning information submitted by the second client to a fourth client.

21. A method for loading a component, comprising:

22. A method for obtaining video data, comprising:

23. A method for obtaining video data, comprising:

and pushing the video data to a second server for the first client to obtain.

24. A method for obtaining video data, comprising:

25. A method for obtaining video data, comprising:

26. A method for obtaining video data, comprising:

27. A method for obtaining video data, comprising:

and obtaining the video data from the second server.

28. A method for obtaining video data, comprising:

29. A method for obtaining video data, comprising:

30. A method for obtaining video data, comprising:

31. A method for loading a component, comprising:

32. An apparatus for obtaining video data, applied to a first client, comprising:

33. An apparatus for obtaining video data, applied to a second client associated with a physical store, comprising:

34. An apparatus for obtaining video data, applied to a third client, comprising:

35. An apparatus for obtaining video data, applied to a first service side, comprising:

36. An apparatus for loading a component, applied to a third server, includes:

37. An apparatus for obtaining video data, applied to a third client, comprising:

38. An apparatus for obtaining video data, applied to a second client associated with a physical store, comprising:

39. An apparatus for obtaining video data, applied to a first service side, comprising:

40. An apparatus for obtaining video data, applied to a first service side, comprising:

41. An apparatus for obtaining video data, applied to a second client associated with a physical store, comprising:

42. An apparatus for obtaining video data, applied to a first client, comprising:

43. An apparatus for obtaining video data, applied to a third client, comprising:

44. An apparatus for obtaining video data, applied to a first service side, comprising:

45. An apparatus for obtaining video data, applied to a second client associated with a target organization, comprising:

46. An apparatus for loading a component, applied to a third server, includes:

47. An electronic device, comprising:

one or more processors; and

and obtaining the video data from the second server.

48. An electronic device, comprising:

one or more processors; and

and pushing the video data to a second server for the first client to obtain.

49. An electronic device, comprising:

one or more processors; and

50. An electronic device, comprising:

one or more processors; and

51. An electronic device, comprising:

one or more processors; and

52. An electronic device, comprising:

one or more processors; and

53. An electronic device, comprising:

one or more processors; and

and pushing the video data to a second server for the first client to obtain.

54. An electronic device, comprising:

one or more processors; and

55. An electronic device, comprising:

one or more processors; and

56. An electronic device, comprising:

one or more processors; and

57. An electronic device, comprising:

one or more processors; and

and obtaining the video data from the second server.

58. An electronic device, comprising:

one or more processors; and

59. An electronic device, comprising:

one or more processors; and

60. An electronic device, comprising:

one or more processors; and

61. An electronic device, comprising:

one or more processors; and