StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18823523
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-09-16T08:28:55.017
FavoriteCount
0
LastActivityDate
2013-09-16T08:28:55.017
LastEditDate
LastEditorUserId
0
OwnerUserId
1486865
ParentId
18814726
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
There are two CRS-related concepts : the CRS as a registry within the card, and the CRS application which exposes the former to device a application (typically EMV's AAUI) to display the configuration and query user's choice. Currently the CRS application is an optional part of the standard. The PPSE's role is to expose a list of payment applications to the point of sale (PoS). In order to do this, it listens to application activation events that are broadcast by the CRS (register). For this to work the banking apps will be instantiated specifying explicitly the PPSE as a destinator of their activation events. In EMV "internal mode", bank apps typically have the contactless self-activation priviledge, which means that the bank mobile app will send a set-status command to the banking card app, which activates itself using the CRS APIs. In turn the CRS will broadcast this event to all authorised registered listeners, including the PPSE. On top of that, in some markets, another application receives the broadcast in order to implement a market-specific policy. For instance AEPM requirements (which apply broadly in Europe) state that the PPSE's response shall only ever contain one application at a given point in time. To enforce this rule, there is a dedicated application (AEPM CREL) which will deactivate all other apps but the latest activated. This is described in details in the <a href="http://www.emvco.com/specifications.aspx?id=21" rel="nofollow">EMVCo</a> and <a href="http://www.aepm.com/uk_formulaire_telechargement.php" rel="nofollow">AEPM specifications</a>. CRS is covered in details in <a href="http://globalplatform.org/specificationscard.asp" rel="nofollow">GlobalPlatform's Amendment C to the card specification</a>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPPSE and CRS relation when using INTERNAL mode
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. UStakumar
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POPPSE and CRS relation when using INTERNAL mode
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.