The three examples below illustrate a research-oriented search workflow: start from a clearly defined technical problem, set up keywords and synonyms, narrow the range with IPC/CPC directions, expand through patent families and citations, and then distinguish among patent specifications, standards texts, and marketing material in the results. The keywords and classification directions in this article are examples only. Before searching, they should be checked against the current databases and classification tables of the relevant offices. The article does not guarantee coverage of all synonyms or all jurisdictions.

Example One: Floor Arbitration and Priority

Problem definition In half-duplex group calling, when multiple users request transmit rights at the same time, how does the system decide who gets the floor, whether higher-priority users may preempt, and how conflicts are avoided? Searching only for "push to talk" or "two-way radio" usually creates heavy noise. It is better to move toward terms related to dispatch semantics, such as arbitration, floor control, talk permit, and priority.

Keywords and combinations Useful English queries may include push to talk arbitration, floor control, group call priority, dispatch talk permit, and preemption. Additional context terms such as "wireless," "group call," "mobile radio," and "LMR" help distinguish the field from general conferencing systems or VoIP meeting patents. Chinese search environments may add equivalents for floor right, preemption, group call, and dispatch.

Classification directions Filtering inside H04 sections related to wireless communications and multi-user scheduling can help, although the exact IPC/CPC codes must be checked against the current version of the classification tables. In practice, combining keywords with classification filters is usually more stable than relying on one broad keyword alone.

Handling mixed results If search results contain large amounts of video-conferencing floor-control material or pure WebRTC signaling documents, a second round of filtering can be applied using the applicant's technical field or abstract terms such as "radio," "LTE," and "LMR." When the same technical idea appears both in standards and in patents, the citations should be listed separately. Standards clauses and patent claim scope do not automatically mean the same thing.

Example Two: RoIP and Cross-Network Interoperability

Problem definition Gateways, routing, and group-call interoperability between traditional private radio systems and IP networks often involve mapping radio channels into IP multicast or SIP environments and connecting systems from different vendors. Useful technical terms include radio over IP, RoIP, LMR gateway, dispatch interoperability, interconnect, and cross-network group communication.

Search characteristics This topic easily crosses product lines in private radio, enterprise dispatch, and softswitch systems. A patent family may include both a hardware gateway and a pure software-routing implementation. If the survey first splits the field into the "repeaters and routing" and "broadband PTT" buckets from the patent topic map, and then assigns different keyword weights to each bucket, repeated work can be reduced.

Document types Vendor white papers often describe "interoperability architecture diagrams," but they do not necessarily correspond to independently granted patents. Patent claims more often sit on specific signaling conversion, state synchronization, or failover methods. A review should label document type explicitly so that a marketing diagram is not treated as a technical source.

Example Three: MCPTT and Broadband PTT

Problem definition Mission-critical push-to-talk over LTE or other cellular packet networks involves server-side floor control, group-call establishment, cooperation with QoS and bearer mechanisms, and interaction between terminals and the network. Common English keywords include mission critical push to talk, MCPTT, group communication over LTE, floor control server, and push to talk over cellular.

Search difficulty In this field, standards documents such as 3GPP technical specifications, patents, and operator white papers often overlap heavily in their titles and abstracts. A researcher should therefore separate them actively: standards clauses are interoperability specifications; patents are specific implementation proposals; white papers may contain operational recommendations that were never filed as patents. If SEP analysis is required, it needs a separate methodology and dedicated databases, which this volume does not cover.

Integrating the workflow into the text A typical sequence is: define the technical problem and its boundary; list keywords and synonyms; execute the search in the chosen databases and record the date; trace citations and patent families for the core documents; verify legal status; and then organize the results into traceable notes. A flowchart is optional. Traceability matters more than the visual form of the steps.

If the result set is still too large, the search may be tightened by narrowing the applicant or inventor technical field, limiting publication dates to the past ten years, or switching to a citation-based outward search from one highly relevant document. If the result set is too small, check whether the search relies too heavily on one product trademark or on obsolete classification codes. Running both Chinese-language and English-language databases often fills gaps left by either side alone.

References

The keywords above are for research training only. Actual patent status and claim scope depend on the public records of the competent patent offices.