Home

Results 1 - 10 of 402,000 for locate function. Search took 4.003 seconds.  
Sort by date/Sort by relevance
Draft new Recommendation X.738 (Corrigendum 1): Systems Management: summarization function (Corrigendum 1) Location: COM4-52 Summary: This Corrigendum corrects some texts in Recommendation X.738 which provides Summarization Function. (...) Draft new Recommendation X.743: Open Systems Interconnection - Systems Management - Part 20: Time Management Function Location: COM4-66 Summary: This Recommendation defines a systems function which consists of generic definitions, services, and functional units. (...) Draft new Recommendation X.746 (Corrigendum 1): Systems Management: Scheduling Function (Corrigendum 1) Location: COM4-59 Summary: This Corrigendum corrects some texts in Recommendation X.746 which defines the scheduling function which is a systems management function.
Language:English
Score: 1069335.2 - https://www.itu.int/itudoc/itu-t/circ/circ3/108_ww7.doc
Data Source: un
Draft new Recommendation X.738 (Corrigendum 1): Systems Management: summarization function (Corrigendum 1) Location: COM4-52 Summary: This Corrigendum corrects some texts in Recommendation X.738 which provides Summarization Function. (...) Draft new Recommendation X.743: Open Systems Interconnection - Systems Management - Part 20: Time Management Function Location: COM4-66 Summary: This Recommendation defines a systems function which consists of generic definitions, services, and functional units. (...) Draft new Recommendation X.746 (Corrigendum 1): Systems Management: Scheduling Function (Corrigendum 1) Location: COM4-59 Summary: This Corrigendum corrects some texts in Recommendation X.746 which defines the scheduling function which is a systems management function.
Language:English
Score: 1069335.2 - https://www.itu.int/itudoc/itu-t/com4/circ/108_ww7.doc
Data Source: un
Given that the communication distance between the ID tag reading function and the ID tag is usually very short (i.e., within a few metres), and given that end-user functions containing the ID tag reading function usually have more intelligence, the track information DB stores the location information of the ID tag reading function as the location of ID tag. When a given ID tag reading function in the end-user functions identifies a new ID tag, the end-user functions send location information and the identifier of the ID tag to the track information DB. 2) Usage traceability The operation of writing/reading (to) ID tag(s), and the handling of identifier(s) stored in ID tag(s) are performed by the end-user functions. (...) The location information can be the location information of the ID reader or more globally of the end-user functions. (4) As a result, the track information DB provides a confirmation notification.
Language:English
Score: 1065578.7 - https://www.itu.int/wftp3/Publ.../files/basic-html/page637.html
Data Source: un
Draft Revised Recommendation X.746: Scheduling Function. Location: COM 4-R 44 Summary: This Recommendation defines the scheduling function. (...) Location: COM 4-R 44 Summary: The Recommendation X.746 (03/2000) defines the scheduling function. (...) Draft new Recommendation X.754: Enhanced Event Control Function. Location: COM 4- Summary: This Recommendation presents enhancement event control functions to handle the unavailability of the logging systems.
Language:English
Score: 1062396.6 - https://www.itu.int/itudoc/itu-t/circ/circ5/229_ww9.doc
Data Source: un
Draft Revised Recommendation X.746: Scheduling Function. Location: COM 4-R 44 Summary: This Recommendation defines the scheduling function. (...) Location: COM 4-R 44 Summary: The Recommendation X.746 (03/2000) defines the scheduling function. (...) Draft new Recommendation X.754: Enhanced Event Control Function. Location: COM 4- Summary: This Recommendation presents enhancement event control functions to handle the unavailability of the logging systems.
Language:English
Score: 1062396.6 - https://www.itu.int/itudoc/itu-t/com4/circ/229_ww9.doc
Data Source: un
In any case, exchanges of data occur between these entities. 1.1 The Home Location Function (HLF) This functional entity is a data base in charge of the management of mobile subscribers. (...) However, it seems safer to store all subscription parameters in the HLF even when some are stored in a subscriber or User Identity Module. 1.2 The Visitor Location Function (VLF) A H.323 mobile terminal roaming in an Gatekeeper/Gateway area is controlled by the Visitor Location function in charge of this area. When a H.323 Mobile Terminal (MT) enters a new location area it starts a registration procedure. The Gatekeeper/Gateway in charge of that area notices this registration and transfers to the Visitor Location Function the identity of the location area where the H.323 MT is situated.
Language:English
Score: 1061935.4 - https://www.itu.int/wftp3/av-a...bilityDefn_Geneva_02072000.doc
Data Source: un
As defined in [ITU-T Q.1707], MMCF is composed of two sub-functions, LMF and HCF for location management function and handover control function, respectively. (...) The definition of those mobility node functions makes it easier to explain forwarding plane procedures in mobility functional scenarios. 6.4 Functional entities The functional entities required for support of mobility in the control plane of the transport stratum are: • mobile location management functional entity (MLM-FE); • handover decision and control functional entity (HDC-FE); • network information distribution functional entity (NID-FE); • network information repository functional entity (NIR-FE). (...) These functional entities and functions are described in the following clauses. 6.4.1 Mobile location management functional entity (MLM-FE) The mobile location management functional entity (MLM-FE) has the following responsibilities: • in the case of network-based mobility, initiating location registration on behalf of the UE; 470     475     476     477     478     479     480     481     482     483     484     485          
Language:English
Score: 1058257.9 - https://www.itu.int/en/publica.../files/basic-html/page480.html
Data Source: un
Page 557 - 2015 Security in Telecommunications and Information Technology           Basic HTML Version Table of Contents View Full Version Page 557 - 2015 Security in Telecommunications and Information Technology P. 557 Unleashing the potential of the Internet of Things 5 7.2 Transport control functional entities 7.2.1 T-10: Network access configuration functional entity (NAC-FE) • Connectivity requirement: The NAC-FE provides connectivity to IP-based and non-IP based sensor networks through gateways. 7.2.2 T-11: Transport authentication and authorization functional entity (TAA-FE) • Identification, authentication and authorization: The TAA-FE provides authentication of the USN end-users and authorization of network access. 7.2.3 T-12: Transport user profile functional entity (TUP-FE) • Identification, authentication and authorization: The TAA-FE provides authentication of the USN end-users and authorization of network access. 7.2.4 T-13: Transport location management functional entity (TLM-FE) • Location management requirement: The TLM-FE provides location management capability at the IP layer. If a sensor network uses IP addresses directly or a USN gateway provides IP-based connectivity, the location information management of sensor networks at the IP layer is supported by the TLM-FE. 7.2.5 T-17: Transport resource control functional entity (TRC-FE) • Differentiated QoS and data prioritization requirement: The TRC-FE provides different QoS and also supports data prioritization capabilities. 7.2.6 T-18: Mobile location management functional entity (MLM-FE) • Mobility requirement: The MLM-FE provides functions for the support of IP-based mobility of a sensor network as well as a sensor node. 7.3 Service control functional entities 7.3.1 S-5: Service user profile functional entity (SUP-FE) • Identification, authentication and authorization: The SUP-FE is responsible for storing user profiles, subscriber-related location data and presence status data in the service stratum. A user profile is required to be provided in support of authentication, authorization and so on. 7.3.2 S-6: Service authentication and authorization functional entity (SAA-FE) • Identification, authentication and authorization: The SAA-FE provides authentication and authorization in the service stratum.
Language:English
Score: 1058193.6 - https://www.itu.int/wftp3/Publ.../files/basic-html/page557.html
Data Source: un
Page 557 - Unleashing the potenti al of the Internet of Things           Basic HTML Version Table of Contents View Full Version Page 557 - Unleashing the potenti al of the Internet of Things P. 557 Unleashing the potential of the Internet of Things 5 7.2 Transport control functional entities 7.2.1 T-10: Network access configuration functional entity (NAC-FE) • Connectivity requirement: The NAC-FE provides connectivity to IP-based and non-IP based sensor networks through gateways. 7.2.2 T-11: Transport authentication and authorization functional entity (TAA-FE) • Identification, authentication and authorization: The TAA-FE provides authentication of the USN end-users and authorization of network access. 7.2.3 T-12: Transport user profile functional entity (TUP-FE) • Identification, authentication and authorization: The TAA-FE provides authentication of the USN end-users and authorization of network access. 7.2.4 T-13: Transport location management functional entity (TLM-FE) • Location management requirement: The TLM-FE provides location management capability at the IP layer. If a sensor network uses IP addresses directly or a USN gateway provides IP-based connectivity, the location information management of sensor networks at the IP layer is supported by the TLM-FE. 7.2.5 T-17: Transport resource control functional entity (TRC-FE) • Differentiated QoS and data prioritization requirement: The TRC-FE provides different QoS and also supports data prioritization capabilities. 7.2.6 T-18: Mobile location management functional entity (MLM-FE) • Mobility requirement: The MLM-FE provides functions for the support of IP-based mobility of a sensor network as well as a sensor node. 7.3 Service control functional entities 7.3.1 S-5: Service user profile functional entity (SUP-FE) • Identification, authentication and authorization: The SUP-FE is responsible for storing user profiles, subscriber-related location data and presence status data in the service stratum. A user profile is required to be provided in support of authentication, authorization and so on. 7.3.2 S-6: Service authentication and authorization functional entity (SAA-FE) • Identification, authentication and authorization: The SAA-FE provides authentication and authorization in the service stratum.
Language:English
Score: 1058193.6 - https://www.itu.int/en/publica.../files/basic-html/page557.html
Data Source: un
Draft new Recommendation X.737 (Corrigendum 1): System management: confidence and diagnostic test categories (Corrigendum 1) Location: COM4-51 18. Draft new Recommendation X.738 (Corrigendum 1): Systems Management: summarization function (Corrigendum 1) Location: COM4-52 19. (...) Draft new Recommendation X.743: Open Systems Interconnection - Systems Management - Part 20: Time Management Function Location: COM4-66 24. Draft new Recommendation X.744 (Corrigendum 1): Systems Management: Software Management Function Location: COM4-57 25. Draft new Recommendation X.745 (Corrigendum 2): Systems Management: Test Management Function (Corrigendum 2) Location: COM4-58 26. Draft new Recommendation X.746 (Corrigendum 1): Systems Management: Scheduling Function (Corrigendum 1) Location: COM4-59 27.
Language:English
Score: 1055954.7 - https://www.itu.int/itudoc/itu-t/com4/circ/132_ww7.doc
Data Source: un