Upload 2 files
Browse files
test.tsv
CHANGED
|
@@ -1,74 +1,74 @@
|
|
| 1 |
-
ID Sentence Detected as
|
| 2 |
-
1 diagnostic#01 The absolute time of input will be associated with each sensed data item for <referential>its</referential> complete lifecycle, including permanent storage. NOCUOUS
|
| 3 |
-
2 diagnostic#02 Each sensed data item will be qualified as to <referential>its</referential> certitude during the acquisition process. INNOCUOUS
|
| 4 |
-
3 diagnostic#03 Sensed data input to the tool shall be validated with respect to <referential>its</referential> expected range of values. INNOCUOUS
|
| 5 |
-
4 diagnostic#04 The faults identified and <referential>their</referential> causes and sources, shall be saved to permanent storage for subsequent analysis. INNOCUOUS
|
| 6 |
-
5 diagnostic#05 The tool shall monitor the unit under diagnosis, either in real time or batch mode, for an indefinite period of time or until input data are no longer available, and log diagnostic results as <referential>they</referential> are determined. NOCUOUS
|
| 7 |
-
6 diagnostic#06 Selecting the “Configure Diagnostics” menu item of the main menu entitled “File” shall display the configuration window, making <referential>it</referential> the current window, modal to the main window. NOCUOUS
|
| 8 |
-
7 diagnostic#07 Entering a file name shall cause the permanent storage of the modified parameters and <referential>their</referential> immediate use by the diagnostic operations after confirmatory responses by the user. INNOCUOUS
|
| 9 |
-
8 diagnostic#08 If the user does not confirm the request to save, <referential>it</referential> will not be performed. INNOCUOUS
|
| 10 |
-
9 diagnostic#09 If the user does not confirm the request to relay the modified parameters to the diagnostic processing immediately, <referential>it</referential> will not be performed. NOCUOUS
|
| 11 |
-
10 diagnostic#10 The subsystems window, condition window, and diagnostic information window shall display a title that indicates <referential>its</referential> specific location or absolute path in the navigation hierarchy of windows. NOCUOUS
|
| 12 |
-
11 diagnostic#11 This set(s) of indicators shall summarize diagnostic indicators not currently appearing on the list above (below) <referential>it</referential>. NOCUOUS
|
| 13 |
-
12 diagnostic#12 An indicator in the summary set shall be active if any similar indicator not appearing above (or below) <referential>it</referential> is active. NOCUOUS
|
| 14 |
-
13 diagnostic#13 The third window in the hierarchy is the subsystems window and <referential>it</referential> can only be displayed by a user selection on the main window. INNOCUOUS
|
| 15 |
-
14 diagnostic#14 The fourth window in the hierarchy is the condition window and <referential>it</referential> can only be displayed by a user selection on the subsystems window. INNOCUOUS
|
| 16 |
-
15 diagnostic#15 This window can only be displayed by a user selection on the condition window or by a user selection on the diagnostic history window if <referential>it</referential> is displayed. NOCUOUS
|
| 17 |
-
16 library#26-0 In addition, some publishers may only allow <referential>their</referential> material to be served up through NLM’s system at a certain interval after its publication. INNOCUOUS
|
| 18 |
-
17 library#26-1 In addition, some publishers may only allow their material to be served up through NLM’s system at a certain interval after <referential>its</referential> publication. NOCUOUS
|
| 19 |
-
18 library#27 The Archival Information Update function in Administration also submits dissemination requests to obtain DIPs needed to perform <referential>its</referential> update functions. NOCUOUS
|
| 20 |
-
19 library#28 During the development of the functional requirements for the NLM Digital Repository, <referential>it</referential> has become apparent that NLM will have several repositories – LocatorPlus, PubMed Central (covering journals), and the digital repository currently under investigation. NOCUOUS
|
| 21 |
-
20 library#29 <referential>It</referential> is possible that the initial NLM Repository may be composed of more than one electronic storage facility, especially in the early development of the repository. NOCUOUS
|
| 22 |
-
21 library#30 The NLM System Administration/Programming Access: Provides an NLM Administrative/Programming Level, ultimate rights to the system, required for <referential>its</referential> management, development, and for assigning appropriate rights to users. NOCUOUS
|
| 23 |
-
22 library#31 Access rights and conditions to materials and the directories/folders in which <referential>they</referential> are kept must provide for one or more of the following basic privileges, either alone or in combination:• Create/Write access• Edit access• Read access• Delete access. NOCUOUS
|
| 24 |
-
23 library#32 Both an object and <referential>its</referential> related metadata may be embargoed in terms of public access. INNOCUOUS
|
| 25 |
-
24 library#33 Access rights and conditions of use will be held for each digital object and <referential>its</referential> related metadata. INNOCUOUS
|
| 26 |
-
25 library#34 System must have the ability to search and display metadata, preferably in a user-conformable, human readable display as well as in <referential>its</referential> native format for machine harvesting and manipulation. NOCUOUS
|
| 27 |
-
26 weather#21 The Clarus program shall maintain information about requestors and <referential>their</referential> access to data and information. INNOCUOUS
|
| 28 |
-
27 weather#22 The Clarus program shall operate the Clarus system according to <referential>its</referential> published IT Security Plan. NOCUOUS
|
| 29 |
-
28 weather#23 The QChS shall be able to use historical environmental data in <referential>their</referential> quality checking algorithms. NOCUOUS
|
| 30 |
-
29 weather#24 The QChS shall be implemented to quality check new observation types as <referential>they</referential> become available. NOCUOUS
|
| 31 |
-
30 weather#25 The Clarus system shall process data as <referential>they</referential> are received. INNOCUOUS
|
| 32 |
-
31 weather#26 The QChS shall apply quality flags to data as <referential>they</referential> are received. NOCUOUS
|
| 33 |
-
32 weather#27 The SS shall record when <referential>it</referential> initiates actions. INNOCUOUS
|
| 34 |
-
33 weather#28 The Clarus system shall be able to publish environmental data at three times the volume rate that <referential>it</referential> collects it. NOCUOUS
|
| 35 |
-
34 archive#01 <referential>It</referential> shall be possible to request that automatically generated migration metadata be stored in the converted iles (e.g., OS/Kernel type, original ARC name, ARC size, ARC digests, conversion timestamp, ARC record offset, ...). INNOCUOUS
|
| 36 |
-
35 archive#02-0 The IIPC members should provide <referential>us</referential> with the default METADATA they want to be included for migration. NOCUOUS
|
| 37 |
-
36 archive#02-1 The IIPC members should provide us with the default METADATA <referential>they</referential> want to be included for migration. INNOCUOUS
|
| 38 |
-
37 archive#03 Software checkpoints (such as start-trans, end-trans) may be added during processing for managing atomic transactions (e.g., operations on a ile, these must start and complete to be accepted in the migration), except where operating system limitations would prohibit <referential>it</referential>. NOCUOUS
|
| 39 |
-
38 archive#04 <referential>It</referential> shall be possible to perform a “dry-run migration”. INNOCUOUS
|
| 40 |
-
39 archive#05 To validate that the migration succeeded, arc_warc_verify will use the METADATA included in the newly generated WARC iles to match records with <referential>their</referential> corresponding ARC iles (see FR4, and FR5). NOCUOUS
|
| 41 |
-
40 archive#06 Enhance the WARC browser to display aggregated WARCs summaries in <referential>its</referential> UI. INNOCUOUS
|
| 42 |
-
41 archive#07 Enhance the WARC browser to display a manifest of WARC iles and <referential>their</referential> locations. INNOCUOUS
|
| 43 |
-
42 railway#63 As a train approaches the limits of the coverage of the PLMN <referential>it</referential> is registered with, <referential>it</referential> will be necessary for <referential>it</referential> to register with the next PLMN providing coverage. NOCUOUS
|
| 44 |
-
43 railway#64 Each type of equipment has slightly different requirements placed upon <referential>it</referential> in terms of EMC and climate. INNOCUOUS
|
| 45 |
-
44 railway#65 Where other data interfaces are implemented, <referential>they</referential> should be of the RS422 standard. INNOCUOUS
|
| 46 |
-
45 railway#66 Upon switch on, once the radio is connected to a mobile network, <referential>it</referential> shall be able to receive all calls made using the MSISDN or appropriate group call number. NOCUOUS
|
| 47 |
-
46 railway#67 In addition, the Operational radio is specified to allow <referential>its</referential> use in the operating environment experienced on the operational railway (eg shunting and maintenance), with the specifications in this section taking priority over those in section 4 where any discrepancy is identified. INNOCUOUS
|
| 48 |
-
47 railway#68 The SIM cards shall be fixed into the radio such that <referential>they</referential> can only be removed by the use of a tool. INNOCUOUS
|
| 49 |
-
48 railway#69 A group call controller who wishes to start talking (except in the case of an originator, a joiner or a re-joiner speaking for the first time5) shall indicate <referential>his</referential> wish, for example by pressing the PTT button, whereupon the 3-digit DTMF sequence “###” shall be transferred. NOCUOUS
|
| 50 |
-
49 railway#70 The terminal of the controller should receive a single DTMF grant tone “#” of duration 100ms 5ms sent by the network if <referential>it</referential> has detected the 3-digit DTMF sequence “###” and if the controller was not previously talking. NOCUOUS
|
| 51 |
-
50 railway#71 Any group call controller who wishes to stop talking shall indicate <referential>his</referential> wish, for example by releasing the PTT button, whereupon the 3-digit DTMF sequence “#**” shall be transferred. INNOCUOUS
|
| 52 |
-
51 railway#72 All Train Function Numbers and <referential>their</referential> associated MSISDN numbers shall be stored in the same routing database, which is the database of the GSM-R network in which the train is currently operating. INNOCUOUS
|
| 53 |
-
52 railway#73 If functional numbers are to be used outside the EIRENE network, <referential>they</referential> will require either a public number allocation or, alternatively, an EIRENE Network Access Number (ENAN) may be used as described in 9.11 9.3.3 Each national railway should obtain a public numbering allocation for MSISDN numbers from the relevant regulatory bodies. INNOCUOUS
|
| 54 |
-
53 railway#74-0 <referential>It</referential> is the responsibility of each individual GSM-R operator to acquire a public domain NDC from their national telecommunications regulator. NOCUOUS
|
| 55 |
-
54 railway#74-1 It is the responsibility of each individual GSM-R operator to acquire a public domain NDC from <referential>their</referential> national telecommunications regulator. INNOCUOUS
|
| 56 |
-
55 railway#75 Mobiles shall be capable of operation using algorithms for all countries in which <referential>they</referential> need to roam. NOCUOUS
|
| 57 |
-
56 railway#76 Functional numbering provides the mechanism by which a mobile terminal, or an item of equipment connected to a mobile terminal, can be addressed by a number identifying the function for which <referential>it</referential> is being used. NOCUOUS
|
| 58 |
-
57 railway#77 For international Railway emergency calls, in order to minimise call set-up times, <referential>it</referential> is recommended that the anchor MSC always directly controls the cell where the Railway emergency call was originated. NOCUOUS
|
| 59 |
-
58 railway#78 Each mobile shall store a list of emergency Group IDs in the SIM appropriate to <referential>its</referential> function (the Cab radio will store Group ID 299 and 599 - see table 9-8). NOCUOUS
|
| 60 |
-
59 railway#79 For post-incident analysis <referential>it</referential> is important that the initiation and receipt of Railway emergency calls by mobiles is confirmed by a message sent to a ground-based location (and also registered in the train borne recorder, in cases where a train borne recorder is connected to the Cab radio). NOCUOUS
|
| 61 |
-
60 railway#80 The common shunting group provides a point of contact for leaders and team members to set up a dedicated shunting group call for <referential>their</referential> shunting operation. NOCUOUS
|
| 62 |
-
61 railway#81 The terminal application shall prevent members of a dedicated shunting team from initiating a new call (unless <referential>they</referential> are registered as shunting team leader and have left shunting mode using the “maintain group call” function described in 14.2.4). INNOCUOUS
|
| 63 |
-
62 railway#82 Users shall be prevented from joining a dedicated shunting group by the EIRENE terminal application unless a valid functional number for the group has been successfully registered to the GSM-R network by <referential>their</referential> terminal. INNOCUOUS
|
| 64 |
-
63 railway#83 If an ETCS equipped train passes a level transition to one or more levels for which <referential>it</referential> is not equipped, ETCS shall initiate a brake application. INNOCUOUS
|
| 65 |
-
64 space#21 When memory alignment is permitted, Redundancy Management attempts to reintegrate a processor with the other members of <referential>its</referential> original FCP virtual group by commanding the affected FCP virtual group to perform re-synchronization operations. NOCUOUS
|
| 66 |
-
65 space#22 Network Element FTSS CSCIIBNF time-out Indicates that the members of the destination virtual group corresponding to the set bits did not free enough space in <referential>their</referential> input buffers to hold the incoming packet within the allowable time skew. NOCUOUS
|
| 67 |
-
66 space#23 The FTSS shall provide an API call to allow the ICP application to determine on which channel <referential>it</referential> resides. NOCUOUS
|
| 68 |
-
67 space#24 The FTPP shall recover from a babbling NE or ICP within 40 milliseconds after <referential>it</referential> is detected. NOCUOUS
|
| 69 |
-
68 space#25 <referential>It</referential> shall be possible to modify the CT whenever any of this information is changed by using a CT update primitive in a synchronous and atomic manner. INNOCUOUS
|
| 70 |
-
69 space#26 When a majority, but not a unanimity, of FCP members are observed with packets in <referential>their</referential> output buffers, a time-out shall (3.2.2.6.7) be initiated. NOCUOUS
|
| 71 |
-
70 space#27 When the timestamp counter reaches the maximum value (Hex FFFFFFFF or approximately 5500 seconds), <referential>it</referential> shall (3.2.2.7.6) wrap around to zero. INNOCUOUS
|
| 72 |
-
71 space#28 The Start-Up shall synchronize <referential>its</referential> FCP with other operational FCPs. INNOCUOUS
|
| 73 |
-
72 space#29 The Scheduler shall detect 50 Hz, 10 Hz, and 1 Hz frame overruns at the next frame following the end of <referential>their</referential> respective rate boundaries. NOCUOUS
|
| 74 |
-
73 space#30 The FTSS shall wait for the ICP to signal that <referential>it</referential> has completed initialization before suspending the application for memory re-alignment. NOCUOUS
|
|
|
|
| 1 |
+
ID Sentence Detected as
|
| 2 |
+
1 diagnostic#01 The absolute time of input will be associated with each sensed data item for <referential>its</referential> complete lifecycle, including permanent storage. NOCUOUS
|
| 3 |
+
2 diagnostic#02 Each sensed data item will be qualified as to <referential>its</referential> certitude during the acquisition process. INNOCUOUS
|
| 4 |
+
3 diagnostic#03 Sensed data input to the tool shall be validated with respect to <referential>its</referential> expected range of values. INNOCUOUS
|
| 5 |
+
4 diagnostic#04 The faults identified and <referential>their</referential> causes and sources, shall be saved to permanent storage for subsequent analysis. INNOCUOUS
|
| 6 |
+
5 diagnostic#05 The tool shall monitor the unit under diagnosis, either in real time or batch mode, for an indefinite period of time or until input data are no longer available, and log diagnostic results as <referential>they</referential> are determined. NOCUOUS
|
| 7 |
+
6 diagnostic#06 Selecting the “Configure Diagnostics” menu item of the main menu entitled “File” shall display the configuration window, making <referential>it</referential> the current window, modal to the main window. NOCUOUS
|
| 8 |
+
7 diagnostic#07 Entering a file name shall cause the permanent storage of the modified parameters and <referential>their</referential> immediate use by the diagnostic operations after confirmatory responses by the user. INNOCUOUS
|
| 9 |
+
8 diagnostic#08 If the user does not confirm the request to save, <referential>it</referential> will not be performed. INNOCUOUS
|
| 10 |
+
9 diagnostic#09 If the user does not confirm the request to relay the modified parameters to the diagnostic processing immediately, <referential>it</referential> will not be performed. NOCUOUS
|
| 11 |
+
10 diagnostic#10 The subsystems window, condition window, and diagnostic information window shall display a title that indicates <referential>its</referential> specific location or absolute path in the navigation hierarchy of windows. NOCUOUS
|
| 12 |
+
11 diagnostic#11 This set(s) of indicators shall summarize diagnostic indicators not currently appearing on the list above (below) <referential>it</referential>. NOCUOUS
|
| 13 |
+
12 diagnostic#12 An indicator in the summary set shall be active if any similar indicator not appearing above (or below) <referential>it</referential> is active. NOCUOUS
|
| 14 |
+
13 diagnostic#13 The third window in the hierarchy is the subsystems window and <referential>it</referential> can only be displayed by a user selection on the main window. INNOCUOUS
|
| 15 |
+
14 diagnostic#14 The fourth window in the hierarchy is the condition window and <referential>it</referential> can only be displayed by a user selection on the subsystems window. INNOCUOUS
|
| 16 |
+
15 diagnostic#15 This window can only be displayed by a user selection on the condition window or by a user selection on the diagnostic history window if <referential>it</referential> is displayed. NOCUOUS
|
| 17 |
+
16 library#26-0 In addition, some publishers may only allow <referential>their</referential> material to be served up through NLM’s system at a certain interval after its publication. INNOCUOUS
|
| 18 |
+
17 library#26-1 In addition, some publishers may only allow their material to be served up through NLM’s system at a certain interval after <referential>its</referential> publication. NOCUOUS
|
| 19 |
+
18 library#27 The Archival Information Update function in Administration also submits dissemination requests to obtain DIPs needed to perform <referential>its</referential> update functions. NOCUOUS
|
| 20 |
+
19 library#28 During the development of the functional requirements for the NLM Digital Repository, <referential>it</referential> has become apparent that NLM will have several repositories – LocatorPlus, PubMed Central (covering journals), and the digital repository currently under investigation. NOCUOUS
|
| 21 |
+
20 library#29 <referential>It</referential> is possible that the initial NLM Repository may be composed of more than one electronic storage facility, especially in the early development of the repository. NOCUOUS
|
| 22 |
+
21 library#30 The NLM System Administration/Programming Access: Provides an NLM Administrative/Programming Level, ultimate rights to the system, required for <referential>its</referential> management, development, and for assigning appropriate rights to users. NOCUOUS
|
| 23 |
+
22 library#31 Access rights and conditions to materials and the directories/folders in which <referential>they</referential> are kept must provide for one or more of the following basic privileges, either alone or in combination:• Create/Write access• Edit access• Read access• Delete access. NOCUOUS
|
| 24 |
+
23 library#32 Both an object and <referential>its</referential> related metadata may be embargoed in terms of public access. INNOCUOUS
|
| 25 |
+
24 library#33 Access rights and conditions of use will be held for each digital object and <referential>its</referential> related metadata. INNOCUOUS
|
| 26 |
+
25 library#34 System must have the ability to search and display metadata, preferably in a user-conformable, human readable display as well as in <referential>its</referential> native format for machine harvesting and manipulation. NOCUOUS
|
| 27 |
+
26 weather#21 The Clarus program shall maintain information about requestors and <referential>their</referential> access to data and information. INNOCUOUS
|
| 28 |
+
27 weather#22 The Clarus program shall operate the Clarus system according to <referential>its</referential> published IT Security Plan. NOCUOUS
|
| 29 |
+
28 weather#23 The QChS shall be able to use historical environmental data in <referential>their</referential> quality checking algorithms. NOCUOUS
|
| 30 |
+
29 weather#24 The QChS shall be implemented to quality check new observation types as <referential>they</referential> become available. NOCUOUS
|
| 31 |
+
30 weather#25 The Clarus system shall process data as <referential>they</referential> are received. INNOCUOUS
|
| 32 |
+
31 weather#26 The QChS shall apply quality flags to data as <referential>they</referential> are received. NOCUOUS
|
| 33 |
+
32 weather#27 The SS shall record when <referential>it</referential> initiates actions. INNOCUOUS
|
| 34 |
+
33 weather#28 The Clarus system shall be able to publish environmental data at three times the volume rate that <referential>it</referential> collects it. NOCUOUS
|
| 35 |
+
34 archive#01 <referential>It</referential> shall be possible to request that automatically generated migration metadata be stored in the converted iles (e.g., OS/Kernel type, original ARC name, ARC size, ARC digests, conversion timestamp, ARC record offset, ...). INNOCUOUS
|
| 36 |
+
35 archive#02-0 The IIPC members should provide <referential>us</referential> with the default METADATA they want to be included for migration. NOCUOUS
|
| 37 |
+
36 archive#02-1 The IIPC members should provide us with the default METADATA <referential>they</referential> want to be included for migration. INNOCUOUS
|
| 38 |
+
37 archive#03 Software checkpoints (such as start-trans, end-trans) may be added during processing for managing atomic transactions (e.g., operations on a ile, these must start and complete to be accepted in the migration), except where operating system limitations would prohibit <referential>it</referential>. NOCUOUS
|
| 39 |
+
38 archive#04 <referential>It</referential> shall be possible to perform a “dry-run migration”. INNOCUOUS
|
| 40 |
+
39 archive#05 To validate that the migration succeeded, arc_warc_verify will use the METADATA included in the newly generated WARC iles to match records with <referential>their</referential> corresponding ARC iles (see FR4, and FR5). NOCUOUS
|
| 41 |
+
40 archive#06 Enhance the WARC browser to display aggregated WARCs summaries in <referential>its</referential> UI. INNOCUOUS
|
| 42 |
+
41 archive#07 Enhance the WARC browser to display a manifest of WARC iles and <referential>their</referential> locations. INNOCUOUS
|
| 43 |
+
42 railway#63 As a train approaches the limits of the coverage of the PLMN <referential>it</referential> is registered with, <referential>it</referential> will be necessary for <referential>it</referential> to register with the next PLMN providing coverage. NOCUOUS
|
| 44 |
+
43 railway#64 Each type of equipment has slightly different requirements placed upon <referential>it</referential> in terms of EMC and climate. INNOCUOUS
|
| 45 |
+
44 railway#65 Where other data interfaces are implemented, <referential>they</referential> should be of the RS422 standard. INNOCUOUS
|
| 46 |
+
45 railway#66 Upon switch on, once the radio is connected to a mobile network, <referential>it</referential> shall be able to receive all calls made using the MSISDN or appropriate group call number. NOCUOUS
|
| 47 |
+
46 railway#67 In addition, the Operational radio is specified to allow <referential>its</referential> use in the operating environment experienced on the operational railway (eg shunting and maintenance), with the specifications in this section taking priority over those in section 4 where any discrepancy is identified. INNOCUOUS
|
| 48 |
+
47 railway#68 The SIM cards shall be fixed into the radio such that <referential>they</referential> can only be removed by the use of a tool. INNOCUOUS
|
| 49 |
+
48 railway#69 A group call controller who wishes to start talking (except in the case of an originator, a joiner or a re-joiner speaking for the first time5) shall indicate <referential>his</referential> wish, for example by pressing the PTT button, whereupon the 3-digit DTMF sequence “###” shall be transferred. NOCUOUS
|
| 50 |
+
49 railway#70 The terminal of the controller should receive a single DTMF grant tone “#” of duration 100ms 5ms sent by the network if <referential>it</referential> has detected the 3-digit DTMF sequence “###” and if the controller was not previously talking. NOCUOUS
|
| 51 |
+
50 railway#71 Any group call controller who wishes to stop talking shall indicate <referential>his</referential> wish, for example by releasing the PTT button, whereupon the 3-digit DTMF sequence “#**” shall be transferred. INNOCUOUS
|
| 52 |
+
51 railway#72 All Train Function Numbers and <referential>their</referential> associated MSISDN numbers shall be stored in the same routing database, which is the database of the GSM-R network in which the train is currently operating. INNOCUOUS
|
| 53 |
+
52 railway#73 If functional numbers are to be used outside the EIRENE network, <referential>they</referential> will require either a public number allocation or, alternatively, an EIRENE Network Access Number (ENAN) may be used as described in 9.11 9.3.3 Each national railway should obtain a public numbering allocation for MSISDN numbers from the relevant regulatory bodies. INNOCUOUS
|
| 54 |
+
53 railway#74-0 <referential>It</referential> is the responsibility of each individual GSM-R operator to acquire a public domain NDC from their national telecommunications regulator. NOCUOUS
|
| 55 |
+
54 railway#74-1 It is the responsibility of each individual GSM-R operator to acquire a public domain NDC from <referential>their</referential> national telecommunications regulator. INNOCUOUS
|
| 56 |
+
55 railway#75 Mobiles shall be capable of operation using algorithms for all countries in which <referential>they</referential> need to roam. NOCUOUS
|
| 57 |
+
56 railway#76 Functional numbering provides the mechanism by which a mobile terminal, or an item of equipment connected to a mobile terminal, can be addressed by a number identifying the function for which <referential>it</referential> is being used. NOCUOUS
|
| 58 |
+
57 railway#77 For international Railway emergency calls, in order to minimise call set-up times, <referential>it</referential> is recommended that the anchor MSC always directly controls the cell where the Railway emergency call was originated. NOCUOUS
|
| 59 |
+
58 railway#78 Each mobile shall store a list of emergency Group IDs in the SIM appropriate to <referential>its</referential> function (the Cab radio will store Group ID 299 and 599 - see table 9-8). NOCUOUS
|
| 60 |
+
59 railway#79 For post-incident analysis <referential>it</referential> is important that the initiation and receipt of Railway emergency calls by mobiles is confirmed by a message sent to a ground-based location (and also registered in the train borne recorder, in cases where a train borne recorder is connected to the Cab radio). NOCUOUS
|
| 61 |
+
60 railway#80 The common shunting group provides a point of contact for leaders and team members to set up a dedicated shunting group call for <referential>their</referential> shunting operation. NOCUOUS
|
| 62 |
+
61 railway#81 The terminal application shall prevent members of a dedicated shunting team from initiating a new call (unless <referential>they</referential> are registered as shunting team leader and have left shunting mode using the “maintain group call” function described in 14.2.4). INNOCUOUS
|
| 63 |
+
62 railway#82 Users shall be prevented from joining a dedicated shunting group by the EIRENE terminal application unless a valid functional number for the group has been successfully registered to the GSM-R network by <referential>their</referential> terminal. INNOCUOUS
|
| 64 |
+
63 railway#83 If an ETCS equipped train passes a level transition to one or more levels for which <referential>it</referential> is not equipped, ETCS shall initiate a brake application. INNOCUOUS
|
| 65 |
+
64 space#21 When memory alignment is permitted, Redundancy Management attempts to reintegrate a processor with the other members of <referential>its</referential> original FCP virtual group by commanding the affected FCP virtual group to perform re-synchronization operations. NOCUOUS
|
| 66 |
+
65 space#22 Network Element FTSS CSCIIBNF time-out Indicates that the members of the destination virtual group corresponding to the set bits did not free enough space in <referential>their</referential> input buffers to hold the incoming packet within the allowable time skew. NOCUOUS
|
| 67 |
+
66 space#23 The FTSS shall provide an API call to allow the ICP application to determine on which channel <referential>it</referential> resides. NOCUOUS
|
| 68 |
+
67 space#24 The FTPP shall recover from a babbling NE or ICP within 40 milliseconds after <referential>it</referential> is detected. NOCUOUS
|
| 69 |
+
68 space#25 <referential>It</referential> shall be possible to modify the CT whenever any of this information is changed by using a CT update primitive in a synchronous and atomic manner. INNOCUOUS
|
| 70 |
+
69 space#26 When a majority, but not a unanimity, of FCP members are observed with packets in <referential>their</referential> output buffers, a time-out shall (3.2.2.6.7) be initiated. NOCUOUS
|
| 71 |
+
70 space#27 When the timestamp counter reaches the maximum value (Hex FFFFFFFF or approximately 5500 seconds), <referential>it</referential> shall (3.2.2.7.6) wrap around to zero. INNOCUOUS
|
| 72 |
+
71 space#28 The Start-Up shall synchronize <referential>its</referential> FCP with other operational FCPs. INNOCUOUS
|
| 73 |
+
72 space#29 The Scheduler shall detect 50 Hz, 10 Hz, and 1 Hz frame overruns at the next frame following the end of <referential>their</referential> respective rate boundaries. NOCUOUS
|
| 74 |
+
73 space#30 The FTSS shall wait for the ICP to signal that <referential>it</referential> has completed initialization before suspending the application for memory re-alignment. NOCUOUS
|
train.tsv
ADDED
|
@@ -0,0 +1,140 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
ID Sentence Detected as
|
| 2 |
+
1 library#01 All material that is stored in the repository will enter <referential>it</referential> via the Ingest function. NOCUOUS
|
| 3 |
+
2 library#02-1 The Library may want to accept important digital materials in non-standard formats in case <referential>we</referential> are able to migrate them to a more usable format in the future. NOCUOUS
|
| 4 |
+
3 library#02-2 The Library may want to accept important digital materials in non-standard formats in case we are able to migrate <referential>them</referential> to a more usable format in the future. INNOCUOUS
|
| 5 |
+
4 library#03 Once material has arrived, <referential>it</referential> must undergo several reviews, including virus checking, format compliance and anticipated content and file type. INNOCUOUS
|
| 6 |
+
5 library#04 Allows resources to be reviewed before a decision is made whether <referential>they</referential> should be retained. INNOCUOUS
|
| 7 |
+
6 library#05 Allows metadata to be stored in a database in a manner that conforms to repository reformatting and linked to <referential>their</referential> corresponding objects via an identifier. INNOCUOUS
|
| 8 |
+
7 library#06 The Coordinate Updates function also incorporates the storage identification information into the Descriptive Information for the AIP and transfers <referential>it</referential> to the Data Management entity along with a database update request. NOCUOUS
|
| 9 |
+
8 library#07 Archival Storage functions include receiving AIPs from Ingest and adding <referential>them</referential> to permanent storage, managing the storage hierarchy, refreshing the media on which archive holdings are stored, performing routine and special error checking, providing disaster recovery capabilities, and providing AIPs to Access to fulfill orders. INNOCUOUS
|
| 10 |
+
9 library#08 <referential>It</referential> will also conform to any special levels of service required for the AIP, or any special security measures that are required, and ensures the appropriate level of protection for the AIP. NOCUOUS
|
| 11 |
+
10 library#09 <referential>It</referential> monitors error logs to ensure AIPs are not corrupted during transfers. NOCUOUS
|
| 12 |
+
11 library#10 However, the data constituting the Packaging Information may be changed as long as <referential>it</referential> continues to perform the same function and there is a straightforward implementation that does not cause information loss. NOCUOUS
|
| 13 |
+
12 library#11 The migration strategy must select a storage medium, taking into consideration the expected and actual rates of errors encountered in various media types, <referential>their</referential> performance, and <referential>their</referential> costs of ownership. INNOCUOUS
|
| 14 |
+
13 library#12 This function receives an AIP request that identifies the requested AIP(s) and provides <referential>them</referential> on the requested media type or transfers <referential>them</referential> to a staging area. INNOCUOUS
|
| 15 |
+
14 library#13 The Generate Report function receives a report request from Ingest, Access or Administration and executes any queries or other processes necessary to generate the report that <referential>it</referential> supplies to the requester. NOCUOUS
|
| 16 |
+
15 library#14 <referential>It</referential> may also receive a report request from Access and provides descriptive information for a specific AIP. NOCUOUS
|
| 17 |
+
16 library#15 Administration functions include soliciting and negotiating submission agreements with producers, auditing submissions to ensure that <referential>they</referential> meet archive standards, and maintaining configuration management of system hardware and software. NOCUOUS
|
| 18 |
+
17 library#16 Audits data in SIPs or AIPs to ensure that <referential>they</referential> meet specified requirements. NOCUOUS
|
| 19 |
+
18 library#17 The Activate Requests function maintains a record of event-driven requests and periodically compares <referential>it</referential> to the contents of the archive to determine if all needed data is available. NOCUOUS
|
| 20 |
+
19 library#18 Maintains a record of event-driven events and compares <referential>it</referential> to the contents of the repository. INNOCUOUS
|
| 21 |
+
20 library#19 The Monitor Designated Community function interacts with archive Consumers and Producers to track changes in <referential>their</referential> service requirements and available product technologies. INNOCUOUS
|
| 22 |
+
21 library#20 Interacts with repository users and content providers to track changes in <referential>their</referential> service requirements and available product technologies. NOCUOUS
|
| 23 |
+
22 library#21 This function receives reports from the Monitor Designated Communities and Monitor Technology functions, and <referential>it</referential> receives performance information, inventory reports and summarized consumer comments from Administration. INNOCUOUS
|
| 24 |
+
23 library#22 This function also receives external data standards from Monitor Technology and produces profiles of those standards that are sent to Administration as proposals on <referential>their</referential> potential usage. NOCUOUS
|
| 25 |
+
24 library#23 Produces profiles of those standards that are sent to Administration as proposals on <referential>their</referential> potential usage. NOCUOUS
|
| 26 |
+
25 library#24 The NLM will test preservation actions in order to determine <referential>their</referential> effectiveness across a range of digital objects. NOCUOUS
|
| 27 |
+
26 library#25 The NLM System Administration/Programming Access, ultimate rights to the system, required for <referential>its</referential> management, development, and for assigning appropriate rights to users. NOCUOUS
|
| 28 |
+
27 weather#01 The Clarus system shall process data as <referential>they</referential> are received. INNOCUOUS
|
| 29 |
+
28 weather#02 The Clarus system shall be able to base <referential>its</referential> quality control process on values from multiple observations. INNOCUOUS
|
| 30 |
+
29 weather#03 The Clarus system shall be able to communicate with RWIS databases through <referential>their</referential> native interfaces. INNOCUOUS
|
| 31 |
+
30 weather#04 The Clarus system shall be able to collect data from sources within 5 minutes of <referential>them</referential> becoming available. NOCUOUS
|
| 32 |
+
31 weather#05 The CAS shall be configurable to allow new observation types to be implemented as <referential>they</referential> become available. INNOCUOUS
|
| 33 |
+
32 weather#06 The CS shall collect environmental data based on <referential>its</referential> configured schedule. NOCUOUS
|
| 34 |
+
33 weather#07 The CS shall be able to dynamically adjust <referential>its</referential> retrieval schedules when environmental data is expected to be ready but is temporarily delayed. INNOCUOUS
|
| 35 |
+
34 weather#08 The CS shall process environmental data as <referential>they</referential> are received. INNOCUOUS
|
| 36 |
+
35 weather#09 The Clarus system shall be able to communicate with environmental sensor stations through <referential>its</referential> collector using the NTCIP ESS 1204. NOCUOUS
|
| 37 |
+
36 weather#10 The CS shall be able to accept data from an RWIS database in <referential>its</referential> native output format. NOCUOUS
|
| 38 |
+
37 weather#11 The Clarus system shall be able to communicate with an individual ESS through <referential>its</referential> native interface. NOCUOUS
|
| 39 |
+
38 weather#12 The DOG shall be able to monitor new environmental data services as <referential>they</referential> are added. INNOCUOUS
|
| 40 |
+
39 weather#13 The DOG shall be able to record <referential>its</referential> activities. INNOCUOUS
|
| 41 |
+
40 weather#14 The QEDC shall maintain observations and <referential>their</referential> associated quality flags for seven days. INNOCUOUS
|
| 42 |
+
41 weather#15 The QEDC shall support queries for <referential>its</referential> observations. INNOCUOUS
|
| 43 |
+
42 weather#16 The QEDS shall log <referential>their</referential> activities. NOCUOUS
|
| 44 |
+
43 weather#17 The QChS shall be able to base <referential>its</referential> quality checking process on values distributed in time. INNOCUOUS
|
| 45 |
+
44 weather#18 The contributors shall define the units of measurements of <referential>their</referential> shared data and information. INNOCUOUS
|
| 46 |
+
45 weather#19 The Clarus program shall determine how <referential>it</referential> will provide data and information to contributors. INNOCUOUS
|
| 47 |
+
46 weather#20 """The Clarus program shall inform contributors of the acceptance and use"""" of <referential>their</referential> data and information.""""""" INNOCUOUS
|
| 48 |
+
47 railway#01 The logon screen shall activate command control for the user if the user requests <referential>it</referential> and has authorization. INNOCUOUS
|
| 49 |
+
48 railway#02 When a device status has been overridden, on the screen <referential>it</referential> shall appear with different color from the normal and alarm status colors. INNOCUOUS
|
| 50 |
+
49 railway#03 <referential>It</referential> shall display and allow modification of all database tables with the exception of log tables. NOCUOUS
|
| 51 |
+
50 railway#04 The user should not be able to update log entries other than for <referential>their</referential> own login, for the current day and current shift. NOCUOUS
|
| 52 |
+
51 railway#05 Any change in device state shall be reported on the screen not later than 2 seconds from the time <referential>it</referential> occurs. INNOCUOUS
|
| 53 |
+
52 railway#06-1 When each workstation and control unit (workstation or intelligent controller at the FCU or DCU) comes online, the system shall identify <referential>it</referential> and all its associated device sensors. NOCUOUS
|
| 54 |
+
53 railway#06-2 When each workstation and control unit (workstation or intelligent controller at the FCU or DCU) comes online, the system shall identify it and all <referential>its</referential> associated device sensors. NOCUOUS
|
| 55 |
+
54 railway#07 The RLCS software shall initialize each control unit and device sensor as <referential>it</referential> is identified. NOCUOUS
|
| 56 |
+
55 railway#08 The devices can be manually controlled/operated from <referential>their</referential> cabinets (e.g.: Gates). INNOCUOUS
|
| 57 |
+
56 railway#09 The normal operating mode is Monday through Friday, between 5:00am and 8:00pm, but the system must be functional in order to stay in <referential>its</referential> closed state after hours. INNOCUOUS
|
| 58 |
+
57 railway#10 The ETCS shall provide the driver with information to allow <referential>him</referential> to drive the train safely. INNOCUOUS
|
| 59 |
+
58 railway#11-1 If the supervision is performed by a RBC <referential>it</referential> shall be possible to prevent movements of a traction unit in its area if not authorised by the RBC. NOCUOUS
|
| 60 |
+
59 railway#11-2 If the supervision is performed by a RBC it shall be possible to prevent movements of a traction unit in <referential>its</referential> area if not authorised by the RBC. NOCUOUS
|
| 61 |
+
60 railway#12 <referential>It</referential> shall be possible to implement one or more of the ETCS application levels on a line. INNOCUOUS
|
| 62 |
+
61 railway#13 The ETCS shall be compatible with existing national systems listed in the CCS TSI such that <referential>it</referential> does not interfere with the national systems and is not interfered with by the national systems. INNOCUOUS
|
| 63 |
+
62 railway#14 If an ETCS equipped train passes a level transition to a line fitted with more than one level, the onboard shall switch to the highest level, according to the priority given by trackside, for which <referential>it</referential> is equipped. INNOCUOUS
|
| 64 |
+
63 railway#15 On request of the RBC, the driver shall have the possibility to confirm that the track ahead of <referential>him</referential> until the end of the on sight section is clear . INNOCUOUS
|
| 65 |
+
64 railway#16 The braking curves shall ensure that the train complies with <referential>its</referential> speed requirements. INNOCUOUS
|
| 66 |
+
65 railway#17 If the release speed is calculated on board <referential>it</referential> shall ensure that the train will stop before reaching the danger point . NOCUOUS
|
| 67 |
+
66 railway#18 A train shall be supervised to <referential>its</referential> static and dynamic train speed profiles. INNOCUOUS
|
| 68 |
+
67 railway#19 Within the braking curve area, a warning shall be given to the driver to enable <referential>him</referential> to react and avoid intervention from ETCS equipment at least 5 sec. before the intervention. INNOCUOUS
|
| 69 |
+
68 railway#20 The ETCS trainborne equipment shall transmit <referential>its</referential> own train identification to the RBC. INNOCUOUS
|
| 70 |
+
69 railway#21 If a train cannot stop at the proposed new target location <referential>it</referential> shall reject the request and keep the old target location. NOCUOUS
|
| 71 |
+
70 railway#22 The train may proceed unrestricted to the end of <referential>its</referential> movement authority. INNOCUOUS
|
| 72 |
+
71 railway#23 <referential>It</referential> is acceptable that only one mobile user involved in the group call may talk at any time. INNOCUOUS
|
| 73 |
+
72 railway#24 If the text message facility is implemented, <referential>it</referential> shall not interfere with the ability of users to make or receive high priority voice or data calls. INNOCUOUS
|
| 74 |
+
73 railway#25 Where fax functionality is provided, <referential>it</referential> shall be possible to interrupt the fax to make or receive a high priority voice or data call. NOCUOUS
|
| 75 |
+
74 railway#26 The network shall provide the ability to inform a user, who is involved in an existing call, of attempts by other users to contact <referential>them</referential>. NOCUOUS
|
| 76 |
+
75 railway#27 Where network services are chargeable, <referential>it</referential> should be possible for the network to provide information about call rates and on-going call charges. INNOCUOUS
|
| 77 |
+
76 railway#28 Picking up the handset shall transfer the communication to the handset and reduce the loudspeaker volume to <referential>its</referential> minimum level. NOCUOUS
|
| 78 |
+
77 railway#29 An indication shall be provided to the driver as a reminder of the need to use the Push-To-Talk button on the handset if <referential>he</referential> wants to talk. INNOCUOUS
|
| 79 |
+
78 railway#30 <referential>It</referential> shall be possible for a driver to initiate Railway emergency calls (see section 13). INNOCUOUS
|
| 80 |
+
79 railway#31 If the train moves out of the call area whilst the call is in progress, <referential>it</referential> will leave the call and an audible and visual indication of the loss of call shall be provided to the driver. NOCUOUS
|
| 81 |
+
80 railway#32 Once the driver has accepted the standard point-to-point call, <referential>it</referential> shall be connected appropriately, eg if the driver has accepted the call by lifting the handset, then the call shall be routed to the handset. INNOCUOUS
|
| 82 |
+
81 railway#33 In this case, the security device alerts the driver if the link has failed or if <referential>it</referential> is cancelled. NOCUOUS
|
| 83 |
+
82 railway#34-1 <referential>It</referential> should be possible for the Cab radio to be used without the network service (if it should fail or if there is no authorised network coverage), such that local open channel communications are still possible. NOCUOUS
|
| 84 |
+
83 railway#34-2 It should be possible for the Cab radio to be used without the network service (if <referential>it</referential> should fail or if there is no authorised network coverage), such that local open channel communications are still possible. NOCUOUS
|
| 85 |
+
84 railway#35 Where the Cab radio is required by a national railway to support a handheld portable, the Cab radio shall: - provide a clear indication as to whether the handheld portable is activated or not; - provide an interface to allow the handheld portable to be recharged when not in use; - forward calls automatically to the handheld portable when the handheld portable is activated; - cancel any call forwarding to the handheld portable when <referential>it</referential> is deactivated; - allow the driver to override the call forwarding to the handheld portable. INNOCUOUS
|
| 86 |
+
85 railway#36 When the MMI is switched on, the configuration shall be determined by the time elapsed since the MMI was last switched off: - less than t minutes – the MMI shall power up with the same configuration as when <referential>it</referential> was last powered down; - greater than t minutes – the MMI shall power up with default settings. INNOCUOUS
|
| 87 |
+
86 railway#37 If directed network selection is implemented, input from the external device(s) shall initiate the network change regardless of the identity of the current network and how <referential>it</referential> was selected. NOCUOUS
|
| 88 |
+
87 railway#38 Non leading drivers shall be able to indicate to the system <referential>their</referential> location in the train during the registration procedure (2nd driver, 3rd driver etc). INNOCUOUS
|
| 89 |
+
88 railway#39 Each type of equipment has slightly different requirements placed upon <referential>it</referential> in terms of EMC and climate. INNOCUOUS
|
| 90 |
+
89 railway#40 The design of the equipment shall make <referential>it</referential> possible to install <referential>it</referential> within a cab complying with the requirements of UIC fiche 651 concerning the layout of cab equipment5. NOCUOUS
|
| 91 |
+
90 railway#41 If the call is a broadcast call, the user shall be informed that <referential>he</referential> cannot speak as part of the broadcast call. INNOCUOUS
|
| 92 |
+
91 railway#42 Where a change of functional number is required, <referential>it</referential> shall be possible for the user to initiate the change. NOCUOUS
|
| 93 |
+
92 railway#43-1 <referential>It</referential> shall be possible for the user to find and display stored numbers and their information. NOCUOUS
|
| 94 |
+
93 railway#43-2 It shall be possible for the user to find and display stored numbers and <referential>their</referential> information. NOCUOUS
|
| 95 |
+
94 railway#44 The Operational radio is specified to allow <referential>its</referential> use in the operating environment experienced on the operational railway (eg shunting and maintenance). INNOCUOUS
|
| 96 |
+
95 railway#45 Controls shall be designed such that <referential>they</referential> are suitable for use by people wearing gloves. INNOCUOUS
|
| 97 |
+
96 railway#46-1 <referential>It</referential> should be possible for the system to prevent certain types of users from registering functional numbers that they are not authorised to use, for example: - train number; - driver of train; - shunting team leader. NOCUOUS
|
| 98 |
+
97 railway#46-2 It should be possible for the system to prevent certain types of users from registering functional numbers that <referential>they</referential> are not authorised to use, for example: - train number; - driver of train; - shunting team leader. NOCUOUS
|
| 99 |
+
98 railway#47 As a minimum, the location information used by the EIRENE system shall be derived from that available from the network <referential>itself</referential> (eg current cell or base station serving the mobile). NOCUOUS
|
| 100 |
+
99 railway#48 After the 30 second period, if the connection was unsuccessful, the system shall provide another audible and visual indication that <referential>it</referential> was unable to connect the call. INNOCUOUS
|
| 101 |
+
100 railway#49 For post-incident analysis, <referential>it</referential> is important that the origination and reception of Railway emergency calls by mobiles is confirmed by a message sent to a ground-based central location (and also recorded in the on-train recording device). NOCUOUS
|
| 102 |
+
101 railway#50 Throughout the duration of the shunting group call, <referential>it</referential> shall be possible for any member of the shunting group to speak to all other members of the group, using the PTT function (as described in sections 5.2.2.53, 6.2.2.12 and 7.2.2.20), except during transmission of the link assurance signal. NOCUOUS
|
| 103 |
+
102 railway#51 The shunting leader can then choose the moment when <referential>he</referential> takes or rejects the call. INNOCUOUS
|
| 104 |
+
103 railway#52 In this case, the safety device will alert the driver only if the link assurance signal has failed or if <referential>it</referential> is cancelled. INNOCUOUS
|
| 105 |
+
104 railway#53 The 300ms represents <referential>our</referential> current best estimate of the QoS figure, although this will need to be confirmed through user trials. NOCUOUS
|
| 106 |
+
105 railway#54 Each authority can decide whether <referential>it</referential> wishes to use synchronised BTSs. INNOCUOUS
|
| 107 |
+
106 railway#55 The network shall terminate the ongoing VGCS/VBS call if <referential>it</referential> receives the 3-digit sequence “***” transmitted via DTMF signals. NOCUOUS
|
| 108 |
+
107 railway#56 The network shall send the SET-PARAMETER message with the attribute “D-ATT = T”1 [EN 301 515, Index [6]] to the mobile station of the talking subscriber if <referential>it</referential> receives the 3- digit sequence “###” transmitted via DTMF or the group call SETUP message2 from a controller terminal. NOCUOUS
|
| 109 |
+
108 railway#57-1 When the network has detected the 3-digit DTMF sequence “###” transmitted via DTMF from a controller terminal and if the controller was not previously talking <referential>it</referential> should indicate its recognition by playing a single DTMF grant tone “#” of duration of 100ms 5ms to be sent to that controller terminal only. NOCUOUS
|
| 110 |
+
109 railway#57-2 When the network has detected the 3-digit DTMF sequence “###” transmitted via DTMF from a controller terminal and if the controller was not previously talking it should indicate <referential>its</referential> recognition by playing a single DTMF grant tone “#” of duration of 100ms 5ms to be sent to that controller terminal only. NOCUOUS
|
| 111 |
+
110 railway#58 The network shall send the SET-PARAMETER message with the attribute “D-ATT = F”3 [EN 301 515, Index [6]] to the mobile of the talking subscriber only if <referential>it</referential> has received the 3-digit sequence “#**” transmitted via DTMF from all the talking controllers4. NOCUOUS
|
| 112 |
+
111 railway#59 Many of the railway specific standards referenced are Pre-standards (eg [prEN 50155, ENV 50121, prEN 50125]) and should be re-examined for <referential>their</referential> applicability to the EIRENE system if any modifications are made to these standards in the future. INNOCUOUS
|
| 113 |
+
112 railway#60 Each of the other cabs on the train will be contacted using <referential>its</referential> functional number (registered by the other drivers prior to the establishment of the call). NOCUOUS
|
| 114 |
+
113 railway#61 Upon registration, the mobile shall be accessible by calling the MSISDN or the Engine or Coach number with which <referential>it</referential> is associated. INNOCUOUS
|
| 115 |
+
114 railway#62 The Cab radio system shall provide a means for the driver to terminate established calls which <referential>he</referential> is authorised to terminate. INNOCUOUS
|
| 116 |
+
115 home#01 The DigitalHome programmable Appliance Manager shall provide for management of a home’s small appliances, including lighting units, by allowing a user to turn <referential>them</referential> on or off as desired. NOCUOUS
|
| 117 |
+
116 home#02 Although the product produced under this document will be a “prototype” version, all modules and components of this prototype version shall be designed and implemented in such a manner that <referential>it</referential> may be incorporated in a fully specified commercial version of the DigitalHome System. NOCUOUS
|
| 118 |
+
117 home#03 The DigitalHome System shall provide users with online documentation about the DigitalHome system installed in <referential>their</referential> home. INNOCUOUS
|
| 119 |
+
118 space#01 The FCP shall, if the NEFU ICP fails to send <referential>its</referential> ICP Ready signal, mask out that ICP, but continue to use the NE.16. INNOCUOUS
|
| 120 |
+
119 space#02 Each rate group has some number of tasks associated with <referential>it</referential>, and <referential>it</referential> also has a rate for those tasks. INNOCUOUS
|
| 121 |
+
120 space#03 The enabled tasks are then unblocked at the rate given in <referential>its</referential> associated rate group. NOCUOUS
|
| 122 |
+
121 space#04-1 An API call is available for the task to call to block <referential>itself</referential> when it is finished with its cyclic processing. NOCUOUS
|
| 123 |
+
122 space#04-2 An API call is available for the task to call to block itself when <referential>it</referential> is finished with its cyclic processing. NOCUOUS
|
| 124 |
+
123 space#04-3 An API call is available for the task to call to block itself when it is finished with <referential>its</referential> cyclic processing. NOCUOUS
|
| 125 |
+
124 space#05 There is up to a full major frame from notification of an impending mode change to acting on <referential>it</referential> in minor frame 0 of the next major frame plus the time <referential>it</referential> takes during the next minor frame 0 to switch tasking. NOCUOUS
|
| 126 |
+
125 space#06 The scheduler shall execute cyclic tasks, providing an API call to allow the application to block until <referential>its</referential> next iteration. NOCUOUS
|
| 127 |
+
126 space#07 The scheduler shall give tasks priority values according to <referential>their</referential> rate - the higher the rate, the higher the priority. NOCUOUS
|
| 128 |
+
127 space#08 The scheduler shall provide a mechanism to inform a task when <referential>it</referential> did not complete during the previous frame and restart <referential>it</referential> at the beginning of the task. NOCUOUS
|
| 129 |
+
128 space#09 All tasks in rate groups and <referential>their</referential> corresponding schedules for all vehicle modes will be setup at system initialization. NOCUOUS
|
| 130 |
+
129 space#10 Tasks in a rate group must suspend on a scheduler API call at the top of <referential>their</referential> execution loop. INNOCUOUS
|
| 131 |
+
130 space#11 For hardware exceptions and reserved exceptions, the FTSS shall make the error type and <referential>its</referential> context data available to the application, then return from the exception handler to the task that was running when the exception occurred. NOCUOUS
|
| 132 |
+
131 space#12 Messages are addressed with a global unique communication identifier that routes <referential>them</referential> to the appropriate virtual group (VG) and socket. INNOCUOUS
|
| 133 |
+
132 space#13 This restriction does NOT apply to the ICPs since <referential>they</referential> are running as simplex VGs. INNOCUOUS
|
| 134 |
+
133 space#14 The FTSS shall mask out a babbling NE or ICP within 40 milliseconds after <referential>it</referential> is detected. NOCUOUS
|
| 135 |
+
134 space#15 Synchronous message passing sockets shall queue outgoing messages until <referential>they</referential> are transmitted at frame boundaries. NOCUOUS
|
| 136 |
+
135 space#16 """Pipes may be opened by multiple receiving tasks if <referential>they</referential> are created with the broadcast"""" capability; otherwise <referential>they</referential> may only be opened by one receiving task.""""""" NOCUOUS
|
| 137 |
+
136 space#17 """Communication services shall provide the capability to create pipe""""s which """"broadcast"""" <referential>their</referential> messages to all virtual groups.""""""" NOCUOUS
|
| 138 |
+
137 space#18 If the broadcast option is used, each virtual group should open the pipe and read from <referential>it</referential> to avoid flow control problems. NOCUOUS
|
| 139 |
+
138 space#19 The application software shall have the capability to reset a permanently failed channel to <referential>its</referential> initial recovery state. NOCUOUS
|
| 140 |
+
139 space#20 Redundancy Management picks up where <referential>it</referential> left off in these attempts. INNOCUOUS
|