Please enable JavaScript.

Coggle requires JavaScript to display documents.

FRMCS plug tests - Coggle Diagram

- - - - per-user functional alias information;
      - per-functional alias status information
      - 9A.3.1.2 Syntax
        
        Table 9A.3.1.2-1: XML schema
        
        9A.3.2 Extension of application/simple-filter+xml MIME type
        
        need to support to not fail during plugtests
  - - - one <FunctionalAliasList> element which contains one or more <entry> element
      - H) an <allow-query-functional-alias-other-user> element;
      - e) a <RulesForAffiliation> element containing: <ListOfLocationCriteria>
      - Location?
  - - - SUBSCRIBE
        
        application/vnd.3gpp.mcptt-info+xml
      - NOTIFY
        
        request contains an application/pidf+xml MIME body indicating per-user
        functional alias information constructed according to subclause 9A.3.1
      - If a location criterion for functional alias activation or de-activation is met, the MCPTT client shall initiate the
        functional alias status change procedure as specified in subclause 9A.2.1.2.
    - - Validations
      - PUBLISH
        
        application/pidf+xml
        
        <p-id-fa>
        
        Consider proposal from last Plugtests to distinguish the request from Affiliation change request
  - - - a
      - a receiving subscription to functional alias status
      - sending notification of change of functional alias status NOTIFY to clients
      - sending functional alias status change towards MCPTT server owning the functional
        
        send an activation request of a served MCPTT ID for a handled functional alias ID
        
        send an deactivation request of a served MCPTT ID for a handled functional alias ID
        
        send a take over request of a served MCPTT ID for a handled functional alias ID due to take over
        
        send an activation request of a served MCPTT ID for a handled functional alias ID due to near expiration of
        the previously published information
      - functional alias status determination from MCPTT server owning the functional alias
        
        SUBSCRIBE
      - functional alias resolution from MCPTT server owning the functional alias
        
        In order to discover the MCPTT users that have successfully activated a handled functional alias in the MCPTT server
        owning the functional alias, the MCPTT server shall generate an initial SIP SUBSCRIBE request
        like CONFERENCE INFO?
        
        Request-URI to the public service identity of the controlling MCPTT function associated with the
        handled functional alias
        
        resolving needs for Whom? TPF or OPF?
      - Storage
        
        The MCPTT server shall maintain a list of MCPTT user information entries
    - - receiving functional alias status change
        PUBLISH handling
      - receiving subscription to functional alias status :
        
        shall identify the served functional alias ID in the <mcptt-request-uri>
        
        shall identify the handled MCPTT ID in the <mcptt-calling-user-id>
      - sending notification of change of functional alias status
        9A.2.2.3.5
      - modification of functional alias eligibility check
      - receiving subscription to functional alias resolution
        
        requested functional alias ID in the <mcptt-request-uri>
      - sending notification of functional alias resolution
        9.2.2.3.y
      - Storage
        functional alias information entry