付费计量系统数据元素(Data elements)

        See also Clause 4 for a discussion on general concepts.Data elements are the instruments used to keep record of information on the status of the system and changes over time.
        参见条目 4 关于一般概念的讨论。数据元素是仪器使用保留关于系统状态和随时间变动的信息纪录。

        Definition of a Data_Object should state at least the following attributes.
        数据对象定义应该至少陈述以下属性。

        System entities embody data elements and they are thus distributed within the system to where they are required to fulfill their specific purpose. Some system entities may embody only a few data elements, while others may embody more. Where there is a large congregation of data elements such as in the CIS, it is normal practice for the data to be organized into more formal and manageable database structures.
        系统个体包含数据元素，他们被分布在系统需要他们的地方实现特定用处。一些系统个体也许包含仅有的几个数据元素, 而有些个体也许包含更多。有些系统有大量的数据元素集成，例如 CIS, 通常用更加正式和更加易处理的数据库结构实现数据组织。

        Relational associations exist between data elements, thus implying logical context and making it possible to model the external workings of the payment metering system fairly accurately. For example: “User_name”, “Password” and “Receipting_function” are 3 data elements that are associated by logic in that a particular user with that name and password is authorized to perform the activities related to the Receipting function.
        关系联合存在数据元素之间, 这意味着建立上下文逻辑，并且使建立预付费电表系统的表面工
作模型相当准确成为可能。例如: "用户名称", "密码" 和"发票/收据 是3个 数据元素，它们由逻辑相
互联系，一个确定的用户拥有相应用户名称和密码获准进行开发票/收据的活动。

        Data elements may be grouped into a record or a table of records where, in the case of a relational database, these tables are relationally associated or linked with each other and specifying the data elements in the record that are related to the data elements in the other table.
        数据元素可能被分组到一条记录或者一个记录表，在关系型数据库条件下，这些表相互关系，相互连接，并且指定在记录中的哪些数据元素和另外表中哪些数据元素相关联；

        In a normalized database, a particular data element will be primarily recorded in only one record in the entire database and thereafter, it will be merely referenced from other tables that require to have a relational association with that particular data element. Such an object oriented database design is highly desirable, because with careful consideration to the relational associations it can very effectively model the payment metering system and make the execution of the operational processes much simpler and easier to manage with a corresponding reduction in data errors.
        在一个标准数据库中,一个特殊数据元素将首先记录在整个数据库唯一的一条记录中，尔后, 它
将仅仅作为与要求和该特殊数据元素相关的表的参考。这样的面向对象型数据库设计就是非常好的,因为经过对关系仔细的考虑，它可以非常有效地建立预付费系统，并且使操作过程的处理更加简单和容易处理，使数据错误相应减少。

        In general, all entities in a payment metering system are secured by allocating unique reference identifiers to them and assigning access rights of read only, or read and write to the data elements associated with them for control purposes.
        总之, 在预付费系统中的所有个体安全通过分配唯一的标志符和分配只读或读/写数据元素的存
取权限，实现控制目的。

        In a normalized database, the classification of data elements is most conveniently done by reference to the system entity, with which the data element is contextually associated. For example: in the “Customer_record” we would find Customer_Name, Customer_ID and Customer_Address, so these data elements would conveniently be classified under “Customer“.
        在一个标准数据库, 数据元素的分类参考和数据元素关联系统个体是最方便地。例如: 在"客户
记录"中，我们会发现客户名称 、客户ID 和客户地址, 因此这些数据元素将很方便地被分类在"
顾客"中 。

        As specific systems are defined, each system should publish its specific data elements and
the attributes of each element. Examples of records that are generally used in payment metering systems are shown in the following table.
        当系统细节定义后, 各个系统应该公布它的具体数据元素和各个元素属性。在预付费系统中记录应用实例，参见下表。

        Table 11 – Examples of records used in payment metering systems
        表11 – 例记录在预付费系统中应用