Skip to content

Commit 655ab12

Browse files
committed
Reorder the paragraph structures
1 parent 5473b69 commit 655ab12

File tree

1 file changed

+19
-14
lines changed
  • articles/ai-services/computer-vision/Tutorials

1 file changed

+19
-14
lines changed

articles/ai-services/computer-vision/Tutorials/liveness.md

Lines changed: 19 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -21,10 +21,12 @@ The liveness detection solution successfully defends against various spoof types
2121
[!INCLUDE [liveness-sdk-gate](../includes/liveness-sdk-gate.md)]
2222

2323

24-
## Key concepts
24+
## Introduction
2525

2626
The liveness solution integration involves two distinct components: a frontend mobile/web application and an app server/orchestrator.
2727

28+
:::image type="content" source="../media/liveness/liveness-diagram.jpg" alt-text="Diagram of the liveness workflow in Azure AI Face." lightbox="../media/liveness/liveness-diagram.jpg":::
29+
2830
- **Frontend application**: The frontend application receives authorization from the app server to initiate liveness detection. Its primary objective is to activate the camera and guide end-users accurately through the liveness detection process.
2931
- **App server**: The app server serves as a backend server to create liveness detection sessions and obtain an authorization token from the Face service for a particular session. This token authorizes the frontend application to perform liveness detection. The app server's objectives are to manage the sessions, to grant authorization for frontend application, and to view the results of the liveness detection process.
3032

@@ -35,9 +37,12 @@ Additionally, we combine face verification with liveness detection to verify whe
3537
| Liveness detection | Determine an input is real or fake, and only the app server has the authority to start the liveness check and query the result. |
3638
| Liveness detection with face verification | Determine an input is real or fake and verify the identity of the person based on a reference image you provided. Either the app server or the frontend application can provide a reference image. Only the app server has the authority to initial the liveness check and query the result. |
3739

38-
This tutorial demonstrates how to operate a frontend application and an app server to perform liveness detection across various language SDKs.
3940

