Body worn solutions from Axis capture valuable evidence. And they’re an effective way to deter bad behavior and positively influence the actions of camera wearers and the public alike. They record incidents as they appeared to the camera wearer, and as they sounded to all involved. They deliver recordings with high quality audio and video that you can use in internal investigations and in court.
Get to know Axis body worn solution.
Use cases and important considerations when integrating Axis body worn solution.
Step-by-step guide and implementation recommendations.
Before you go and make those successful sales, we have some tips and considerations for you.
Availability in more countries/regions is planned for next year. Stay tuned for updated information on this page or contact your local Axis office if you have any urgent requests.
Footage from Axis body worn cameras is a useful tool for teaching personnel how to respond to situations they’re likely to encounter. For example, you can analyze footage of an incident. Or use portions of an encounter as the basis for testing how students would respond to a similar set of circumstances before revealing the real outcome.
Axis body worn solution - including the robust camera, docking stations and system controller - has been designed as an open system architecture, which allows for integration with video management systems (VMS) and evidence management systems (EMS), making the solution incredibly flexible.
You can plug Axis body worn solutions right into an Axis video management system or use your own preferred system. You can store video in the cloud or onsite. Either way you’ll do a better-than-ever job of deterring and protecting, and of gathering documentation and forensic evidence. And of course, Axis body worn solutions give you superior image quality and video that holds up in court.
The Axis body worn solution brings several concrete advantages, e.g.:
Store as much footage as you need without compromising image quality
View and label material from any cell phone (mobile app will be released during Q3 2020)
Find and retrieve evidence quickly and easily
Easy integration with VMS & EMS systems
Cost effective and scalable solution
Designed from the ground up with cybersecurity in mind
To help you build a strong integration with Axis body worn solution, we have developed trainings, API’s, code examples and important information about things you should consider when designing your integration. Follow the step-by-step guidelines below to learn more about suggested architecture, development examples and recommended considerations.
The fastest way to get to know and get a good understanding of the Axis body worn solution is to read the introduction presentation and run the online training. You will learn about the components involved, the capabilities offered and various security aspects.
Introduction presentation – for integration of Axis body worn (pdf)
Remember that Axis body worn solution is a closed system in terms of streaming and accessibility. The only part you will integrate with is the system controller, AXIS W800, that pushes the recording files to you in MP4 or MKV format.
Camera user (police officer or security guard)
Carries and uses the body worn camera on patrol.
Processes recordings and metadata that the camera user produces. For smaller departments, one person can have both the camera user and investigator roles.
In order to integrate Axis body worn solution, you will need physical access to a system which consists of a system controller, a body worn camera and a docking station.
Once you are familiar with Axis body worn data flow, such as adding a user, assigning a camera and transfer of recordings, it is a good idea to try out the body worn integration example. We have used the same APIs covered in this section for integration of the body worn solution in AXIS Camera Station.
Follow the install instructions to configure Axis body worn Swift service example. For example:
The screenshots are representative and may not match the latest version of the sample code. We will add new features in this sample code, please check the readme file inside AxisBodyWornSwiftServiceExample.zip for more detailed information.
When run as a service, you should configure it to start automatically every time the computer boots.
The logs from the service are logged in Windows event viewer. You can type “event” in the windows search bar and run it. In the event viewer, choose Windows logs and then Applications. The logs will be listed under the application name AxisBodyWornSwiftServiceExample.
AxisBodyWornSwiftServiceExample version 1.6 contains a separate executable file that can demonstrate GPS trails. It is called "GNSSViewerExample" and it uses Leaflet and OpenStreetMap. This can be changed to google maps or any other geographical information system(GIS) tool easily. It can be done under cmd/index.html.
In order to use GNSSViewerExample, you must run the AxisBodyWornSwiftServiceExample first. Then you need to transfer recordings with the GPS trail information to your server. It will contain a file called "*_gpstrail.json". If you run the command "GNSSViewerExample_windows_amd64.exe Sample_gpstrail.json" it will open a port and ask you to select your browser to show it.
Sample cmd call:
View in the browser:
If you have a NAS device with Swift server or an application that works as a Swift Server, you can try setting it up as a content destination for the body worn system as well. Learn more about the Swift API if you need a deeper understanding of the API.
In order to test, upload the config file in the Body Worn Manager. You can do this either during the setup wizard or afterwards in the content destination tab.
If you get any errors, please make sure that the Windows firewall is not blocking. You can disable it temporary or configure the correct ports that enable the communication.
The containers storing the files will be created in the directory specified during installation. The uploader needs a json connection file which will have been auto generated. It is located in the storage location specified during installation, named as config.json.
The Body Worn Manager handles all camera configuration. The data is pushed form the body worn system to the content destination. This is different from how you normally integrate with other Axis cameras. The VMS or EMS is acting like a server and listening for data that is pushed from the system controller. At the end of the transfer you will get a video and metadata, while all the configuration takes place outside the content destination in the Body Worn Manager.
After configuration, by running the “AxisBodyWornSwiftServiceExample.exe” or of the general Swift server, please try filming a few clips and offloading them to your server. You can use Wireshark to sniff the network and get API calls during the transfer.
To understand the file structures that the swift server creates, consult the body worn API documentation.
For every recording, a new container will be created. It is named as <userid>_<deviceid>_date_time where Username is the nice name and userid is the UUID of the user who was assigned to the camera when it was recording and deviceid is the id of the camera that did the recording.
Note that if the user who did the recording for some reason doesn't exist in the Users folder, the naming of the container will instead be <userid>_<deviceid>_date_time.
In every recording container there will be one or multiple clips with the naming <date>_<time>_<id>.<mkv|mp4>. And its corresponding metadata, <containername>.<moviename>.metadata.json. There will also be a metadata file for the container which is called <containername>.metadata.json
To make integration easier, the 'status: Complete' metadata attribute value of a container is also available as a zero size file named 'complete', inside the container directory, when it is set. Thereby an integrating application can notify/watch for that file to appear instead of polling and parsing the json metadata file.
Axis body worn solution is constantly evolving with new features and functions. Our recent development is the Capability API. It allows you to integrate our extended and updated features in your own timeline. It is backwards compatible, which makes sure that if the capabilities API is not supported in your integration, it will work as it is used to, without any effect.
For instance, StoreBookmarks capability allow the user to tag each clip with a category and notes out in the field using the body worn assistant application, available in Android's Google Play and on the iOS App Store. If you have not implemented StoreBookmarks yet to parse the new notes and categories from the end user, it will simply turn off that functionality in our app. You can find more information on the Body worn API.
Another example: Retention time could be based on a category for each recording. Depending on the category of the file, it can be kept longer. However, once your support for a capability is published, it should not be revoked afterwards.
With AXIS OS 11.0, Axis body worn systems got the capability of signed video (except AXIS W100). Signed video is available on other axis devices too, separate integration guidelines for signed video is available to you. In order to use the signed video in Axis body worn systems, you need to enable it via the capability API. After transferring the recording from the system controller you should keep the SEI frames in the content destination to verify the signing information.
You are now prepared to start your implementation. It is up to you to decide which programming language to use, but feel free to look at parts of the sample code and convert them to your choice of programming language.
If you have come this far, we would like to congratulate you on finishing your integration. Before you go and make those successful sales, we have some tips and considerations for you.
It is important to be aware of how quickly your server can handle uploads from system controllers. We recommend that you do some testing on relevant hardware to see which upload speeds you get. The maximum transfer speed of an AXIS W800 (System Controller) is 1Gbit/s.
For instance, let's say that your normal hardware setup measures 500Mbit/s for body worn offload. That would be fine for your customer that has 300 cameras that are used each day in three shifts. But If you have 100 cameras per shift, roughly 2 hours of recordings per camera in 1080 high bitrate is 100 x 2 x 5. (We are using 5 GByte per hour high bitrate in 1080p. It is just a good assumption ). That means you will get 1TByte of data per shift, and with 500Mbit/s that is a five hour offload time. You have to do it in less than 16 hours or eight hours before your next shift starts with the same hardware. If you have only 100Mbit/s and still 1TByte data per shift, then it will not be fine.
This consideration is important to test for and to take into account.
Except for the certificate, the same content destination requires the same connection file in order to continue to work as it should. Consider educating your end users that they cannot simply move a system controller to another instance of content destination without a proper system reset. This is a key feature of the system, and if you have implemented the StoreReadSystemID capability the body worn system will automatically block users from trying to change the connection file to a different system than what it was initially was set up with.
You need to reset the body worn manager in order to change the content destination.
Always test with the newest AXIS OS version (firmware). We are careful to keep the backwards combability, but like all other Axis products, we would like you to support our latest version.
Per the above explanation about upload speed, it is good if you can give your customers some system performance recommendations.
We have prepared a list for you to verify your integration capabilities that consist of "Mandatory" and "Good to have" features:
|Use case description||Explanation||Importance|
|Is HTTPS communication supported when communicating with Axis body worn system?||Mandatory|
|Could HTTPS certificate be renewed when it needs to be updated, e.g. when the IP address of the server (where your application is running) is changed?||Mandatory|
|Download connection file|
|Could the same connection file be used for multiple body worn systems connected to the same server (where your application is running)?||The connection file should not be uniquely created for a system controller by connecting to its serial number, for example. This makes system maintenance easier for large installations.||Good to have|
|Import data from body worn system|
|Is the default minimum retention period long enough, e.g. 90 days, to handle situations when people forget to dock camera for a long time?||This is to avoid the situation when recordings are removed right after they are uploaded.||Mandatory|
|Could the retention time of a recording be adjusted automatically based on its category?||Requires support for "Category" capability||Good to have|
|Would the users of your application be notified if there are problems with offloading recordings from the body worn system?||Good to have|
|Would the users of your application be notified about newly arrived recordings of a certain category?||Requires support for "Category" capability||Good to have|
|Would the users of your application be able to import and decrypt a file?||In the bodyworn system it is possible to offload a stuck recording from the W800 to a USB stick. If your application supports encryption you should also be able to import this file and decrypt it.||Good to have|
|Are you using the signed video?||Axis Bodyworn System is designed for evidence management. Signed video provides end-to-end authentication from camera to client.||Good to have|
|Present body worn system data|
|Are recordings organized by camera user and not by physical cameras in your application?||So it's easy to find a camera user's recording if a physical camera is assigned to different camera users now and then, e.g. when BWS is set to self-assign mode.||Mandatory|
|Is the camera user name combined with the unique user ID (if configured in Body Worn Manager) as identifiers for cameras in your application?||For example, name the cameras by "Nice name (User ID)”. In case there are two camera users of the same name. Requires support for "StoreUserIDKey" capability.||Mandatory|
|Is the metadata of each recording presented in a user friendly manner?||In the form of bookmarks, for example.||Mandatory|
|Is it possible to search for recordings by metadata?||By searching for a category, location, trigger method, etc.||Good to have|
|Is a recording longer than minutes displayed as a single recording instead of multiple clips?||Mandatory|
|Could the location data be used in a sensible way?||For example, by displaying recordings on a map, or possibility to search for recordings nearby a specified location, or at least allowing the location data to be copied and pasted so that the operator can find out where the recording was taken (by using a third party application, like Google Maps).||Good to have|
|Is the operator directed to the playback view in a friendly way when the live view for body worn camera is opened?||By displaying a body worn camera image or a friendly message that explains live view is not available for body worn cameras, for example.||Good to have|
|When playing back a recording, is the recording's trigger time (i.e. when the recording button is pressed) used as the default start point, instead of the beginning of the recording?||This is preferred because pre-buffer (by default on) recording is often not as interesting at first sight. It can be achieved by auto-generating bookmarks or thumbnails at the trigger time, for example.||Good to have|
|Are you showing the GPS trails of the devices during the recording time on a map?||Since Axis OS 11.1, Axis bodyworn solution can provide GPS trails as a part of the metadata that you can project on various maps.||Good to have|
|Is there any measure taken to stop users of your application from removing a body worn camera in your application before it's removed from Body Worn Manager?||This is to prevent complications caused by a mismatch between cameras in your applications and Body Worn Manager, e.g. license issues, leftover recording upload issues.||Mandatory|
|Does your application back up the body worn system related configurations regularly, together with the other important system configurations, e.g. username/userID/deviceID/systemID etc?||This helps the body worn system to restore the connection to your application in case of reinstallation of your application and prevents that you will have stuck content on your AXIS W800.||Good to have|
|Is it possible to show Body Worn Manager in a built-in browser in your application?||This way the system admin doesn't have to switch between Body Worn Manager and your application.||Good to have|
|Does your application notify its users if licenses for body worn system run out?||If licenses are based on camera users, licenses may run out when a new camera user is created in Body Worn Manager.||Good to have|
|Are body worn system related events logged in your application?||i.e. recordings from a body worn camera has arrived?||Mandatory|
|Has performance test been done on a system as large as you plan to support?||Recordings from body worn system need to be offloaded to your application in time. Otherwise, the system controllers and cameras can be filled up. As a result, the system won't be usable.||Mandatory|
|Is there user documentation in place that explains how to integrate Axis Body Worn System with your application?||Please provide a PDF copy of your documentation to Axis.||Mandatory|
|Is there a webpage on your website that shows you have an integration with Axis Body Worn System?||Please provide a link to the page to Axis.||Good to have|
|Is it clearly documented from which body worn system firmware version your application has support for?||Mandatory|
|Are the users of your application informed about this: Once the body worn system is set up to connect to one application, it is locked to that instance. A proper system reset is required if the system needs to be connected to another application instance.||Out of security reasons, the body worn system works only with the application instance with its SystemID.||Mandatory|
|Are the users of your application informed about this: Body worn system administration should be done in Body Worn Manager and not in your application.||Mandatory|