discussed briefly above, a network service, referred to herein as the schedule processor and trigger service (“STS”) 302, generates the pre-meeting signal 212 in some configurations. 

[0048] In order to generate the pre-meeting signal 212, the STS 302 can utilize schedule-based processing 306 and/or event-based processing 304. When schedule-based processing 306 is utilized, the STS 302 retrieves a list 310 of upcoming meetings on a predefined schedule (e.g. once per day). For example, and without limitation, the STS 302 might call a calendaring application programming interface (“API”) 308 to retrieve a list of upcoming meetings 310 for a predetermined period of time in the future (e.g. seven days ) from the substrate 206 according to a predefined schedule. The list of meetings 310 can be generated based upon data defining the meetings 312 on users’calendars 314 stored in the substrate 206 or in another location. 

[0049] Using data identifying the start time of the meetings specified in the list 310 of upcoming meetings, the STS 302 can generate a pre-meeting signal 212 a predetermined amount of time (e.g. one hour) prior to the start time of each meeting. For example, and without limitation, if a meeting is scheduled to begin at 2:00 pm, the STS 302 can transmit a pre-meeting signal 212 to the language model preparation service 210 for the meeting at 1:00 pm. As described briefly above, the language model preparation service 210 generates a meeting-specific statistical language model 216 for the meeting identified by the pre meeting signal 212. In this manner, generation of a meeting-specific statistical language model 216 for a meeting can begin at a predetermined amount of time prior to the start of the meeting. 

[0050] As mentioned above, the STS might also, or alternately, user event-based processing 302 to trigger generation of pre-meeting signals 212 for meetings. In order to utilize event-based processing 302, the STS 302 can subscribe to receive meeting change event notifications 316. In one particular embodiment, for example, an event signaling service 318 can generate meeting change event notifications 316 responsive to detecting that a meeting has changed. For example, the event signaling service 318 might generate a meeting change event notification 316 responsive to detecting the addition or removal of attendees to/from a meeting, the addition or removal of files associated with a meeting, or the modification of the start time of the meeting. The meeting change event notification 316 includes data describing the detected changes to a meeting. 

[0051] Once the STS 302 has subscribed to receive meeting change event notifications 316, the STS 302 can generate a pre-meeting signal 212 in response to receiving a meeting change event notification 316. This can occur prior to or during a 