40-
## Prerequisites
41+
## Get started
42+
43+
This tutorial demonstrates how to operate a frontend application and an app server to perform [liveness detection](#perform-liveness-detection) and [liveness detection with face verification](#perform-liveness-detection-with-face-verification) across various language SDKs.
44+
45+
### Prerequisites
4146

4247
- Azure subscription - [Create one for free](https://azure.microsoft.com/free/cognitive-services/)
4348
- Your Azure account must have a **Cognitive Services Contributor** role assigned in order for you to agree to the responsible AI terms and create a resource. To get this role assigned to your account, follow the steps in the [Assign roles](/azure/role-based-access-control/role-assignments-steps) documentation, or contact your administrator.
@@ -46,7 +51,7 @@ This tutorial demonstrates how to operate a frontend application and an app serv
4651
- You can use the free pricing tier (`F0`) to try the service, and upgrade later to a paid tier for production.
4752
- Access to the Azure AI Vision Face Client SDK for mobile (IOS and Android) and web. To get started, you need to apply for the [Face Recognition Limited Access features](https://customervoice.microsoft.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR7en2Ais5pxKtso_Pz4b1_xUQjA5SkYzNDM4TkcwQzNEOE1NVEdKUUlRRCQlQCN0PWcu) to get access to the SDK. For more information, see the [Face Limited Access](/legal/cognitive-services/computer-vision/limited-access-identity?context=%2Fazure%2Fcognitive-services%2Fcomputer-vision%2Fcontext%2Fcontext) page.
4853

49-
## Setup frontend applications and app servers to perform liveness detection
54+
### Setup frontend applications and app servers to perform liveness detection
5055

5156
We provide SDKs in different languages for frontend applications and app servers. They're available in these languages:
5257

@@ -60,7 +65,7 @@ We provide SDKs in different languages for frontend applications and app servers
6065
| Kotlin |-||
6166
| Swift |-||
6267

63-
### Integrate liveness into mobile application
68+
#### Integrate liveness into mobile application
6469

6570
Once you have access to the SDK, follow instruction in the [azure-ai-vision-sdk](https://github.com/Azure-Samples/azure-ai-vision-sdk) GitHub repository to integrate the UI and the code into your native mobile application. The liveness SDK supports Java/Kotlin for Android mobile applications, Swift for iOS mobile applications and JavaScript for web applications:
6671
- For Swift iOS, follow the instructions in the [iOS sample](https://aka.ms/azure-ai-vision-face-liveness-client-sdk-ios-readme)
@@ -69,19 +74,19 @@ Once you have access to the SDK, follow instruction in the [azure-ai-vision-sdk]
6974

7075
Once you've added the code into your application, the SDK handles starting the camera, guiding the end-user to adjust their position, composing the liveness payload, and calling the Azure AI Face cloud service to process the liveness payload.
7176

72-
### Download Azure AI Face client library for an app server
77+
#### Download Azure AI Face client library for an app server
7378

7479
The app server/orchestrator is responsible for controlling the lifecycle of a liveness session. The app server has to create a session before performing liveness detection, and then it can query the result and delete the session when the liveness check is finished. We offer a library in various languages for easily implementing your app server. Follow these steps to install the package you want:
7580
- For C#, follow the instructions in the [dotnet readme](https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/face/Azure.AI.Vision.Face/README.md)
7681
- For Java, follow the instructions in the [Java readme](https://github.com/Azure/azure-sdk-for-java/tree/main/sdk/face/azure-ai-vision-face/README.md)
7782
- For Python, follow the instructions in the [Python readme](https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/face/azure-ai-vision-face/README.md)
7883
- For JavaScript, follow the instructions in the [JavaScript readme](https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/face/ai-vision-face-rest/README.md)
7984

80-
#### Create environment variables
85+
##### Create environment variables
8186

8287
[!INCLUDE [create environment variables](../includes/face-environment-variables.md)]
8388

84-
## Perform liveness detection
89+
### Perform liveness detection
8590

8691
The high-level steps involved in liveness orchestration are illustrated below:
8792

@@ -412,7 +417,7 @@ The high-level steps involved in liveness orchestration are illustrated below:
412417

413418
---
414419

415-
## Perform liveness detection with face verification
420+
### Perform liveness detection with face verification
416421

417422
Combining face verification with liveness detection enables biometric verification of a particular person of interest with an added guarantee that the person is physically present in the system.
418423
There are two parts to integrating liveness with verification:
@@ -421,15 +426,15 @@ There are two parts to integrating liveness with verification:
421426

422427
:::image type="content" source="../media/liveness/liveness-verify-diagram.jpg" alt-text="Diagram of the liveness-with-face-verification workflow of Azure AI Face." lightbox="../media/liveness/liveness-verify-diagram.jpg":::
423428

424-
### Select a good reference image
429+
#### Select a good reference image
425430

426431
Use the following tips to ensure that your input images give the most accurate recognition results.
427432

428-
#### Technical requirements:
433+
##### Technical requirements:
429434
[!INCLUDE [identity-input-technical](../includes/identity-input-technical.md)]
430435
* You can utilize the `qualityForRecognition` attribute in the [face detection](../how-to/identity-detect-faces.md) operation when using applicable detection models as a general guideline of whether the image is likely of sufficient quality to attempt face recognition on. Only `"high"` quality images are recommended for person enrollment and quality at or above `"medium"` is recommended for identification scenarios.
431436

432-
#### Composition requirements:
437+
##### Composition requirements:
433438
- Photo is clear and sharp, not blurry, pixelated, distorted, or damaged.
434439
- Photo is not altered to remove face blemishes or face appearance.
435440
- Photo must be in an RGB color supported format (JPEG, PNG, WEBP, BMP). Recommended Face size is 200 pixels x 200 pixels. Face sizes larger than 200 pixels x 200 pixels will not result in better AI quality, and no larger than 6 MB in size.
@@ -441,7 +446,7 @@ Use the following tips to ensure that your input images give the most accurate r
441446
- Background should be uniform and plain, free of any shadows.
442447
- Face should be centered within the image and fill at least 50% of the image.
443448

444-
### Set up the orchestration of liveness with verification.
449+
#### Set up the orchestration of liveness with verification.
445450

446451
The high-level steps involved in liveness with verification orchestration are illustrated below:
447452
1. Providing the verification reference image by either of the following two methods:
@@ -808,7 +813,7 @@ The high-level steps involved in liveness with verification orchestration are il
808813

809814
---
810815

811-
## Clean up resources
816+
### Clean up resources
812817

813818
If you want to clean up and remove an Azure AI services subscription, you can delete the resource or resource group. Deleting the resource group also deletes any other resources associated with it.
814819

0 commit comments

Comments
 (0)