BAIC — Update Request

User Interfaces Release 9.1 Subscriber Provisioning Reference Manual entity identification set of attributes and values criteria Request Identification : A request tag (e.g., ) must be used to formulate the type of request. Entity Identification : An entity tag (e.g., ) must be used to identify the entity that will receive the request. Set : A set is used to specify the value for each attribute of that entity. Criteria : The criteria (also called „where џ) can be an expression (expr) or set of expressions separated by operators (op). The square brackets “[“, “]” indicate optional items. The grammar format is provided below: where := expr [op expr] ...

The "where" part is a list consisting of the following items: expr := [expr | attr | attr op value] attr := name=”name” ent=”entity” ns=”namespace” op := value=[“=” | “!=” | “and” | “or” | “gt” | “ge” | “lt” | “le”] value := val =”value” The operators are: equal (=), not equal (!=),and, or, greater than (gt), greater than or equal (ge),less than (lt), less than or equal (le) respectively. The default operator is equal (=). Note: The "resonly="y/n" field is optional and can be used in each request in order to indicate to the system whether it must include this request in the reply or simply the response.

Note that excluding this optional attribute simply means that the system uses the default behavior, in which case it returns the entire request in the reply. … resonly=”y” … request properties Moreover, it can be used in the transaction. In this case, it will apply to all the requests in the transaction. … request properties … request properties Update Request Update requests are formulated with the following parts: request identification entity identification set of attributes and values criteria (also called "where") operations (AddToSet, RemoveFromSet to manage sets) 33 910-6701-001 Revision A, June 2013