PC6/PC7 AVPs
PC6/PC7 (application id: 16777340)
The PC6/PC7 interfaces enable communication between ProSe Functions located in different PLMNs (Public Land Mobile Networks), specifically between the Home PLMN (HPLMN) and local or visited PLMNs. The primary purpose of these interfaces is to support service authorization and management for ProSe services, such as ProSe Direct Discovery and communication.
PC6/PC7 workflow:
Service Authorization:
- When a UE in a local or visited PLMN attempts to use a ProSe service, the request is first processed by the local ProSe Function.
- The local ProSe Function uses the PC6 or PC7 interface to send a service authorization request to the ProSe Function in the HPLMN.
- The HPLMN ProSe Function processes this request and determines whether the UE is authorized to use the requested service.
- If authorized, the HPLMN ProSe Function sends a positive response back to the local ProSe Function, allowing the service to proceed. If not, the request is denied.
Direct Discovery Authorization:
- A UE initiates a ProSe Direct Discovery request through the local ProSe Function.
- The local ProSe Function forwards this request via the PC6/PC7 interface to the HPLMN for authorization.
- The HPLMN ProSe Function evaluates the request and returns the authorization status to the local ProSe Function.
- Based on the response, the local ProSe Function either allows the discovery process to continue or terminates it.
Discovery Filters and Application Code Translation:
- When a ProSe service requires the application of specific discovery filters, the local ProSe Function retrieves these filters from the HPLMN ProSe Function via the PC6/PC7 interface.
- The interface also facilitates the translation of ProSe Application Codes to their corresponding Application Names, ensuring that services are accurately identified and managed.
For complete technical specification of PC6/PC7 interface in Diameter protocol please refer to: [3GPP TS 29.345].
package com.mobius.software.telco.protocols.diameter.primitives.pc6
Name |
AVP Code |
Data Type |
Vendor |
App-Identifier |
3840 |
Grouped |
3GPP |
Used to identify a specific application within the Operating System (OS) context. It contains the OS ID and OS Application ID, enabling the differentiation and identification of applications in the network. The AVP structure is defined as follows: OS-ID (OctetString, Mandatory): Identifies the Operating System associated with the application. OS-App-ID (UTF8String, Mandatory): Contains the Application ID within the identified Operating System. |
|||
App-Layer-User-Id |
3801 |
UTF8String |
3GPP |
Identifies a user within the context of a specific application. It serves as a unique identifier, often resembling an email or username format (e.g., alice@social.net), enabling application-layer-level identification. |
|||
Assistance-Info |
3802 |
Grouped |
3GPP |
Provides supporting information for direct discovery and communication between User Equipment (UEs). It includes optional assistance data related to WLAN networks to facilitate proximity-based services and optimized communications. The AVP structure is defined as follows: WLAN-Assistance-Info (Optional): Contains WLAN-specific assistance parameters to support UE discovery and communications. |
|||
Assistance-Info-Validity-Timer |
3803 |
Unsigned32 |
3GPP |
Specifies the maximum duration, in seconds, for which the provided Assistance Information remains valid. It is primarily used to define the time-to-live (TTL) for assistance-related data in proximity-based discovery and communication scenarios. Value = 0 Assistance Information is immediately invalid upon delivery. Value > 0 Specifies the time-to-live (TTL) in seconds. Default behavior assumes that assistance information is valid indefinitely. |
|||
Banned-PDUID |
3841 |
OctetString |
3GPP |
Used to specify a ProSe Discovery UE ID (PDUID) that uniquely identifies a User Equipment (UE) which is banned from participating in restricted ProSe direct discovery requests. No UEs are banned by default, enabling all UEs for discovery. |
|||
Banned-RPAUID |
3842 |
UTF8String |
3GPP |
Used to specify a Restricted ProSe Application User ID (RPAUID) that uniquely identifies an application user who is banned from participating in restricted ProSe direct discovery requests. No application users are banned by default, enabling all RPAUIDs for discovery. |
|||
Beginning-Suffix |
3843 |
OctetString |
3GPP |
Specifies the lowest suffix in a consecutive sequence of ProSe Restricted Code Suffixes or ProSe Application Code Suffixes. It defines the starting point for a range of suffixes used in ProSe Discovery or ProSe Application Codes. |
|||
Change-Of-Area-Type |
3825 |
Grouped |
3GPP |
Defines triggers and parameters for location update events related to ProSe functions. It specifies the type of event and reporting rules for updating a UE's location during Proximity Service (ProSe) operations. The AVP structure is defined as follows: Location-Update-Event-Trigger (Enumerated): Specifies the event type triggering the location update. E.g., cell change, TA change. Report-Cardinality (Enumerated): Indicates whether updates are single or multiple (with intervals). Enumerated values:
Minimum-Interval-Time (Unsigned32, Optional): Defines the minimum interval (in seconds) for repeated updates when multiple reporting is enabled. |
|||
Code-Receiving-Security-Material |
3860 |
Grouped |
3GPP |
Used to define security parameters for a UE (User Equipment) receiving restricted ProSe direct discovery messages. It specifies how the received messages are protected and provides keys, indicators, and encryption settings. The AVP structure is defined as follows: DUSK (OctetString): Discovery User Security Key for validating the security of the message. DUIK (OctetString): Discovery User Integrity Key for validating the integrity of the message. MIC-Check-Indicator (Enumerated): Specifies whether to validate MIC using DUIK or Match Reports. DUCK (OctetString): Discovery User Confidentiality Key for ensuring confidentiality. Encrypted-Bitmask (OctetString): Bitmask defining encrypted fields or content in the discovery message. Condition behaviour: MIC-Check-Indicator set to MATCH_REPORTS: DUIK may be omitted, but Match Reports must be included elsewhere in the message. DUCK and Encrypted-Bitmask present together: Must match encryption rules as per [TS 23.003]. |
|||
Discovery-Auth-Request |
3854 |
Grouped |
3GPP |
Contains information used in ProSe (Proximity Services) direct discovery authorization requests. This AVP enables various types of ProSe discovery operations, each defined by the Discovery-Type and its associated AVPs. The AVP structure is defined as follows: Discovery-Type (Mandatory): Specifies the type of ProSe discovery operation. Conditional additional AVPs based on the Discovery-Type value. Optional AVPs: User-Identity: Identifies the User Equipment (UE) involved in the discovery. ProSe-App-ID: The ProSe application identifier. ProSe-App-Code: A unique code for the ProSe application. ProSe-App-Code-Suffix-Range: Range of ProSe codes applicable. ProSe-Validity-Timer: Time for which the discovery authorization is valid. App-Identifier: Identifier of the specific application. Requesting-RPAUID: Identifier of the requesting RPAUID. Target-RPAUID: Identifier of the target RPAUID. Target-PDUID: Identifier of the target PDUID. ProSe-Restricted-Code: Restriction code for ProSe discovery. ProSe-Query-Code: Query code for restricted discovery. ProSe-Response-Code: Response code for restricted discovery. ProSe-Restricted-Code-Suffix-Range: Range of restricted codes. Banned-RPAUID: Identifier of banned RPAUIDs. Banned-PDUID: Identifier of banned PDUIDs. Service-Result: Result of the requested service. PC5-Tech: Indicates the PC5 radio technology used. Discovery-Type Based Behavior Depending on the value of Discovery-Type, specific mandatory and optional AVPs must be included:
|
|||
Discovery-Auth-Response |
3855 |
3GPP |
Grouped |
Used in ProSe (Proximity Services) to provide responses to ProSe direct discovery authorization requests. It carries the necessary parameters based on the specific discovery operation indicated by the Discovery-Type. The AVP structure is defined as follows: Discovery-Type (Enumerated): Specifies the request type being responded to (e.g., announcing, monitoring). ProSe-Discovery-Filter (List, Grouped): Provides filters for monitoring requests to refine discovery results. Visited-PLMN-Id (OctetString): Identifies the visited PLMN (Public Land Mobile Network) where the UE is currently operating. ProSe-Restricted-Code (OctetString): Returns a restricted code for restricted discovery scenarios. ProSe-Query-Code (missing definition) (OctetString): Sends a query code for restricted discovery queries. ProSe-Response-Code (missing definition) (OctetString): Provides a response code for restricted discovery operations. ProSe-Validity Timer (Unsigned32): Specifies the validity period (in seconds) for the discovery authorization. Code-Sending-Security-Material (Grouped): Contains security material for sending discovery messages securely. Code-Receiving-Security-Material (Grouped): Contains security material for receiving discovery messages securely. DUIK (OctetString): Includes a DUIK (Discovery User Identity Key) for MIC checking or encryption purposes. PC5-tech (OctetString): Specifies the radio technology used for discovery (e.g., PC5 interface). Discovery-Type Based Behavior Below are the behaviors and required AVPs for each Discovery-Type:
|
|||
Discovery-Entry-ID |
3859 |
Unsigned32 |
3GPP |
Used to uniquely identify a discovery entry within the UE context related to the discovery authorization request in the requesting ProSe Function. Discovery-Entry-ID must be valid and unique for successful identification. |
|||
Discovery-Type |
3855 |
Enumerated (Unsigned32) |
3GPP |
Specifies the type of ProSe (Proximity Services) Direct Discovery Authorization Request. It defines the purpose of the discovery operation (e.g., announcing, monitoring, or authorization) and differentiates between open and restricted discovery models. Enumerated Values: 0 ANNOUNCING_REQUEST_FOR_OPEN_PROSE_DIRECT_DISCOVERY: Authorization request for a UE to announce in open ProSe Direct Discovery (Model A). 1 MONITORING_REQUEST_FOR_OPEN_PROSE_DIRECT_DISCOVERY: Authorization request for a UE to monitor in open ProSe Direct Discovery (Model A). 2 ANNOUNCING_REQUEST_FOR_RESTRICTED_PROSE_DIRECT_DISCOVERY: Authorization request for a UE to announce in restricted ProSe Direct Discovery (Model A). 3 MONITORING_REQUEST_FOR_RESTRICTED_PROSE_DIRECT_DISCOVERY: Authorization request for a UE to monitor in restricted ProSe Direct Discovery (Model A). 4 DISCOVEREE_REQUEST_FOR_RESTRICTED_PROSE_DIRECT_DISCOVERY: Authorization request for a discoveree UE to monitor in restricted ProSe Direct Discovery (Model B). 5 DISCOVERER_REQUEST_FOR_RESTRICTED_PROSE_DIRECT_DISCOVERY: Authorization request for a discoverer UE to announce in restricted ProSe Direct Discovery (Model B). 6 DISCOVERER_ANNOUNCING_REQUEST_FOR_RESTRICTED_PROSE_DIRECT_DISCOVERY: Authorization request for a discoverer UE in the visited PLMN to announce in restricted ProSe Direct Discovery (Model B). 7 MONITORING_UPDATE_FOR_RESTRICTED_PROSE_DIRECT_DISCOVERY: Request from the ProSe Function to ban a user for monitoring authorization in restricted ProSe Direct Discovery (Model A). 8 MONITORING_RESPONSE_FOR_RESTRICTED_PROSE_DIRECT_DISCOVERY: Request from the ProSe Function to report the result of a monitoring authorization in restricted ProSe Direct Discovery (Model A). |
|||
DUCK |
3862 |
OctetString |
3GPP |
Used in restricted ProSe (Proximity Services) direct discovery. It contains the encryption key required to encrypt and decrypt specific portions of messages exchanged during ProSe discovery operations. The format and use of DUCK are defined in [TS 33.303] for ProSe security procedures. |
|||
DUIK |
3863 |
OctetString |
3GPP |
Used in restricted ProSe (Proximity Services) direct discovery. It contains the integrity key required to compute the Message Integrity Code (MIC) for verifying the integrity of specific messages exchanged during ProSe discovery operations. The format and handling of DUIK are specified in [TS 33.303]. |
|||
DUSK |
3862 |
OctetString |
3GPP |
Used in restricted ProSe (Proximity Services) direct discovery. It contains the scrambling key required to scramble or unscramble specific messages during ProSe discovery operations. The format and handling of DUSK are specified in [TS 33.303]. |
|||
Encrypted-Bitmask |
3863 |
OctetString |
3GPP |
Used in ProSe (Proximity Services) direct discovery to indicate which parts of a ProSe Restricted Code, ProSe Query Code, or ProSe Response Code are encrypted using the DUCK (Discovery User Confidentiality Key). It shall contain a 184-bit bitmask which uses bit "1" to mark the positions of the bits of a ProSe Restricted Code, ProSe Query Code or ProSe Response Code, for which the DUCK encryption is applied. |
|||
Ending-Suffix |
3870 |
OctetString |
3GPP |
Specifies the highest suffix in a consecutive sequence of ProSe Restricted Code Suffixes or ProSe Application Code Suffixes. Used to define the range of suffixes allocated to a ProSe discovery or communication session. The suffixes comply with the format specified in [TS 23.003]. The size of the suffix must align with octet boundaries. |
|||
Filter-Id |
3871 |
OctetString |
3GPP |
Used to specify a Discovery Filter Identifier associated with ProSe Direct Discovery operations. It identifies a specific filter applied to ProSe discovery requests and responses. Enables fine-grained control over discovery rules for user equipment (UE) in ProSe communications. Supports policy-based filtering by matching filters during the discovery process. |
|||
Location-Report-Interval-Time |
3850 |
Unsigned32 |
3GPP |
Specifies the time interval (in seconds) between successive location reports generated by a ProSe Function or user equipment (UE) during ProSe operations. It is used for periodic reporting of location information to maintain tracking and monitoring. Supports time-bound delivery of location updates for ProSe discovery and communication scenarios. Allows configuration of reporting frequency to balance accuracy and network efficiency. The interval must be greater than zero to ensure valid reporting periods. If this AVP is missing, the system may rely on default intervals defined in configuration. |
|||
Location-Update-Event-Trigger |
3851 |
Enumerated |
3GPP |
Defines the type of event that triggers a location update procedure for the User Equipment (UE) in ProSe (Proximity Services) scenarios. It specifies whether the UE has entered, exited, or is present within a predefined target area. Enumerated Values 0 UE_ENTRY: Triggered when the UE enters a predefined area. 1 UE_EXIT: Triggered when the UE leaves a predefined area. 2 UE_PRESENCE: Triggered when the UE is currently present in a predefined area. |
|||
Location-Update-Event-Type |
3850 |
Enumerated |
3GPP |
Specifies types of events that will trigger a location update for a User Equipment (UE) in ProSe (Proximity Services) or location-based applications. These events include UE availability, movement across areas, or periodic triggers. Enumerated Values 0 UE_AVAILABLE: Triggered when the MSC/SGSN/MME establishes contact with the UE. 1 CHANGE_OF_AREA: Triggered when the UE enters, leaves, or is within a predefined area. 2 PERIODIC_LOCATION: Triggered when a periodic timer expires in the UE to update location. |
|||
Location-Update-Trigger |
3823 |
Grouped |
3GPP |
Used to define the triggers for location updates in ProSe (Proximity Services) or location-based applications. It determines the event types that activate a location update procedure for reporting the UE's location to the ProSe Function initiating the Proximity Request. The AVP structure is defined as follows: Location-Update-Event-Type (Enumerated): Defines the event type that triggers the location update. Values:
Change-Of-Area-Type (Grouped) (Conditional): Specifies additional area-related parameters for location triggers. Must be present if Location-Update-Event-Type is CHANGE_OF_AREA (1). Periodic-Location-Type (Grouped) (Conditional): Specifies periodic update parameters (e.g., interval time). Must be present if Location-Update-Event-Type is PERIODIC_LOCATION (2). |
|||
MAC-Address |
3806 |
UTF8String |
3GPP |
Represents a 6-octet MAC address used as a link-layer identifier for discovery and communication in ProSe (Proximity Services) or other network functionalities. Encoding Format String Representation: Uppercase ASCII characters. Dash-separated octets. Fixed length of 17 characters (including separators). Example: "00-10-A4-23-19-C0" |
|||
Match-Report |
3807 |
Grouped |
3GPP |
Provides information related to a match event in a ProSe direct discovery session. This AVP contains details about the ProSe Application Code, Application ID, validity timer, refresh timer, and optionally the PC5 radio technology that the UE is using. The AVP structure is defined as follows: Discovery-Type (Mandatory, Enumerated): Specifies the type of discovery request being reported (e.g., Monitoring).
ProSe-App-Code (Mandatory, OctetString): Identifies the application code used for ProSe discovery. ProSe-Metadata-Index-Mask (Optional, OctetString): Index mask related to the ProSe metadata for filtering and matching. ProSe-App-Id (Mandatory, UTF8String): The Application ID associated with ProSe service. ProSe-Validity-Timer (Mandatory, Unsigned32): Specifies the validity duration (in seconds) for ProSe results. ProSe-Match-Refresh-Timer (Mandatory, Unsigned32): Specifies the refresh interval for ProSe match reports. ProSe-Application-Metadata (Optional, UTF8String): Contains metadata information for ProSe applications. PC5-tech (Optional, OctetString): Optionally specifies the PC5 radio technology in use. |
|||
Match-Report-Info |
3857 |
Grouped |
3GPP |
Contains details required for querying ProSe match report information, including user identity and associated ProSe application IDs. The AVP structure is defined as follows: Discovery-Type (Mandatory, Enumerated): Specifies the type of discovery request (e.g., monitoring request).
User-Identity (Mandatory, Grouped): Contains the user identity information used in discovery. ProSe-App-ID (Mandatory, UTF8String): List of ProSe Application IDs related to the user and discovery monitoring. (Optional): Any additional AVPs as required. |
|||
Match-Request |
3856 |
Grouped |
3GPP |
Contains information required for initiating a match request for ProSe Direct Discovery. The AVP structure is defined as follows: Discovery-Type (Mandatory, Enumerated): Specifies the type of discovery request (e.g., monitoring request).
User-Identity (Mandatory, Grouped): Contains the user identity information used in discovery. Visited-PLMN-ID (Mandatory, OctetString): Identifies the visited PLMN ID during the discovery process. ProSe-App-Code-Info (Mandatory, Grouped): List of ProSe Application Code Info linked to the discovery request. PC5-tech (Optional, OctetString): Indicates the PC5 radio technology used by the UE. |
|||
Match-Timestamp |
3851 |
Time |
3GPP |
Represents the UTC timestamp indicating when a ProSe discovery match event occurred. |
|||
MIC |
3836 |
OctetString |
3GPP |
MIC AVP (Message Integrity Check) is a binary OctetString AVP designed to store the integrity verification data for a ProSe Application Code. It is used to ensure message authenticity and data integrity in ProSe direct discovery communications. |
|||
MIC-Check-Indicator |
3865 |
Enumerated |
3GPP |
Specifies whether the ProSe Function should verify the Message Integrity Check (MIC) field of a received discovery message. It is used to indicate whether the MIC validation process must be delegated to the ProSe Function. Enumerated Values 1 MIC_CHECK_BY_PROSE_FUNCTION: The MIC check is required to be performed by the ProSe Function. |
|||
Minimum-Interval-Time |
3828 |
Unsigned32 |
3GPP |
Specifies the minimum number of seconds between consecutive area event reports for ProSe Function updates related to location monitoring or change of area triggers. |
|||
Operating-Channel |
3808 |
Unsigned32 |
3GPP |
Specifies the operating frequency channel (in MHz) used for Wi-Fi Peer-to-Peer (P2P) discovery and communication. This value determines the radio frequency on which ProSe direct communication or discovery operations are conducted. |
|||
OS-App-ID |
3842 |
UTF8String |
3GPP |
Identifies an operating system-specific application used in ProSe Discovery Requests. It consists of two parts as defined in [TS 24.334]:
|
|||
OS-ID |
3841 |
OctetString |
3GPP |
Used to identify the operating system running on a device. It plays a key role in ProSe (Proximity Services) and device-to-device communication frameworks by enabling OS-specific handling and policies, as specified in [TS 24.334]. |
|||
P2P-Features |
3809 |
Unsigned32 (Bitmask) |
3GPP |
Used to define Wi-Fi Peer-to-Peer (P2P) functionalities supported by a User Equipment (UE) in ProSe (Proximity Services). It indicates whether the UE can act as a Group Owner (GO) in a Wi-Fi P2P network or as a client. Bitmask Table: 0 Group Owner Indication: When set, UE acts as a Group Owner (GO) in Wi-Fi P2P networks. If not set, UE acts as a client. |
|||
PC5-Tech |
3868 |
OctetString |
3GPP |
Identifies the PC5 radio technology used for Proximity Services (ProSe), particularly for device-to-device (D2D) communication. It provides the radio interface type required for direct discovery and direct communication over the PC5 interface. The PC5-tech field follows the structure defined in [TS 24.334], clause 12.2.2.71, and is encoded as a single octet. Encoding Details: The PC5-tech parameter is a one-octet bitmask structured as follows: Bit, Value, Meaning 1, 0, E-UTRA not included 1, 1, E-UTRA is included 2, 0, WLAN not included 2, 1, WLAN is included 3–8, 000000, Spare bits (set to 0) Example Encoding (Binary Representation): 00000011 (0x03) - Both E-UTRA and WLAN are included 00000001 (0x01) - Only E-UTRA is included 00000010 (0x02) - Only WLAN is included 00000000 (0x00) - Neither E-UTRA nor WLAN is included |
|||
Periodic-Location-Type |
3829 |
Grouped |
3GPP |
Specifies parameters for periodic location reporting of a User Equipment (UE). It defines the time interval between successive location reports and the total number of reports required. This AVP is essential for scenarios involving location tracking, area monitoring, and Proximity Services (ProSe). It ensures that periodic location updates are reported as per configuration. The AVP structure is defined as follows: Location-Report-Interval-Time (Unsigned32): Time interval (in seconds) between successive location reports. Total-Number-Of-Reports (Unsigned32): Total number of location reports to be sent. |
|||
PMR-Flags |
3852 |
Unsigned32 (Bitmask) |
3GPP |
Specifies configuration flags for ProSe Metadata Requests (PMR). It contains bitmask values indicating whether metadata information associated with the ProSe Application ID is requested. Bitmask Definition Table: 0: Metadata Requested: If set, metadata information associated with the ProSe Application ID is requested. Other Bits: Reserved: Bits not defined are cleared by the sender and discarded by the receiver. |
|||
ProSe-App-Code |
3810 |
OctetString |
3GPP |
Contains either a ProSe Application Code or a ProSe Application Code Prefix. This AVP is associated with a ProSe Application ID and is used for identifying Proximity-based Services (ProSe) applications in ProSe direct discovery. The ProSe Application Code serves as a temporary identity that enables UEs to announce or monitor ProSe services while maintaining user privacy. The ProSe Application Code Prefix is used when the full ProSe Application Code is not available, and it must be combined with a ProSe Application Code Suffix to form a complete identifier. ProSe Application Code: The ProSe Application Code is a 184-bit temporary identity. It consists of a fixed structure to ensure efficient ProSe discovery. ProSe Application Code Prefix: Used when the full ProSe Application Code is unavailable. The temporary identity part is of variable length (must be multiples of 8 bits). The minimum length is 8 bits, and the maximum length is 152 bits. The combined length of the ProSe Application Code Prefix and the ProSe Application Code Suffix must be 184 bits. |
|||
ProSe-App-Code-Info |
3835 |
Grouped |
3GPP |
Designed to contain information related to a ProSe Application Code, including its associated Message Integrity Check (MIC) and a UTC-based counter. It is used in ProSe Direct Discovery and communication processes to ensure data integrity, security, and synchronization. The AVP structure is defined as follows: ProSe-App-Code (OctetString): Contains the ProSe Application Code associated with the ProSe Application ID. MIC (OctetString): Contains the Message Integrity Check (MIC) for verifying the integrity of the ProSe Application. UTC-Based Counter (Unsigned32): Provides a timestamp or counter based on UTC to prevent replay attacks and maintain security. |
|||
ProSe-App-Code-Suffix-Range |
3867 |
Grouped |
3GPP |
Used to define a range of consecutive ProSe Application Code Suffixes. These suffixes can be appended to a ProSe Application Code Prefix to form complete codes used in ProSe Direct Discovery and communication procedures. Beginning-Suffix and Ending-Suffix shall have the same length. The AVP structure is defined as follows: Beginning-Suffix (OctetString): The first suffix in the range. Required and must be set. Ending-Suffix (OctetString): The last suffix in the range. Optional—if omitted, the range consists of only the Beginning-Suffix. |
|||
ProSe-App-Id |
3811 |
UTF8String |
3GPP |
Used to uniquely identify a ProSe application. It serves as an identifier for Proximity-based Services (ProSe) applications, enabling devices to discover and communicate with each other based on application-specific requirements. |
|||
ProSe-Application-Metadata |
3853 |
UTF8String |
3GPP |
Contains metadata associated with a ProSe Application ID. It is used primarily in Match Reports to provide additional contextual information about the ProSe application involved in the discovery or communication process. |
|||
ProSe-App-Mask |
3812 |
OctetString |
3GPP |
Contains a ProSe Application Mask, which is a bitmask provided by the ProSe Function to control how a monitoring UE matches received PC5_DISCOVERY messages. The ProSe Application Mask is used in ProSe Direct Discovery Filtering and determines whether a ProSe Application Code is considered a valid match.
Matching Behavior: All bits set to 1: Full matching (strict filter) Some bits set to 0: Partial matching (looser filter) Multiple masks in filter: Multiple matching conditions |
|||
ProSe-Discovery-Filter |
3813 |
Grouped |
3GPP |
Used to specify filtering criteria for ProSe Discovery operations. It contains parameters to define filters, application IDs, validity timers, application codes, and application masks, enabling precise control over ProSe application discovery and authorization processes. The AVP structure is defined as follows: Filter-Id (OctetString, Mandatory): Unique identifier for the filter. ProSe-App-Id (UTF8String, Mandatory): ProSe Application ID, identifying the application associated with the filter. ProSe-Validity-Timer (Unsigned32, Mandatory): Specifies the validity duration (in seconds) of the filter. ProSe-App-Code (OctetString, Mandatory): ProSe Application Code used in the discovery process. ProSe-App-Mask (OctetString, Optional): List of ProSe Application Masks providing additional filtering criteria. |
|||
ProSe-Match-Refresh-Timer |
3838 |
Unsigned32 |
3GPP |
Specifies the time interval (in seconds) a User Equipment (UE) must wait before generating and sending a new Match Report for a given ProSe Application Code. |
|||
ProSe-Metadata-Index-Mask |
3839 |
OctetString |
3GPP |
The ProSe-Metadata-Index-Mask AVP is an OctetString that contains a bitmask used for identifying and isolating metadata indexes within the ProSe Application Code. This bitmask is provided by the ProSe Function to indicate which portion of the ProSe Application Code corresponds to the Metadata Index for use by the monitoring UE. Encoding Rules (from 3GPP [TS 24.334]):
Behavior: Bits set to 1: Specifies the portion used for Metadata Index Bits set to 0: Excluded from Metadata Index interpretation |
|||
ProSe-Restricted-Code |
3846 |
OctetString |
3GPP |
Used to contain a ProSe Restricted Code. This code is associated with a Restricted ProSe Application User ID (RPAUID) and is defined in 3GPP [TS 23.003]. Restricted ProSe Application User ID a single 64-bit identifier that corresponds to one or more Restricted ProSe Application User ID(s) |
|||
ProSe-Restricted-Code-Suffix-Range |
3847 |
Grouped |
3GPP |
Used to specify a range of consecutive ProSe Restricted Code Suffixes that can be appended to a ProSe Restricted Code Prefix. It is primarily utilized in ProSe Direct Discovery scenarios to define valid suffix ranges for restricted discovery codes. The AVP structure is defined as follows: Beginning-Suffix (OctetString, Mandatory): Specifies the lowest suffix in the range. Ending-Suffix (OctetString, Optional): Specifies the highest suffix in the range. If omitted, the range consists of only the Beginning-Suffix. Both Beginning-Suffix and Ending-Suffix must have the same length in bytes. |
|||
ProSe-Validity-Timer |
3815 |
Unsigned32 |
3GPP |
Specifies the maximum number of seconds that a ProSe Application Code or a ProSe Discovery Filter remains valid. It is a time-based parameter that ensures ProSe operations adhere to defined lifespans, enhancing security and resource management. |
|||
PRR-Flags |
3814 |
Unsigned32 (Bitmask32) |
3GPP |
Specifies ProSe-related flags used in ProSe Resource Requests (PRR). Each bit in the bitmask represents a specific feature or capability that may be enabled for ProSe Direct Discovery and Communication. Bitmask Definition 0: WLAN Indication: Indicates that the UE requests EPC support for WLAN-based direct discovery and communication. Note: Bits not explicitly defined in this table must be cleared by the sending ProSe Function and discarded by the receiving ProSe Function. |
|||
Report-Cardinality |
3827 |
Enumerated |
3GPP |
Defines whether the change of area event should be reported once or multiple times. This AVP helps configure the behavior of location update reports when a UE (User Equipment) triggers area-related events. Enumerated Values 0: SINGLE: Reports the change of area event once and does not send further updates. 1: MULTIPLE: Reports the change of area event multiple times based on defined intervals or triggers. |
|||
Requesting-EPUID |
3816 |
UTF8String |
3GPP |
Represents a unique identifier for a User Equipment (UE) participating in EPC-level ProSe Discovery and WLAN direct communication. It is used to identify a UE that triggers a Proximity Service (ProSe) request for direct discovery or communication. |
|||
Requesting-RPAUID |
3843 |
UTF8String |
3GPP |
Specifies a unique identifier for an application user initiating a restricted ProSe direct discovery request. It is utilized in ProSe (Proximity Services) to manage and control restricted discovery requests between users or devices within predefined application groups. |
|||
Targeted-EPUID |
3817 |
UTF8String |
3GPP |
Designed to provide a unique identifier for a UE (User Equipment) that is targeted by a Proximity Services (ProSe) request in the context of EPC-level ProSe Discovery and WLAN direct communication. |
|||
Target-PDUID |
3845 |
OctetString |
3GPP |
Used to specify a ProSe Discovery UE ID that uniquely identifies the targeted UE in a restricted ProSe direct discovery request. |
|||
Target-RPAUID |
3844 |
UTF8String |
3GPP |
Used to specify a Restricted ProSe Application User ID (RPAUID) that uniquely identifies an application user targeted by a restricted ProSe direct discovery request. |
|||
Time-Window |
3818 |
Unsigned32 |
3GPP |
Defines the maximum duration (in seconds) for which a Proximity request remains valid. It provides a time constraint for processing or responding to a proximity-based request in ProSe (Proximity Services). |
|||
Total-Number-Of-Reports |
3831 |
Unsigned32 |
3GPP |
Specifies the maximum number of requested location reports during Proximity Services (ProSe). It is part of the Periodic-Location-Type AVP and determines the number of reports required for location tracking or proximity monitoring. |
|||
UTC-Based-Counter |
3837 |
Unsigned32 |
3GPP |
Specifies a counter value in seconds based on Coordinated Universal Time (UTC). It is associated with a discovered ProSe Application Code in Proximity Services (ProSe), ensuring time synchronization for discovery events. |
|||
Validity-Time-Announce |
3832 |
Unsigned32 |
3GPP |
Specifies the maximum validity period (in seconds) for a ProSe announcing authorization policy. This AVP determines how long the ProSe announcing permissions are valid before requiring renewal or reauthorization. |
|||
Validity-Time-Communication |
3834 |
Unsigned32 |
3GPP |
Specifies the maximum validity period (in seconds) for a ProSe communication authorization policy. It controls the duration during which a ProSe communication session remains authorized before requiring renewal or reauthorization. |
|||
Validity-Time-Monitor |
3833 |
Unsigned32 |
3GPP |
Specifies the maximum validity period (in seconds) for a ProSe monitoring authorization policy. It controls the duration during which ProSe monitoring operations remain authorized before requiring renewal or reauthorization. |
|||
WiFi-P2P-Assistance-Info |
3819 |
Grouped |
3GPP |
Provides assistance information for WLAN direct discovery and communication required by the Wi-Fi Peer-to-Peer (P2P) technology. It facilitates device-to-device communication over WLAN by supplying relevant configuration and security parameters. The AVP structure is defined as follows: SSID (UTF8String, Optional): Specifies the Service Set Identifier (SSID) used for WLAN discovery. EAP-Master-Session-Key (OctetString, Optional): Contains the EAP session key for secure WLAN communication. P2P-Features (Bitmask32, Optional): Indicates features supported by the device, such as Group Owner (GO). WLAN-Link-Layer-Id-List (Grouped, Optional): Provides identifiers for link-layer connections. Operating-Channel (Unsigned32, Optional): Specifies the Wi-Fi channel frequency (MHz) for communication. Assistance-Info-Validity-Timer (Unsigned32, Optional): Defines the maximum validity duration (seconds) of the assistance info. |
|||
WLAN-Assistance-Info |
3820 |
Grouped |
3GPP |
Provides assistance information for WLAN direct discovery and communication between User Equipment (UE) devices. It encapsulates Wi-Fi Peer-to-Peer (P2P) assistance information to facilitate device-to-device communication via WLAN technologies. The AVP structure is defined as follows: WiFi-P2P-Assistance-Info (Grouped, Optional): Provides P2P discovery parameters for WLAN communication configuration. |
|||
WLAN-Link-Layer-Id |
3821 |
Grouped |
3GPP |
Provides link layer identity information to support WLAN direct discovery and communication between User Equipment (UE) devices. It primarily encapsulates a MAC address as an identifier for the link layer. The AVP structure is defined as follows: MAC-Address (UTF8String, Optional): Contains the 6-octet MAC address in ASCII with dash separators. |
|||
WLAN-Link-Layer-Id-List |
3822 |
Grouped |
3GPP |
Used to manage a list of WLAN Link Layer IDs associated with User Equipment (UE) implementing the Group Owner (GO) functionality in Wi-Fi Peer-to-Peer (P2P) groups. It serves as a container for multiple WLAN-Link-Layer-Id AVPs, enabling identification and communication between multiple UEs in a P2P group. The AVP structure is defined as follows: WLAN-Link-Layer-Id (Grouped (List), Mandatory): Contains multiple WLAN-Link-Layer-Id AVPs within the list. |
Start innovating with Mobius
What's next? Let's talk!