A method of managing event information relating to User Equipments (UEs) in a device is disclosed. The method includes creating a group of segments for each of the UEs upon the event information of the UEs, wherein each group includes at least one segment and each segment of one group includes the event information relating to the same UE; and storing the segments in order of time when the event information is recorded to obtain an event information sequence. A method for searching for the requested event information from the event information sequence is also provided.
Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A method for handling a request for obtaining event information relating to a User Equipment (UE) of a plurality of UEs from an event information sequence for the plurality of UEs, the event information sequence obtained by creating a plurality of segments for the plurality of UEs upon recording of event information for the plurality of UEs, in which segments pertaining to respective UEs are linked as a group and in which each segment including one or more elements, wherein each element includes a next pointer pointing to a next element in the event information sequence and a state to show whether the element is released, and wherein at least one element of each segment is a segment head that includes a next segment pointer pointing to a next segment in a same group, a previous pointer pointing to a previous element in the event information sequence, and an identity of the segment, and storing the elements in order of time when the event information sequence is recorded for the plurality of UEs, the method including: obtaining the group of segments which is created for the UE from the event information sequence based on an identity of the UE included in the request; comparing at least one matching parameter included in the request with event information of each element of segments in the group for the UE till the requested event information is obtained or all elements if the group is compared, wherein a next element to be compared is found via at least one of a next pointer and a next segment pointer of the current element; and obtaining respective event information when said at least one matching parameter is matched.
A method for efficiently searching through event logs for specific User Equipment (UE) devices. Event logs are structured as an ordered sequence of segments, grouped by UE. Each segment contains elements with event information, a "next" pointer to the next event, and a flag indicating if the event is still active. Each segment also has a "head" element containing a "next segment" pointer to the next segment for that UE, a "previous" pointer to the previous element in the sequence, and a segment ID. To find events for a specific UE, the system retrieves the UE's group of segments, then compares search parameters against each event in the group, traversing events using the "next" or "next segment" pointers until a match is found or all events have been checked.
2. The method according to claim 1 , wherein one or more element of each segment, except said at least one element being the segment head, is a segment member.
In the method described where event logs for User Equipment (UE) devices are searched, each segment, which contain events with a "next" pointer to the next event, has a "head" element with a "next segment" pointer, and additional elements called "segment members." The "segment member" elements contain the actual event details, while the "segment head" element provides the overall structure and pointers to link segments belonging to the same UE together for efficient retrieval and searching.
3. The method according to claim 2 , wherein storing the elements in order of time including: storing all of the segment heads in a segment head allocated area of a storage with consecutive storage units; storing all of the segment members in a segment member allocated area of said storage; and setting an unallocated area between the segment head allocated area and the segment member allocated area in the storage.
The method of managing event logs for User Equipment (UE) devices by dividing storage into three sections: a section for segment heads, a section for segment members, and an unused area between them. Segment heads (containing "next segment" pointers) are stored contiguously in the head section. Segment members (containing event details) are stored contiguously in the member section. This arrangement optimizes storage and retrieval, but a separate unallocated space is kept between these sections.
4. The method according to claim 1 , wherein the next element to be compared is found via the next pointer when the next element to be compared is a segment member in the group, and the next element to be compared is found via the next segment pointer when the next element to be compared is a segment head.
In the event log search method for User Equipment (UE) devices, when traversing a UE's event segments, the system uses different pointers depending on the type of element it's currently examining. If the next element is a "segment member" (containing event details), the system uses the standard "next" pointer to find it. However, if the next element is a "segment head" (linking to the next segment), the system uses the "next segment" pointer to jump to the beginning of the subsequent segment within the same UE's event history.
5. The method according to claim 1 , wherein obtaining the group of segments for the UE includes: getting a UE context based on the identity of the UE, wherein the UE context includes a head pointer which points to a first segment of the group for the UE and a tail pointer which points to the last segment of the group; and obtaining the group of segments for the UE based on the head pointer and tail pointer.
To efficiently retrieve events for a specific User Equipment (UE), the system first obtains a UE context using the UE's ID. This context contains a "head pointer" pointing to the first segment in the UE's event log and a "tail pointer" pointing to the last segment. By using these head and tail pointers, the system can quickly access the entire group of segments associated with the UE, streamlining the process of searching for specific event information within the UE's history, without needing to scan all event logs.
6. An equipment used for handling event information relating to User Equipment, comprising: a storage device, used to store an event information sequence for a plurality of User Equipment (UEs), including event information for a UE of the plurality of UEs, which event information sequence is obtained by creating a plurality of segments for the plurality of UEs upon recording of event information for the plurality of UEs, in which segments pertaining to respective UEs are linked as a group and in which each segment including one or more elements, wherein each element includes a next pointer pointing to a next element in the event information sequence and a state to show whether the element is released, and wherein at least one element of each segment is a segment head that includes a next segment pointer pointing to a next segment in a same group, one or more previous pointers pointing to a previous element in the event information sequence, and an identity of the segment, and arranging the elements in order of time when the event information sequence is recorded for the plurality of UEs, in which the storage device is divided into a head allocated area, a member allocated area, and an unallocated area, in which the head allocated area is used to store each segment head which is provided with the next pointer, the previous pointer, the next segment pointer, the state and the identity, and the member allocated arena is used to store each element that is not a segment head as a segment member; an input module, used to receive a request for obtaining event information from the storage device; and an output module, used to output a result responding to the request.
An equipment designed for managing User Equipment (UE) event information using segmented logs: it includes a storage device divided into three areas. The first is for segment heads (containing "next," "previous," "next segment" pointers, status, and ID). The second stores segment members (event details). An unused area is maintained between the head and member sections. An input module receives search requests. An output module presents the results. The storage holds event logs structured as segments linked by pointers. An event information sequence is obtained by creating multiple segments linked as a group for each UE when event information is recorded.
7. The equipment according to claim 6 , wherein at least one of an idle storage unit of the head allocated area and the member allocated area is merged with its adjacent storage unit when the latter is idle or unallocated to store the element to form an idle area, and the idle storage unit or the idle area is merged with the unallocated area when the idle storage unit or the idle area is adjacent to the unallocated area, respectively, at least one of the idle storage unit of the head allocated area and the member allocated area referring to the unit in which the state of the stored element shows the element is released.
The equipment that manages segmented event logs for User Equipment (UE) described in the previous claim optimizes storage by merging released (idle) segment head or segment member storage units with adjacent idle/unallocated units to create larger free areas. If these resulting idle areas border the unallocated storage area between the segment head and segment member regions, they are further merged with that unallocated area. This dynamic allocation and merging helps reduce fragmentation and improves overall storage efficiency as the device manages event logs.
8. The equipment according to claim 6 , further including an application processing module used for: obtaining, upon the request which is received via the input module for obtaining event information, a group of segments which are created for a UE and stored in the storage device based on an identity of the UE included in the request; comparing at least one matching parameter included in the request with event information of the segments in the obtained group; and outputting the event information via the output module if said at least one matching parameters are matched.
The equipment which manages User Equipment (UE) event information in segmented logs, includes an application processing module. When a request is received to search for a UE's event information, the module retrieves the appropriate segment group from the storage device using the UE's ID. It then compares provided search parameters against the event information within the retrieved segments. If any of the search parameters match, the corresponding event information is outputted via the output module, providing the requested event details.
9. The equipment according to claim 8 , wherein the application processing module is further used to compare the at least one matching parameter with the event information of each element of segments in the group till the requested event information is obtained or all elements of the group is compared, wherein a next element to be compared is found via at least one of a next pointer and a next segment pointer of the current element.
The equipment described which manages User Equipment (UE) event information in segmented logs refines its event searching process. The application processing module compares search parameters against each element within the segments of a UE's event group, continuing until a match is found or all elements have been checked. The module determines the next element to compare using either the "next" pointer (for traversing within a segment) or the "next segment" pointer (for jumping to the next segment within the UE's group), ensuring a thorough and efficient search of the segmented event logs.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
December 30, 2010
April 11, 2017
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.